Explain GUI Testing and it's Contents - Define UI Testing

GUI Testing is nothing but testing the design of the application.

Verifying the User interface of the application means how the front end design, colors,  fonts, font sizes, Labels, Text format, Text boxes, Captions, Radio Buttons, buttons, list boxes, Alignments, icons, links, popup, content, tabbing is provided to move between the objects, background, foreground etc  are displayed as specified.
GUI testing is functional testing - ensuring that all interactions, navigation, links, pop-ups, content, etc all work as required.

CONTENTS:-
Section 1 - Windows Compliance Standards
1.1. Application
1.2. For Each Window in the Application
1.3. Text Boxes
1.4. Option (Radio Buttons)
1.5. Check Boxes
1.6. Command Buttons
1.7. Drop Down List Boxes
1.8. Combo Boxes
1.9. List Boxes
Section 2 - Tester's Screen Validation Checklist

2.1. Aesthetic Conditions
2.2. Validation Conditions
2.3. Navigation Conditions
2.4. Usability Conditions
2.5. Data Integrity Conditions
2.6. Modes (Editable Read-only) Conditions
2.7. General Conditions
2.8. Specific Field Tests
2.8.1. Date Field Checks
2.8.2. Numeric Fields
2.8.3. Alpha Field Checks
Section 3 - Validation Testing - Standard Actions

3.1. On every Screen
3.2. Shortcut keys / Hot Keys
3.3. Control Shortcut Keys
Section 4 - Origin & Inspiration
4.1. Document origin
4.2. Sources of Inspiration & information
4.3. Contacting the author.

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.

·         Behavior 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 behavior.

·         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, Testing Geek will discuss information about field specific tests and usage of shortcuts in the application GUI.