Scribd
Upload
53 views

GUI Testing Coverage

The document outlines a comprehensive set of GUI testing coverage areas including checking that all required elements are displayed correctly, URLs and page titles are correct, fields are properly aligned and validated, colors and formatting meet standards, images are displayed properly, navigation and pagination functions as intended, and the interface has good usability by being readable, intuitive and responsive across resolutions. It includes testing fields, buttons, links, validation messages, colors, content, images, navigation, and usability.

Uploaded by

Prafula Bartel
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
53 views

GUI Testing Coverage

The document outlines a comprehensive set of GUI testing coverage areas including checking that all required elements are displayed correctly, URLs and page titles are correct, fields are properly aligned and validated, colors and formatting meet standards, images are displayed properly, navigation and pagination functions as intended, and the interface has good usability by being readable, intuitive and responsive across resolutions. It includes testing fields, buttons, links, validation messages, colors, content, images, navigation, and usability.

Uploaded by

Prafula Bartel
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

GUI Testing Coverage

1. Check the all required objects, elements, fields, buttons, labels and links are available

2. Check the URLs of the each page

3. Check the page titles of the each page

4. Check all pages for broken links

5. All fields on pages (e.g. text box, radio options, drop-down lists) should be aligned properly with
size, position, width, height of the elements.

6. Do buttons follow the project standards for size and position?

7. Enough space should be provided between field labels, columns, rows, error messages etc.

8. All mandatory fields should be validated and indicated by asterisk (*) symbol

9. Validation error messages should be displayed properly at correct position

10. Input fields should be checked for maximum field value. Input values greater than specified max
limit should not be accepted or stored in database

11. Confirmation messages should be displayed before performing any update or delete operation

12. Tooltip text should be meaningful.

13. COLORS

13.1 Are the field backgrounds the correct color?

13.2 Are the field prompts the correct color?

13.3 Are the screen and field colors adjusted correctly for non-editable mode?

13.4 Are all the buttons are in standard format and size?

13.5 Is the general screen background the correct color?

13.6 Is the page background (color) distraction free?

13.7 Testing the colors of the error messages, warning messages and success messages displayed in
different CSS styles for each.

14. CONTENT

14.1 Are all the screen prompts specified in the correct screen font?

14.2 Does content remain if you need to go back to a previous page, or if you move forward to
another new page?

14.3 Is all text properly aligned?


14.4 Is the text in all fields specified in the correct screen font?

14.5 Is all the headings are left aligned

14.6 Font size, style and color for headline, description text and labels should be standard as
specified in SRS and check the font whether it is readable or not.

14.7 Testing of the spelling, and ensure that you have test cases that look for grammar or spelling
errors…

15. IMAGES/ICONS

15.1 Are all graphics properly aligned?

15.2 Are graphics being used the most efficient use of file size?

15.3 Assure that buttons are all of similar size and shape, and same font & font size.

15.4 Banner style & size & display exact same as existing windows

15.5 Does text wrap properly around pictures/graphics?

15.6 Testing the alignment of the images and Check all pages for broken images.

16. NAVIGATION

16.1 Can all screens accessible via buttons on this screen be accessed correctly?

16.2 Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? This
is the default unless otherwise specified.

16.3 Is there a link to home on every single page?

16.4 When an error message occurs does the focus return to the field in error when the user cancels
it?

16.5 Testing of the scrollbars according to the size of the page if any.

16.6 Pagination should be enabled when there are more results than the default result count per
page

16.7 Check for Next, Previous, First and Last page pagination functionality

17. USABILITY

17.1 Are all the field prompts spelled correctly?

17.2 Are fonts too large or too small to read?

17.3 Can the typical user run the system without frustration?

17.4 Do pages print legibly without cutting off text?


17.5 Does the site convey a clear sense of its intended audience?

17.6 Does the site have a consistent, clearly recognizable “look-&-feel”?

17.7 Check the screen in different resolutions with the help of zooming in and zooming out like 640 x
480, 600×800, etc.

17.8 Testing whether the interface is attractive or not.

17.9 Does the system provide or facilitate customer service? i.e. responsive, helpful, accurate?

17.10 Is all terminology understandable for all of the site’s intended users?

You might also like