GUI Testing

Graphic User Interface - GUI software testing is the process of testing a product that uses a graphical user interface, to ensure that the end product is satisfying the requirement specified by the client and how easy it is to understand by a common user.

1. GUI Testing

2. Contents GUI Testing –What Is It Why is GUI Testing Important What to look for when performing GUI Testing General Guidelines for GUI Testing A List of GUI Errors

3. GUI Testing - What Is It GUI stands for : Graphic User Interface - GUI software testing is the process of testing a product that uses a graphical user interface, to ensure that the end product is satisfying the requirement specified by the client and how easy it is to understand by a common user. GUI testing means testing the user interface by considering parameters like consistency, usability, visibility, compatibility, Alignment, Spell Check.

4. Why is GUI Testing Important To find out if all functions work correctly on various platforms. To find out if all functions are user friendly. To find out all displays are user understandable. To find out all wording makes sense and is consistent. To have new releases tested and be sure nothing is broken.

5. What to look for when performing GUI Testing for a website For any testing there should be some set of standards to be followed. We should follow the requirements specification documents for GUI testing. There should be some screen shots (given by client) which we should follow as it is.

6. What to look for when performing GUI Testing for a website There are several factors to consider: • Look and Feel  – You must validate that all designed and expected functionality is present and correct and verify that the information that the GUI supplies to the user is correct. • Ease of use  – Does the presentation make the software simple and straightforward to use? 

7. What to look for when performing GUI Testing for a website Clarity  – Are all graphics and text visible and unambiguous?  • Functionality  – All menus, buttons, icons, etc. should respond as expected. • Uniformity  – All graphics and text, button shape and effects, fonts, colors, etc. must be uniform.

8. General Guidelines for GUI Testing All the dialog boxes should have a consistent look through out the Application system. For e.g.- If the heading within a dialog box is blue then for each dialog box the heading should be of this color. Every field on the screen should have an associated Label. Every screen should have an equivalent OK and cancel button. The color combination used should be appealing.

9. General Guidelines for GUI Testing Tab order should be normally set horizontally for the fields. In some case as per the case the Tab Order can be set vertically. Mandatory fields should have * (RED ASTERIK) marked to indicate that they are mandatory fields. Test Functionality of control objects like buttons, textbox, list box etc

10. General Guidelines for GUI Testing Default key <Enter> should be set as OK for the dialog box. Default key <Esc> should be set as Cancel for the dialog box. Test User Friendly labels and Messages, related message content, understandability of the message. Test use of colors, fonts, alignment, tab orders. Test Ease of Navigation.

11. A List of GUI Errors A list of GUI Errors GUI errors include Data validation Incorrect field defaults Mandatory fields, not mandatory Incorrect search criteria

12. A List of GUI Errors Currency of data on screens. Field order. Wrong fields retrieved by queries Focus on objects needing it.