GUI Testing

Definition: Graphical User Interface testing is the process of testing a product's graphical user interface to ensure it meets its written specifications. It tells us how the application interacts with user through its user Interface.

GUI testing involves carrying set of tasks and comparing the result of same with the expected output and ability to repeat same set of tasks multiple times with different data input and same level of accuracy. GUI Testing includes how the application handles keyboard and mouse events, how different GUI components like menu bars, toolbars, dialogs, buttons, edit fields, list controls, images etc. reacts to user input and whether or not it performs in the desired manner.

Or

GUI testing is a process to test application's user interface and to make sure that it confirms the design requirements

1. Text Box

a. Move the Mouse Cursor over all Enterable Text Boxes. Cursor should change from arrow to Insert Bar.

b. If it doesn't then the text in the box should be grey or non-updateable.

c. Try to overflow the text by typing to many characters.

d. Enter invalid characters - Letters in amount fields, try strange characters like + , - * etc. in All fields.

e. SHIFT and Arrow should Select Characters. Selection should also be possible with mouse. Double Click should select all text in box.

 2. Radio Button

Left and Right arrows should move ON Selection. So should Up and Down. Select with mouse by clicking.

Check Boxes: Clicking with the mouse on the box, or on the text should SET/UNSET the box. SPACE should do the same.

 3. Command Buttons

a. If Command Button leads to another Screen, and if the user can enter or change details on the other screen then the Text on the button should be followed by three dots.

b. All Buttons except for OK and 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+Letter. Make sure there is no duplication.

c. Click each button once with the mouse - This should activate

Tab to each button - Press SPACE - This should activate

Tab to each button - Press RETURN - This should activate

d. If there is a Cancel Button on the screen , then pressing should activate it.

 4. Aesthetic Conditions

a. Is the general screen background the correct colour?

b. Are the field prompts the correct colour?

c. Are the field backgrounds the correct colour?

d. In read-only mode, are the field prompts the correct colour?

e. In read-only mode, are the field backgrounds the correct colour?

f. Are all the screen prompts specified in the correct screen font?

g. Is the text in all fields specified in the correct screen font?

h. Are all the field prompts aligned perfectly on the screen?

i. Are all the field edit boxes aligned perfectly on the screen?

j. Should the screen be resizable?

k. Should the screen be minimizable?

l. Is all user input captured in UPPER case or lower case consistently?

5. Validation Conditions

a. Does a failure of validation on every field cause a sensible user error message?

b. Is the user required to fix entries which have failed validation tests?

c. Have any fields got multiple validation rules and if so are all rules being applied?

d. If the user enters an invalid value and clicks on the OK button (i.e. does not TAB off the field) is the invalid entry identified and highlighted correctly with an error message.?

e. Is validation consistently applied at screen level unless specifically required at field level?

f. For all numeric fields check whether negative numbers can and should be able to be entered.

g. For all numeric fields check the minimum and maximum values and also some mid-range values allowable?

h. For all character/alphanumeric fields check the field to ensure that there is a character limit specified and that this limit is exactly correct for the specified database size?

i. Do all mandatory fields require user input?

j. If any of the database columns don't allow null values then the corresponding screen fields must be mandatory. (If any field which initially was mandatory has become optional then check whether null values are allowed in this field.)

 

6. Usability Conditions

a. Is all date entry required in the correct format?

b. When an error message occurs does the focus return to the field in error when the user cancels it?

c. Do all the fields edit boxes indicate the number of characters they will hold by there length? e.g. a 30 character field should be a lot longer

 

7. Data Integrity Conditions

a. Check the maximum field lengths to ensure that there are no truncated characters?

b. Check maximum and minimum field values for numeric fields?

c. If numeric fields accept negative values can these be stored correctly on the database and does it make sense for the field to accept negative numbers?

 

8. Date Field Checks

a. Assure that leap years are validated correctly & do not cause errors/miscalculations

b. Assure that month code 00 and 13 are validated correctly & do not cause errors/miscalculations

c. Assure that 00 and 13 are reported as errors

d. Assure that day values 00 and 32 are validated correctly & do not cause errors/miscalculations

e. Assure that Feb. 28, 29, 30 are validated correctly & do not cause errors/ miscalculations

f. Assure that Feb. 30 is reported as an error

g. Assure that century change is validated correctly & does not cause errors/ miscalculations

 

9. Alpha Field Checks

a. Use blank and non-blank data

b. Include lowest and highest values

c. Include invalid characters & symbols

d. Include valid characters

e. Include data items with first position blank

f. Include data items with last position blank