GUI Testing Checklist - General Conditions
Check List for Software Testing
(Continued from previous question...)
GUI Testing Checklist - General Conditions
- Assure the existence of the "Help" menu.
- Assure that the proper commands and options are in each menu.
- Assure that all buttons on all tool bars have a corresponding key commands.
- Assure that each menu command has an alternative(hot-key) key sequence
which will invoke it where appropriate.
- In drop down list boxes, ensure that the names are not abbreviations /
- In drop down list boxes, assure that the list and each entry in the list
can be accessed via appropriate key / hot key combinations.
- Ensure that duplicate hot keys do not exist on each screen
- Ensure the proper usage of the escape key (which is to undo any changes
that have been made) and generates a caution message "Changes will be lost
- Continue yes/no"
- Assure that the cancel button functions the same as the escape key.
- Assure that the Cancel button operates as a Close button when changes have
be made that cannot be undone.
- Assure that only command buttons which are used by a particular window,
or in a particular dialog box, are present. - i.e make sure they don't
work on the screen behind the current screen.
- When a command button is used sometimes and not at other times, assure
that it is grayed out when it should not be used.
- Assure that OK and Cancel buttons are grouped separately from other command
- Assure that command button names are not abbreviations.
- Assure that all field labels/names are not technical labels, but rather
are names meaningful to system users.
- Assure that command buttons are all of similar size and shape, and same
font & font size.
- Assure that each command button can be accessed via a hot key combination.
- Assure that command buttons in the same window/dialog box do not have duplicate
- Assure that each window/dialog box has a clearly marked default value (command
button, or other object) which is invoked when the Enter key is pressed
- and NOT the Cancel or Close button
- Assure that focus is set to an object/button which makes sense according
to the function of the window/dialog box.
- Assure that all option buttons (and radio buttons) names are not abbreviations.
- Assure that option button names are not technical labels, but rather are
names meaningful to system users.
- If hot keys are used to access option buttons, assure that duplicate hot
keys do not exist in the same window/dialog box.
- Assure that option box names are not abbreviations.
- Assure that option boxes, option buttons, and command buttons are logically
grouped together in clearly demarcated areas "Group Box"
- Assure that the Tab key sequence which traverses the screens does so in
a logical way.
- Assure consistency of mouse actions across windows.
- Assure that the color red is not used to highlight active objects (many
individuals are red-green color blind).
- Assure that the user will have control of the desktop with respect to general
color and highlighting (the application should not dictate the desktop
- Assure that the screen/window does not have a cluttered appearance
- Ctrl + F6 opens next tab within tabbed window
- Shift + Ctrl + F6 opens previous tab within tabbed window
- Tabbing will open next tab within tabbed window if on last field of current
- Tabbing will go onto the 'Continue' button if on last field of last tab
within tabbed window
- Tabbing will go onto the next editable field in the window
- Banner style & size & display exact same as existing windows
- If 8 or less options in a list box, display all options on open of list
box - should be no need to scroll
- Errors on continue will cause user to be returned to the tab and the focus
should be on the field causing the error. (i.e the tab is opened, highlighting
the field with the error on it)
- Pressing continue while on the first tab of a tabbed window (assuming all
fields filled correctly) will not open all the tabs.
- On open of tab focus will be on first editable field
- All fonts to be the same
- Alt+F4 will close the tabbed window and return you to main screen or previous
screen (as appropriate), generating "changes will be lost" message if necessary.
- Microhelp text for every enabled field & button
- Ensure all fields are disabled in read-only mode
- Progress messages on load of tabbed screens
- Return operates continue
- If retrieve on load of tabbed window fails window should not open
(Continued on next question...)
Other Interview Questions