Skip to main content

GUI Testing Checklist - 1

Purpose of this GUI Testing Checklist is to make sure that GUI of all the applications at <XYZ Organization> are developed and tested according to the known and understood standard. This checklist can give some guidance to the development team as well as QE team. Development team should make sure that during the development they follow guidelines related to the compliance, aesthetics, navigation etc. Onus of testing GUI is on the QE team. Appropriate defect should be raised in the <DTS> system, indicating defect and other relevant information.

This GUI test checklist will ensure that all the GUI components are thoroughly tested. This checklist is categorized according to the following sub-sections –

  • Windows compliance standards
  • Validation checklist for tester
  • Field specific test
  • Short-cut keys and hot keys

Windows Compliance Standards

These compliance standards are followed by almost all the windows based application. Any variance from these standards can result into inconvenience to the user. This compliance must be followed for every application. These compliances can be categorized according to following criteria


  1. Compliance for each application
    1. Application should be started by double clicking on the icon.
    2. Loading message should have information about application name, version number, icon etc.
    3. Main window of application should have same caption as the icon in the program manager.
    4. Closing of the application should result in "Are you sure?" message.
    5. Behaviour for starting application more than once must be specified.
    6. Try to start application while it is loading
    7. On every application, if application is busy it should show hour glass or some other mechanism to notify user that it is processing.
    8. Normally F1 button is used for help. If your product has help integrated, it should come by pressing F1 button.
    9. Minimize and restoring functionality should work properly


  2. Compliance for each window in the application
    1. Window caption for every application should have application name and window name. Specially, error messages.
    2. Title of the window and information should make sense to the user.
    3. If screen has control menu, use the entire control menu like move, close, resize etc.
    4. Text present should be checked for spelling and grammar.
    5. If tab navigation is present, TAB should move focus in forward direction and SHIFT+TAB in backward direction.
    6. Tab order should be left to right and top to bottom within a group box.
    7. If focus is present on any control, it should be presented by dotting lines around it.
    8. User should not be able to select greyed or disabled control. Try this using tab as well as mouse.
    9. Text should be left justified
    10. In general, all the operations should have corresponding key board shortcut key for this.
    11. All tab buttons should have distinct letter for it.


To be continued…………

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