Check-List: GUI Testing of Windows and Screens

May 31, 2011 - PRLog -- Plan of checks of GUI application can be called a check-list. This check-list allows us not forget what we wanted and what we need to check.
It is very simple to use it. First define the windows and screens, for which we must check the user interface (GUI). And subsequently for each panel run such checks:
1. Check the entry point. In what cases this window is appearing?
For example:
•   Panel of navigation
•   A drop-down menu list
•   The menu on right click
•   Labels
2. The general state of the window
•   Check all items in the window in their presence: all the necessary elements must be in their place (this may be a field, signature, lists, check boxes, a group of elements, buttons, window titles, menus, etc. ).
•   Check the window: it is desirable that it had a friendly user interface and more convenient for users
•   Check the grammar: it must be checked in all the texts, inscriptions and messages
•   Check the condition of the items in the default settings and their values (they can be active or inactive, something can be selected and something might have some value, etc.)
3. Navigation
•   Check where you can move from page
•   Pay special attention to the "Back" (if there is such)
•   Check the location of the cursor by default (if it is necessary)
•   Check the navigation using the keyboard Tab, Up, Down, etc.: it must be logical and convenient
4. Hotkeys
•   Check the hot keys which are available for application
•   Standard keyboard combination (Ctrl + C, Alt + F4, etc.)
5. Standard functionality of window
For example:
•   Lists - scrolling, sorting
•   Text boxes - should be editable
•   The check-boxes – select, unselect
•   Radio-sticks – select, unselect
•   Fields are read-only
•   Fields passwords
6. Check of data
•   None
•   The minimum value
•   The maximum value
•   Less than the maximum
•   More than the minimum
•   The correct data type (char, numeric, etc.)
•   Incorrect data type
•   All the necessary values
7. Check the necessary input parameters
•   All necessary parameters are defined
•   Necessary parameters are not defined (or all except one)
•   Check the condition of window elements, depending on the states of elements and data
8. Changing of the size of the window. Check the behavior of the elements in the window:
•   When resizing the window
•   Compression and tension
•   Minimize and restore
•   If you change the screen resolution
9. Localization
•   Check the box and its components for the localizations which supports by application
•   Check for various locales environments (operating systems, etc.)
Also it is very important to do functional testing http://qatestlab.com/services/our-qa-services/functional-.... Not just what our application looks like but what our application can do, what function does it perform? Part of the functional problems appears in verifying GUI http://qatestlab.com/company/software-testing-glossary/gu.... More serious problems require a careful approach of testing the functionality. Let’s note in conclusion that it is necessary to allocate a separate group of functional tests.

# # #

QATestLab is independent, offshore software testing company located in Kiev, Ukraine. QATestLab performs testing of products on each stage of software development cycle.