GUI Testing Checklist

By Anand Ramdeo on May 3, 2011 Comments

Purpose of this GUI Testing Checklist is to help you understand how your application can be tested according to the known and understood standards for GUI. This checklist can give some guidance to both development and QE teams. Development team can make sure that during the development they follow guidelines related to the compliance, aesthetics, navigation etc. but onus of testing GUI is on the QE team and as a tester it is your responsibility to validate your product against GUI standards followed by your organization.

This GUI test checklist can ensure that all the GUI components are thoroughly tested. In the first part of this checklist, we will cover Windows compliance standard and some test ideas for field specific tests.

Windows Compliance Standards

These compliance standards are followed by almost all the windows based application. Any variance from these standards can result into inconvenience to the user. This compliance must be followed for every application. These compliances can be categorized according to following criteria

Compliance for each application

  • Application should be started by double clicking on the icon.
  • Loading message should have information about application name, version number, icon etc.
  • Main window of application should have same caption as the icon in the program manager.
  • Closing of the application should result in “Are you sure?” message.
  • Behaviour for starting application more than once must be specified.
  • Try to start application while it is loading
  • On every application, if application is busy it should show hour glass or some other mechanism to notify user that it is processing.
  • Normally F1 button is used for help. If your product has help integrated, it should come by pressing F1 button.
  • Minimize and restoring functionality should work properly
  • Compliance for each window in the application
  • Window caption for every application should have application name and window name. Specially, error messages.
  • Title of the window and information should make sense to the user.
  • If screen has control menu, use the entire control menu like move, close, resize etc.
  • Text present should be checked for spelling and grammar.
  • If tab navigation is present, TAB should move focus in forward direction and SHIFT+TAB in backward direction.
  • Tab order should be left to right and top to bottom within a group box.
  • If focus is present on any control, it should be presented by dotting lines around it.
  • User should not be able to select greyed or disabled control. Try this using tab as well as mouse.
  • Text should be left justified
  • In general, all the operations should have corresponding key board shortcut key for this.
  • All tab buttons should have distinct letter for it.

Text boxes

  • Move mouse to textbox and it should be changed to insert bar for editable text field and should remain unchanged for non-editable text field.
  • Test overflowing textbox by inserting as many characters as you can in the text field. Also test width of the text field by entering all capital W.
  • Enter invalid characters, special characters and make sure that there is no abnormality.
  • User should be able to select text using Shift + arrow keys.
  • Selection should be possible using mouse and double click should select entire text in the text box.

Radio Buttons

  • Only one should be selected from the given option.
  • User should be able to select any button using mouse or key board
  • Arrow key should set/unset the radio buttons.

Check boxes

  • User should be able to select any combination of checkboxes
  • Clicking mouse on the box should set/unset the checkbox.
  • Spacebar should also do the same

Push Buttons

  • All buttons except OK/Cancel should have a letter access to them. This is indicated by a letter underlined in the button text. The button should be activated by pressing ALT
  • Clicking each button with mouse should activate it and trigger required action.
  • Similarly, after giving focus SPACE or RETURN button should also do the same.
  • If there is any Cancel button on the screen, pressing Esc should activate it.

Drop down list boxes

  • Pressing the arrow should give list of options available to the user. List can be scrollable but user should not be able to type in.
  • Pressing Ctrl-F4 should open the list box.
  • Pressing a letter should bring the first item in the list starting with the same letter.
  • Items should be in alphabetical order in any list.
  • Selected item should be displayed on the list.
  • There should be only one blank space in the dropdown list.

Combo Box

  • Similar to the list mentioned above, but user should be able to enter text in it.

List Boxes

  • Should allow single select, either by mouse or arrow keys.
  • Pressing any letter should take you to the first element starting with that letter
  • If there are view/open button, double clicking on icon should be mapped to these behaviour.
  • Make sure that all the data can be seen using scroll bar.

Hope this checklist will help you in testing your GUI components in a better way. In next template, TestingGeek will discuss information about field specific tests and usage of shortcuts in the application GUI.

blog comments powered by Disqus
Finished reading? Browse all posts »