7 GUI Testing

Entry criteria: Before GUI Testing can take place, the GUI (or relevant parts of it) must exist such that these tests are relevant.

Exit criteria: A GUI Testing report must be generated showing where the GUI functions as expected and where it does not.

Due to the nature of GUI Testing, it cannot be automated. Therefore, to test the GUI, the GUI Tester must actually run the GUI and report on its behavior. The GUI Tester must make note of the following [1]:

• Can windows be resized, moved and scrolled?
• Does the window properly regenerate when it is overwritten and then recalled?
• Are all relevant pull-down menus, tool bars, scroll bars, dialog boxes, buttons, icons and other controls available and properly displayed?
• Is the name of the window properly represented?
• Is the active window properly highlighted?
• Do multiple or incorrect mouse clicks within the window cause unexpected side effects?
• Does the window close properly?
• Do pull-down menu operations work properly?
• Are all pull-down menu functions properly listed?
• Is text typeface, size, placing and format correct?
• Does each menu function perform as advertised?
• Are the names of menu functions self-explanatory?
• Is alphanumeric data entry properly echoed?
• Do graphical modes of data entry work properly?
• Are data input messages intelligible?