GUI Testing Checklist

This GUI test checklist can ensure that all the GUI components are thoroughly tested. In the first part of this checklist, we will cover Windows compliance standard and some test ideas for field specific tests.

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

Compliance for each application

• Application should be started by double clicking on the icon.
• Loading message should have information about application name, version number, icon etc.
• Main window of application should have same caption as the icon in the program manager.
• Closing of the application should result in “Are you sure?” message.
• Behaviour for starting application more than once must be specified.
• Try to start application while it is loading
• On every application, if application is busy it should show hour glass or some other mechanism to notify user that it is processing.
• Normally F1 button is used for help. If your product has help integrated, it should come by pressing F1 button.
• Minimize and restoring functionality should work properly
• Compliance for each window in the application
• Window caption for every application should have application name and window name. Specially, error messages.
• Title of the window and information should make sense to the user.
• If screen has control menu, use the entire control menu like move, close, resize etc.
• Text present should be checked for spelling and grammar.
• If tab navigation is present, TAB should move focus in forward direction and SHIFT+TAB in backward direction.
• Tab order should be left to right and top to bottom within a group box.
• If focus is present on any control, it should be presented by dotting lines around it.
• User should not be able to select greyed or disabled control. Try this using tab as well as mouse.
• Text should be left justified
• In general, all the operations should have corresponding key board shortcut key for this.
• All tab buttons should have distinct letter for it.

Text boxes

• Move mouse to textbox and it should be changed to insert bar for editable text field and should remain unchanged for non-editable text field.
• Test overflowing textbox by inserting as many characters as you can in the text field. Also test width of the text field by entering all capital W.
• Enter invalid characters, special characters and make sure that there is no abnormality.
• User should be able to select text using Shift + arrow keys.
• Selection should be possible using mouse and double click should select entire text in the text box.

Radio Buttons

• Only one should be selected from the given option.
• User should be able to select any button using mouse or key board
• Arrow key should set/unset the radio buttons.

Check boxes

• User should be able to select any combination of checkboxes
• Clicking mouse on the box should set/unset the checkbox.
• Spacebar should also do the same

Push Buttons

• All buttons except OK/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
• Clicking each button with mouse should activate it and trigger required action.
• Similarly, after giving focus SPACE or RETURN button should also do the same.
• If there is any Cancel button on the screen, pressing Esc should activate it.

Drop down list boxes

• Pressing the arrow should give list of options available to the user. List can be scrollable but user should not be able to type in.
• Pressing Ctrl-F4 should open the list box.
• Pressing a letter should bring the first item in the list starting with the same letter.
• Items should be in alphabetical order in any list.
• Selected item should be displayed on the list.
• There should be only one blank space in the dropdown list.

Combo Box

• Similar to the list mentioned above, but user should be able to enter text in it.

List Boxes

• Should allow single select, either by mouse or arrow keys.
• Pressing any letter should take you to the first element starting with that letter
• If there are view/open button, double clicking on icon should be mapped to these behaviour.
• Make sure that all the data can be seen using scroll bar.

Hope this checklist will help you in testing your GUI components in a better way. In next template, TestingGeek will discuss information about field specific tests and usage of shortcuts in the application GUI.

Security Testing Checklist

Here is one Security Testing Checklist that may help you all:

1. Are all the Internet-facing servers within the system registered with the corporate web office?

2. Do the test plans for the system include tests to verify that security functionality has been properly
implemented?

3. If the system is rated high on the business effect assessment or if it is Internet facing, has the
company security office been consulted to determine whether or not additional security testing
is required?

4. Has the security test covered the following?
a. application testing
b. back doors in code
c. denial of service testing
d. directory permissions
e. document grinding (electronic waste research)
f. exploit research
g. firewall and application control list
h. intrusion detection systems
i. manual vulnerability testing and verification
j. network surveying
k. password cracking
l. PBX testing
m. port scanning
n. privacy review
o. redundant automated vulnerability scanning
p. review of IDS and server logs
q. security policy review
r. services probing
s. social engineering
t. system fingerprinting
u. trusted systems testing
v. user accounts
w. wireless leak tests

Website Testing Checklist

Website Testing Checklist

1.1  LINKS

1.1.1 Check that the link takes you to the page it said it would.
1.1.2 Ensure to have no orphan pages (a page that has no links to it)
1.1.3 Check all of your links to other websites
1.1.4 Are all referenced web sites or email addresses hyperlinked?
1.1.5 If we have removed some of the pages from our own site, set up a custom 404 page that redirects your visitors to your home page (or a search page) when the user try to access a page that no longer exists.
1.1.6 Check all mailto links and whether it reaches properly

1.2 FORMS

1.2.1 Acceptance of invalid input
1.2.2 Optional versus mandatory fields
1.2.3 Input longer than field allows
1.2.4 Radio buttons
1.2.5 Default values on page load/reload(Also terms and conditions should be disabled)
1.2.6 Is Command Button can be used for HyperLinks and Continue Links ?
1.2.6 Is all the datas inside combo/list box are arranged in chronolgical order?
1.2.7 Are all of the parts of a table or form present? Correctly laid out? Can you confirm that selected texts are in the “right place?
1.2.8 Does a scrollbar appear if required?

1.3  DATA VERIFICATION AND VALIDATION

1.3.1 Is the Privacy Policy clearly defined and available for user access?
1.3.2 At no point of time the system should behave awkwardly when an invalid data is fed
1.3.3 Check to see what happens if a user deletes cookies while in site
1.3.4 Check to see what happens if a user deletes cookies after visiting a site
2. APPLICATION SPECIFIC FUNCTIONAL REQUIREMENTS

2.1 DATA INTEGRATION

2.1.1 Check the maximum field lengths to ensure that there are no truncated characters?
2.1.2 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?
2.1.3 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.2 DATE FIELD CHECKS

2.2.1 Assure that leap years are validated correctly & do not cause errors/miscalculations.
2.2.2 Assure that Feb. 28, 29, 30 are validated correctly & do not cause errors/ miscalculations.
2.2.3 Is copyright for all the sites includes Yahoo co-branded sites are updated

2.3 NUMERIC FIELDS

2.3.1 Assure that lowest and highest values are handled correctly.
2.3.2 Assure that numeric fields with a blank in position 1 are processed or reported as an error.
2.3.3 Assure that fields with a blank in the last position are processed or reported as an error an error.
2.3.4 Assure that both + and – values are correctly processed.
2.3.5 Assure that division by zero does not occur.
2.3.6 Include value zero in all calculations.
2.3.7 Assure that upper and lower values in ranges are handled correctly. (Using BVA)

2.4 ALPHANUMERIC FIELD CHECKS

2.4.1 Use blank and non-blank data.
2.4.2 Include lowest and highest values.
2.4.3 Include invalid characters & symbols.
2.4.4 Include valid characters.
2.4.5 Include data items with first position blank.
2.4.6 Include data items with last position blank.