Page 74 - SOFTWARE TESTING & QUALITY ASSURANCE

Unit 5: Special Types of Testing

Let us now learn some of the general guidelines for GUI testing. It should be ensured that:
1. All the dialog boxes have a consistent appearance throughout the application system.

If a heading in a dialog box is grey, the headings in other dialog boxes should
also be of the same color.

2. Every field on the screen has an associated label.
3. Every screen has an equivalent OK and Cancel button (with an appealing color combination).

4. Every field in the dialog box supports short cut key functioning.
5. Tab order is set horizontal to the fields, as sometimes it can be vertical.
6. Mandatory fields are marked with red asterisk (*) to denote that they are mandatory.
7. Default key <Enter> is set as OK for the dialog box.
8. Default key <Esc> is set as Cancel for the dialog box.

You should remember the following ten points while performing GUI testing:
1. Test for user friendly labels, messages, related message content, and
understandability of the message.

2. Test ease of navigation.
3. Test availability of help for a particular operation.
4. Test use of colors, fonts, alignment, and tab orders.
5. Test end to end navigation.
6. Test functionality of control objects like buttons, textbox, list box, and so on.

7. Test for the risk of critical defects.
8. Test the strict adherence to time and schedule.
9. Test the risk of Quality Assurance (QA) resources yet to be familiarized on the
new application.
10. Test the risk of low priority aspects of the application that is not being tested till
the later stages.

5.2.1 Standards and Guidelines
Standards and guidelines are necessary to obtain a quality software product with good user interface
and reliability.
A software tester needs to pretend to be the user while testing for usability and locate the possible
errors or problem-prone areas in the software product.

LOVELY PROFESSIONAL UNIVERSITY 67