GUI stands for Graphical User Interface where user interacts with the application using mouse, keyboard or other interfaces.
GUI testing includes verifying whether your application meets the standards of graphical user interface or GUI standard specifications.
GUI Testing can be done in 4 ways:
1. Manually
User inputs data and verifies whether application interacts as expected.
2. Record and Playback
User records set of actions using record and playback tools like selenium or Microsoft Test Professional or win-runner and plays back the recorded actions usually tweaking the recorded scripts to include verification for elements present using css or xpath location of a particular element like image. In this approach tester needs to monitor each step of the recorded playback.
3. Coded UI Testing and
In Coded UI Testing tester or developer adds codes to check validation messages, navigations, UI Elements positions, Sizes, Fonts etc., and generate reports on whether the coded tests passed or failed.
4. Model/Graphical representational state transition based testing
In this approach a graphical representation of systems behavior model is prepared. Based on the representation, application is tested whether its behavior matches to the flow.
GUI Check Lists include:
1. Verify whether meaningful tool tips are available.
2. Verify whether proper field labels are present.
3. Verify Field value font, size, prompt message properties, alignment.
4. Verify Navigation.
5. Verify sorting of drop down values and default values.
6. Verify type ahead of drop down values.
7. Verify validation messages and appropriate icon used in message pop up dialog box.
8. Verify event coverage like click action, navigation, save and close.
9. Verify character limits and lengths.
10. Verify validations for special characters, blank values, alpha numerical values, only alphabets, only digits and so on.
11. Verify mandatory fields.
12. Verify error message, warning message, information message and validation message formats.
13. Verify hover effects, click effects, drag effects.
14. Verify hour glass when application is fetching some result.
15. Verify UI elements, alignment of elements for different standard screen resolutions.
16. Check readability, usability, user friendliness etc,.
17 Verify whether images are skewed, pixilated and that they have good resolution.
18. Verify scroll bars wherever necessary.
19. Verify if buttons, text fields and other UI elements are meant to be round cornered.
IMPORTANT LINKS:
| Introduction to Software Testing | Roles and Responsibilities of a Software Tester | What is a Test Case | Software Testing types and Methods | STLC Process | Hierarchy Chart | Differences between Desktop application testing, Client Server application testing, and Web Based application testing | Most Common Interview Questions | Resume Preparation Tips | SDLC Models | Blog Index | Software Testing FAQs |
| Introduction to Software Testing | Roles and Responsibilities of a Software Tester | What is a Test Case | Software Testing types and Methods | STLC Process | Hierarchy Chart | Differences between Desktop application testing, Client Server application testing, and Web Based application testing | Most Common Interview Questions | Resume Preparation Tips | SDLC Models | Blog Index | Software Testing FAQs |
No comments:
Post a Comment
I would like to thank you for your comments..! Please keep commenting. To get posts and updates via mail, I would suggest you to subscribe the Blog. Thanks Again..!