Test engineers testing the user interface for web application is slightly different from testing user interface of traditional applications. Irrespective of the web application there are certain things which should be tested for every web application. As soon as first release happened, Many of test engineer performs adhoc testing (without authoring GUI test cases) to ensure that application is right. If you do not have GUI test cases, none of the managers will agree to give enough time to compare between prototype and application and filing defects into defect tracking system. If you design GUI test cases and show case to manger to get sufficient time for preparation, execution, defect reporting and validation. Easy to measure GUI test case coverage and mapping defects to test cases.
Following the attached matrix template will give some information on items that should be tested to ensure quality of the user interface of your web application. The attached sheet contains field level and page level GUI test cases. Simply you need to create multiple sheets in the same workbook by copying the sheet. Change the sheet name to page name appears in the application. Finally based on your application prototype/screenshot/blue print of application, fill each row against each item listed under column A. During execution of GUI test cases
Note: Do not replace the field1, field2, field 3 columns. Third row is meant for specifying the field names.
Purpose of this GUI Testing Checklist is to help you understand how your application can be tested according to the known and understood standards for GUI. This checklist can give some guidance to the development and QA, both the teams. Development team can make sure that during the development they follow guidelines related to the compliance, aesthetics, navigation etc. but onus of testing GUI is on the QA team and as a tester it is your responsibility to validate your product against GUI standards followed by your organization.
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.