:: QC Boss :: Testing, Independent Software Testing, Manual Testing, Website Testing, Functionality Testing, Usability Testing, QC, QA, UAT

Basic Checklist of GUI Testing

leave a comment »

  1. Test each toolbar and menu item for navigation using the mouse and keyboard.
  2. Test window navigation using the mouse and keyboard.
  3. Check  that proper formatted masks are used. i.e., the drop-down boxes should be sorted.
  4. Date entry should also be properly formatted and sorted.
  5. Make sure to check the colors, fonts, and font widths are to standard for the field alerts and displayed text.
  6. Test that the color of the field prompts and field background is to standard in read-only mode.
  7. Make sure that vertical scroll bars or horizontal scroll bars do not appear unless required.
  8. Test that the various controls on the window are aligned correctly.
  9. Make sure that the window is resizable.
  10. Check the spellings of all the text displayed in the window, such as the window caption, status bar options, field prompts, pop-up text, and error messages.
  11. Test that all character or alphanumeric fields are left-justified and that the numeric fields are right-justified.
  12. Check for the display of defaults if there are any.
  13. In case of multiple pages or windows, check that they all have the same look and feel.
  14. Check that all shortcut keys are defined and work correctly.
  15. Check for the tab order. It should be from top left to bottom right. Also, the read-only/disabled fields should be avoided in the TAB sequence.
  16. Check that the cursor is positioned on the first input field when the window is opened.
  17. Make sure if any default button is specified, it should work properly.
  18. Check for proper functioning of ALT+TAB.
  19. Ensure that each menu command has an alternative hot key sequence and that it works correctly.  
  20. Check that there are no duplicate hot keys defined on the window.
  21. Validate the behavior of each control, such as push button, radio button, list box, and so on.
  22. Test to make sure that the window is modal. This will prevent the user from accessing other functions when this window is active.
  23. Test that multiple windows can be opened at the same time.
  24. Check to make sure that there is a Help menu.
  25. Check to make sure that the command buttons are grayed out when not in use.

Written by QCBoss

November 20, 2008 at 5:32 am

Posted in Software Testing

Tagged with

Leave a Reply

You must be logged in to post a comment.