Skip to main content

Screen Validation Checklist

Along with compliance standard, aesthetic, navigation, usability etc also plays an important role in the GUI Testing and development. This checklist will help you get started with what should be tested as part of GUI testing.

  1. Aesthetic Conditions
    1. Is the general screen background the correct color?
    2. Are the field prompts the correct color?
    3. Are the field backgrounds the correct color?
    4. In read-only mode, are the field prompts the correct color?
    5. In read-only mode, are the field backgrounds the correct color?
    6. Is 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 the entire field prompts aligned perfectly on the screen?
    9. Are all the field edits boxes aligned perfectly on the screen?
    10. Are all group boxes aligned correctly on the screen?
    11. Should the screen be resizable?
    12. Should the screen be minimisable?
    13. Are the entire 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 micro help text spelt correctly on this screen?
    17. Is all the error message text spelt correctly on this screen?
    18. Is all users 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. 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.)
  1. 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? 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?
  1. 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 micro help 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. 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.

  3. Modes Conditions (Editable / Read Only)
    1. Are the screen and field colors 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.
  1. 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 command.
    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 been 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, assures 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
    1. Alt+F4 should close the tabbed window and return to previous screen

Comments

Post a Comment

Popular posts from this blog

SQL SERVER Questions And Answers

SQL SERVER Questions And Answers 1. What is an Entity? The basic data item stored in database is called entity. An entity can be any object, item, place, person, concept, or activity about which data is stored. 2. What is an attribute? An attribute is a property of an entity. It describes a part of an entity. Entity could have one or more attributes. 3. What is ER diagram? An Entity Relationship Diagram is diagrammatic representation of the logical structure of a database system. 4. Describe the concept of keys. Candidate key An attribute that uniquely identifies a row is called candidate key. It is also called das surrogate key. Primary key A candidate key that you choose to identify rows uniquely is called a primary key. Alternate key If there are multiple candidate keys in a table, the candidate keys that are chosen as primary key are called the alternate keys. Composite key When the key that uniquely identifies the rows of a table is made up of more than one attribute, it is ca...
Post a Comment
Read more

Testing Measurement

Someone has rightly said that if something can not be measured, it can not be managed or improved. There is huge value in measurement, but you should always make sure that you get some value out of any measurement that you are doing. You should be able to answer the following questions: What is the purpose of this measurement program? What data items you are collecting and how you are reporting it? What is the correlation between the data and conclusion? Value addition: Any measurement program can be divided into two parts. The first part is to collect data, and the second is to prepare metrics/chart and analyses them to get the valuable insight which might help in decision making. Information collected during any measurement program can help in: Finding the relation between data points, Correlating cause and effect, Input of future planning. Normally, any metric program involves certain steps which are repeated over a period of time. It starts with identifying what to measure. After t...
Post a Comment
Read more

What’s New with QTP 9.5?

This is the general overview giving the brief description of what is new in QTP9.5 New Features: 1.  New design time panes: Various new IDE panes have been introduced which does not provide any new functionality to add up but basically the operations which were in the deep sub menus are now put up in front. Available Keyword Pane: This pane shows all the available functions in the current test (either in-action or externally added), as well as all the objects in your object repository (local and external). The items are effectively separated into groups, making it easier to search for a relevant item. Double clicking any item in the pane will open it, and dragging the item to the main window will add it to the script in the drop position. Double clicking a function will not only open the hosting file in the main window, but also focus on the exact position of the function within the file. Test Flow Pane: This pane lays out the action call structure of the current test. It outlines...
Post a Comment
Read more