Checklist Followed while testing UI

This checklist has been divided into parts and each part contains complete description of how to test the important points of a specific functionality. The general properties of all the functionalities will be covered in General topic. 1. Button:Important properties to be covered for buttons:1. Active/Inactive (Check it in accordance with the spec). 2. Existence of the Button (Sometimes the specified button will not be visible in GUI). 3. To check the Caption and work related to Caption. For e.g. Submit, Save, Ok, Cancel, Reset etc. 4. 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.

5. 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 HotKeys. Make sure there is no duplication. 6. The below are VERY IMPORTANT, and should be done for EVERY command Button. 1. Click each button once with the mouse - This should activate. 2. Tab to each button - Press SPACE - This should activate. 3. Tab to each button - Press RETURN - This should activate. 7. If pressing the Command button results in uncorrectable data e.g. closing an action step, there should be a message phrased positively with Yes/No answers where Yes results in the completion of the action. 8. When a button is used sometimes and not at other times, assures that it is grayed out when it should not be used. 9. Check Active/Inactive state of the Buttons in accordance with the spec.

2. Radio Button:-

Important Properties to be covered for Radio Buttons:1. Multiple selections can not be done. 2. There should be a default selected option (In this case Option1 is default selected option as per design) 3. Check Enable/Disable property of the Radio Buttons in accordance with the spec. 4. Check the navigation using TAB button, Tab should select the radio button which has got next tab index. 5. Selecting an option from the list might dynamically generate some more options to select. If this is the case it will be specified in the spec.

3. Checkbox:-

Important Properties to be covered for Checkbox:1. Clicking with the mouse on the box, or on the text should SET/UNSET the box. Check the same functionality using SPACEBAR. 2. Multiple selections are allowed. 3. Default selection (Check this in accordance with the spec). 4. Grayed property (Check third option, this is SET and grayed, this is a kind of default selection property, if desired we can UNSET this option). 5. Blur Property (This property depends on the spec, for example, if an option is selected that will blur (Make inactive user can neither SET/UNSET the checkbox) one or more checkboxes).

4. Text Field:Important Properties to be covered for Text Field:1. Move the Mouse Cursor over all Enterable Text Boxes. Cursor should change from arrow to Insert Bar. If it doesn't then the text in the box should be grey or nonupdateable. 2. Enter text into Box: 1. Try to overflow the text by typing too many characters - should be stopped. 2. Check the field width with capitals W. 3. Enter invalid characters - Letters in integer fields, try special characters like +, -, * etc. in all fields as per spec. 4. SHIFT and Arrow should Select Characters. Selection should also be possible with mouse. Double Click should select all text in box. 3. Maximum length of characters (Can be checked in design document). 4. Minimum length (Same as above). 5. Check the alignment of the text (Say for example, a text field is of 10 character length and the text you want to type is of 20 character length, after entering 10 characters the characters should start moving to right such that the character entered after 10th character should be visible).

5. Text Area:Important Properties to be covered for Text Area:1. Default Value (There could be a default value specified to the field as per spec). 2. Length of the characters should be definite, and the spec should clearly mention the boundary values (Min (if the field is mandatory field, such that the field is not left with null value) and Max). 3. Maximum characters (For example, in the spec it is specified that max of 300 characters can be entered in the text area then the text area should not accept characters more than 300).

6. Combo Box:-

Important Properties to be covered for Combo box:1. Should editable/non-editable depending on the spec. 2. Clicking Arrow should allow user to choose from list. 3. Selecting a value from the list might not be the same value that has entered in the Database (For example, say Number1 is selected from the list above, due to error in the code the value for the caption Number1 is different, say Number2, then by selecting Number1 will result in updating the DB with incorrect value, so check the value in the DB). 4. Sometimes if user selects a value then some more buttons will appear dynamically at runtime (This will happen depending on the spec and we should be ready to handle this).

7. Scroll Bar:-

Important Properties to be covered for Scroll Bar:1. Horizontal scroll bar should be restricted (Most of the time this convention is followed, that horizontal scroll bar should not appear until and unless agreed upon with the client). 2. When the window is resized then the horizontal scroll bar should appear (this case is not always applicable as some windows will have dynamic objects which will resize to the extent to fit exactly in the window. For example check this functionality with Solitaire game). 3. There is no such convention for the vertical bar.

8. ListBox:-

Important Properties to be covered for List Box:-

1. Should allow a multiple selection to be chosen, by clicking with the mouse, or using the
Up and Down Arrow keys. 2. Pressing a letter should take you to the first item in the list starting with that letter. 3. If there is a 'View' or 'Open' button beside the list box then double clicking on a line in the List Box, should act in the same way as selecting and item in the list box, then clicking the command button. 4. Force the scroll bar to appear, make sure all the data can be seen in the box. 5. List boxes are always white background with black text whether they are disabled or not. All others are grey. 6. If 8 or less options in a list box, display all options on open of list box - should be no need to scroll

9. Boundary Conditions:For example take integer text box that has, 1. Max length is 100. 2. Min length is 1. Say as per design document. Then the boundary value condition will be, Max: - 101, 100, 99 Min: - 0, 1, 2 For the above example 0 and 101 are not valid numbers. In the case of text field the length will be restricted not the value. Say for example for a text field the boundary values are given as 1 and 3. The valid inputs it will take are 1, 9, 11, 99, 111, 999, a, ab, abc etc.. . In this case the field will accept 111 and 999 because there is no restriction for the value in the field and the max length is specified as 3.

General things that need to be taken care before starting a GUI application:1. WINDOWS COMPLIANCE TESTING:-

Start Application by Double Clicking on its ICON. The Loading message should show the application name, version number, and a bigger pictorial representation of the icon. Closing the application should result in a confirmation message box. Attempt to start application Twice (This should not be allowed and a proper message should appear). All screens should have a Help button; F1 should work doing the same. If Window has a Minimize Button, click it. (Window should return to taskbar on the bottom of the screen and click the Icon to return the Window to its original size). If window has a close button, click it. (User should be prompt with a confirmation message Are you sure, clicking on Yes button on the message box should close the application and clicking on No will restore the application). The window caption for every application should have the name of the application and the window name - especially the error messages.

The application should be checked for spelling, English and clarity, especially on the top of the screen. Check does the title of the window make sense. Check all text on window for Spelling/Tense and Grammar. Use TAB to move focus around the Window. Use SHIFT+TAB to move focus backwards (Tab order should be left to right, and Up to Down within a group box on the screen). All controls should get focus - indicated by dotted box, or cursor. Tabbing to an entry field with text in it should highlight the entire text in the field. If a field is disabled (grayed) then it should not get focus. It should not be possible to select them with either the mouse or by using TAB. Try this for every grayed control.

2. Screen Validation Checklist:Aesthetic Conditions:

Is the general screen background is of correct color? Are the field prompts to correct color? Are the field backgrounds are of correct color? Are all the screens prompts specified in the correct screen font? Is the text in all fields specified in the correct screen font? Are all the fields aligned perfectly on the screen? Are all the fields spelt correctly? Are all the micro-helps text spelt correctly on this screen? Is all the error message text spelt correctly on this screen? Assure that all windows and dialog boxes have a consistent look and feel.

Validation Conditions: Does a failure of validation on every field cause a sensible user error message? Have any fields got multiple validation rules and if so are all rules being applied? 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? For all numeric fields check whether negative numbers can and should be able to be entered. For all numeric fields check the minimum and maximum values and also some mid-range values allowable? 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? If any of the database columns dont 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.) Navigation Conditions: Can the screen be accessed correctly from the menu and Toolbar? Can a number of instances of this screen be opened at the same time and is this correct? General Conditions:-

Assure the existence of the "Help" menu. In drop down list boxes, assure that the list and each entry in the list can be accessed via appropriate key / hot key combinations. Assure that the Cancel button operates as a Close button when changes have been made that cannot be undone. All fonts to remain 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.