Web check list

Gui testing checklist a checklist to help testers check gui screens 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. 4.4. Download this file => .pdf section 1 - windows compliance testing 1.1. Application 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 (a 'splash' screen). No login is necessary the main window of the application should have the same caption as the caption of the icon in program manager. Closing the application should result in an "are you sure" message box attempt to start application twice this should not be allowed - you should be returned to main window try to start the application twice as it is loading. On each window, if the application is busy, then the hour glass should be displayed. If there is no hour glass (e.g. Alpha access enquiries) then some enquiry in progress message should be displayed. All screens should have a help button, f1 should work doing the same. 1.2. For each window in the application if window has a minimise button, click it. Window should return to an icon on the bottom of the screen this icon should correspond to the original icon under program manager. Double click the icon to return the window to its original size. The window caption for every application should have the name of the application and the window name - especially the error messages. These should be checked for spelling, english and clarity , especially on the top of the screen. Check does the title of the window makes sense. If the screen has an control menu, then use all ungreyed options. (see below) 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. The text in the micro help line should change - check for spelling, clarity and non-updateable etc. If a field is disabled (greyed) 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 greyed control. Never updateable fields should be displayed with black text on a grey background with a black label. All text should be left-justified, followed by a colon tight to it. In a field that may or may not be updateable, the label text and contents changes from black to grey depending on the current status. List boxes are always white background with black text whether they are disabled or not. All others are grey. In general, do not use goto screens, use gosub, i.e. If a button causes another screen to be displayed, the screen should not hide the first screen, with the exception of tab in 2.0 when returning return to the first screen cleanly i.e. No other screens/applications should appear. In general, double-clicking is not essential. In general, everything can be done using both the mouse and the keyboard. All tab buttons should have a distinct letter. 1.3. Text boxes 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 non-updateable. Refer to previous page. Enter text into box try to overflow the text by typing to many characters - should be stopped check the field width with capitals w. Enter invalid characters - letters in amount fields, try strange characters like + , - * etc. In all fields. Shift and arrow should select characters. Selection should also be possible with mouse. Double click should select all text in box. 1.4. Option (radio buttons) left and right arrows should move 'on' selection. So should up and down.. Select with mouse by clicking. 1.5. Check boxes clicking with the mouse on the box, or on the text should set/unset the box. Space should do the same. 1.6. Command buttons 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. 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. 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 the above are very important, and should be done for every command button. Tab to another type of control (not a command button). One button on the screen should be default (indicated by a thick black border). Pressing return in any no command button control should activate it. If there is a cancel button on the screen , then pressing <esc> should activate it. 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. 1.7. Drop down list boxes pressing the arrow should give list of options. This list may be scrollable. You should not be able to type text in the box. Pressing a letter should bring you to the first item in the list with that start with that letter. Pressing ‘ctrl - f4’ should open/drop down the list box. Spacing should be compatible with the existing windows spacing (word etc.). Items should be in alphabetical order with the exception of blank/none which is at the top or the bottom of the list box. Drop down with the item selected should be display the list with the selected item on the top. Make sure only one space appears, shouldn't have a blank line at the bottom. 1.8. Combo boxes should allow text to be entered. Clicking arrow should allow user to choose from list 1.9. List boxes should allow a single selection to be chosen, by clicking with the mouse, or using the up and down arrow keys. Pressing a letter should take you to the first item in the list starting with that letter. 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. Force the scroll bar to appear, make sure all the data can be seen in the box. Section 2 - screen validation checklist 2.1. Aesthetic conditions: 1. Is the general screen background the correct colour? 2. Are the field prompts the correct colour? 3. Are the field backgrounds the correct colour? 4. In read-only mode, are the field prompts the correct colour? 5. In read-only mode, are the field backgrounds the correct colour? 6. Are all the screen prompts specified in the correct screen font? 7. Is the text in all fields specified in the correct screen font? 8. Are all the field prompts aligned perfectly on the screen? 9. Are all the field edit boxes aligned perfectly on the screen? 10. Are all groupboxes aligned correctly on the screen? 11. Should the screen be resizable? 12. Should the screen be minimisable? 13. Are all the field prompts spelt correctly? 14. Are all character or alpha-numeric fields left justified? this is the default unless otherwise specified. 15. Are all numeric fields right justified? this is the default unless otherwise specified. 16. Is all the microhelp text spelt correctly on this screen? 17. Is all the error message text spelt correctly on this screen? 18. Is all user input captured in upper case or lower case consistently? 19. Where the database requires a value (other than null) then this should be defaulted into fields. The user must either enter an alternative valid value or leave the default value intact. 20. Assure that all windows have a consistent look and feel. 21. Assure that all dialog boxes have a consistent look and feel. 2.2. Validation conditions: 1. Does a failure of validation on every field cause a sensible user error message? 2. Is the user required to fix entries which have failed validation tests? 3. Have any fields got multiple validation rules and if so are all rules being applied? 4. 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.? 5. Is validation consistently applied at screen level unless specifically required at field level? 6. For all numeric fields check whether negative numbers can and should be able to be entered. 7. For all numeric fields check the minimum and maximum values and also some mid-range values allowable? 8. 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? 9. Do all mandatory fields require user input? 10. 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.) 2.3. Navigation conditions: 1. Can the screen be accessed correctly from the menu? 2. Can the screen be accessed correctly from the toolbar? 3. Can the screen be accessed correctly by double clicking on a list control on the previous screen? 4. Can all screens accessible via buttons on this screen be accessed correctly? 5. Can all screens accessible by double clicking on a list control be accessed correctly? 6. Is the screen modal. I.e. Is the user prevented from accessing other functions when this screen is active and is this correct? 7. Can a number of instances of this screen be opened at the same time and is this correct? 2.4. Usability conditions: 1. Are all the dropdowns on this screen sorted correctly? alphabetic sorting is the default unless otherwise specified. 2. Is all date entry required in the correct format? 3. Have all pushbuttons on the screen been given appropriate shortcut keys? 4. Do the shortcut keys work correctly? 5. Have the menu options which apply to your screen got fast keys associated and should they have? 6. Does the tab order specified on the screen go in sequence from top left to bottom right? this is the default unless otherwise specified. 7. Are all read-only fields avoided in the tab sequence? 8. Are all disabled fields avoided in the tab sequence? 9. Can the cursor be placed in the microhelp text box by clicking on the text box with the mouse? 10. Can the cursor be placed in read-only fields by clicking in the field with the mouse? 11. Is the cursor positioned in the first input field or control when the screen is opened? 12. Is there a default button specified on the screen? 13. Does the default button work correctly? 14. When an error message occurs does the focus return to the field in error when the user cancels it? 15. When the user alt+tab's to another application does this have any impact on the screen upon return to the application? 16. 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 2.5. Data integrity conditions: 1. Is the data saved when the window is closed by double clicking on the close box? 2. Check the maximum field lengths to ensure that there are no truncated characters? 3. Where the database requires a value (other than null) then this should be defaulted into fields. The user must either enter an alternative valid value or leave the default value intact. 4. Check maximum and minimum field values for numeric fields? 5. 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? 6. If a set of radio buttons represent a fixed set of values such as a, b and c then what happens if a blank value is retrieved from the database? (in some situations rows can be created on the database by other functions which are not screen based and thus the required initial values can be incorrect.) 7. If a particular set of data is saved to the database check that each value gets saved fully to the database. I.e. Beware of truncation (of strings) and rounding of numeric values. 2.6. Modes (editable read-only) conditions: 1. Are the screen and field colours adjusted correctly for read-only mode? 2. Should a read-only mode be provided for this screen? 3. Are all fields and controls disabled in read-only mode? 4. Can the screen be accessed from the previous screen/menu/toolbar in read-only mode? 5. Can all screens available from this screen be accessed in read-only mode? 6. Check that no validation is performed in read-only mode. 2.7. General conditions: 1. Assure the existence of the "help" menu. 2. Assure that the proper commands and options are in each menu. 3. Assure that all buttons on all tool bars have a corresponding key commands. 4. Assure that each menu command has an alternative(hot-key) key sequence which will invoke it where appropriate. 5. In drop down list boxes, ensure that the names are not abbreviations / cut short 6. In drop down list boxes, assure that the list and each entry in the list can be accessed via appropriate key / hot key combinations. 7. Ensure that duplicate hot keys do not exist on each screen 8. 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" 9. Assure that the cancel button functions the same as the escape key. 10. Assure that the cancel button operates as a close button when changes have be made that cannot be undone. 11. 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. 12. When a command button is used sometimes and not at other times, assure that it is grayed out when it should not be used. 13. Assure that ok and cancel buttons are grouped separately from other command buttons. 14. Assure that command button names are not abbreviations. 15. Assure that all field labels/names are not technical labels, but rather are names meaningful to system users. 16. Assure that command buttons are all of similar size and shape, and same font & font size. 17. Assure that each command button can be accessed via a hot key combination. 18. Assure that command buttons in the same window/dialog box do not have duplicate hot keys. 19. 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 20. Assure that focus is set to an object/button which makes sense according to the function of the window/dialog box. 21. Assure that all option buttons (and radio buttons) names are not abbreviations. 22. Assure that option button names are not technical labels, but rather are names meaningful to system users. 23. If hot keys are used to access option buttons, assure that duplicate hot keys do not exist in the same window/dialog box. 24. Assure that option box names are not abbreviations. 25. Assure that option boxes, option buttons, and command buttons are logically grouped together in clearly demarcated areas "group box" 26. Assure that the tab key sequence which traverses the screens does so in a logical way. 27. Assure consistency of mouse actions across windows. 28. Assure that the color red is not used to highlight active objects (many individuals are red-green color blind). 29. Assure that the user will have control of the desktop with respect to general color and highlighting (the application should not dictate the desktop background characteristics). 30. Assure that the screen/window does not have a cluttered appearance 31. Ctrl + f6 opens next tab within tabbed window 32. Shift + ctrl + f6 opens previous tab within tabbed window 33. Tabbing will open next tab within tabbed window if on last field of current tab 34. Tabbing will go onto the 'continue' button if on last field of last tab within tabbed window 35. Tabbing will go onto the next editable field in the window 36. Banner style & size & display exact same as existing windows 37. If 8 or less options in a list box, display all options on open of list box - should be no need to scroll 38. 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) 39. Pressing continue while on the first tab of a tabbed window (assuming all fields filled correctly) will not open all the tabs. 40. On open of tab focus will be on first editable field 41. All fonts to be the same 42. 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. 43. Microhelp text for every enabled field & button 44. Ensure all fields are disabled in read-only mode 45. Progress messages on load of tabbed screens 46. Return operates continue 47. If retrieve on load of tabbed window fails window should not open 2.8. Specific field tests 2.8.1. Date field checks • assure that leap years are validated correctly & do not cause errors/miscalculations • assure that month code 00 and 13 are validated correctly & do not cause errors/miscalculations • assure that 00 and 13 are reported as errors • assure that day values 00 and 32 are validated correctly & do not cause errors/miscalculations • assure that feb. 28, 29, 30 are validated correctly & do not cause errors/ miscalculations • assure that feb. 30 is reported as an error • assure that century change is validated correctly & does not cause errors/ miscalculations • assure that out of cycle dates are validated correctly & do not cause errors/miscalculations 2.8.2. Numeric fields • assure that lowest and highest values are handled correctly • assure that invalid values are logged and reported • assure that valid values are handles by the correct procedure • assure that numeric fields with a blank in position 1 are processed or reported as an error • assure that fields with a blank in the last position are processed or reported as an error an error • assure that both + and - values are correctly processed • assure that division by zero does not occur • include value zero in all calculations • include at least one in-range value • include maximum and minimum range values • include out of range values above the maximum and below the minimum • assure that upper and lower values in ranges are handled correctly 2.8.3. Alpha field checks • use blank and non-blank data • include lowest and highest values • include invalid characters & symbols • include valid characters • include data items with first position blank • include data items with last position blank section 3 - validation testing - standard actions 3.1. Examples of standard actions - substitute your specific commands add view change delete continue - (i.e. Continue saving changes or additions) add view change delete cancel - (i.e. Abandon changes or additions) fill each field - valid data fill each field - invalid data different check box / radio box combinations scroll lists / drop down list boxes help fill lists and scroll tab tab sequence shift tab 3.2. Shortcut keys / hot keys note: the following keys are used in some windows applications, and are included as a guide. Key no modifier shift ctrl alt f1 help enter help mode n\a n\a f2 n\a n\a n\a n\a f3 n\a n\a n\a n\a f4 n\a n\a close document / child window. Close application. F5 n\a n\a n\a n\a f6 n\a n\a n\a n\a f7 n\a n\a n\a n\a f8 toggle extend mode, if supported. Toggle add mode, if supported. N\a n\a f9 n\a n\a n\a n\a f10 toggle menu bar activation. N\a n\a n\a f11, f12 n\a n\a n\a n\a tab move to next active/editable field. Move to previous active/editable field. Move to next open document or child window. (adding shift reverses the order of movement). Switch to previously used application. (holding down the alt key displays all open applications). Alt puts focus on first menu command (e.g. 'file'). N\a n\a n\a 3.3. Control shortcut keys key function ctrl + z undo ctrl + x cut ctrl + c copy ctrl + v paste ctrl + n new ctrl + o open ctrl + p print ctrl + s save ctrl + b bold* ctrl + i italic* ctrl + u underline* * these shortcuts are suggested for text formatting applications, in the context for which they make sense. Applications may use other modifiers for these operations. Download this in pdf format 4. Origin & inspiration i first conceived this checklist for training testers who were going to be working on a new powerbuilder application (on a windows for workgroups platform) to be used in the initial screen validation testing phase. The initial input for the list came from a site i found on the web, (see below) the remainder of the checklist i made up from internal & external design standards, and experience gained over the last few years working in qa. A long ago i replied to a query (on comp.software.testing) regarding gui/client-server testing and when i mentioned this checklist i got quite a few requests for copies, and as a result i decided to publish it on the web. I hope it can be of some use to you, and if you have any suggestions - or if anyone wants to update this to win95/98/nt/xp standards (or even mac) i'd love if they'd send me a copy !