Website Test Plan template
QA checklist
This document will be used in creating a test plan for your site. Please complete it and forward to Jeanette Deetjen. This section should contain a comprehensive list of the features, which are to be tested.
Note: the list below is intended as a guideline. If this site contains additional content or functionality, it should be added to the Test Items list.
A. Site map
Site map has been prepared and a copy forwarded to QA
FORMCHECKBOX
yes FORMCHECKBOX
no
Additional comments: ________________________________________
Site map indicates what pages are included in the site and how each page can be accessed.
B. Text
Working deck / text documents have been forwarded to QA
FORMCHECKBOX
yes FORMCHECKBOX
no
Additional comments: ________________________________________
Are spelling, punctuation, grammar and syntax correct? Is the text readable? Is text formatted consistently, on the page and across the site? Do text links function correctly? Is text aligned correctly?
Text links have been properly noted, including destination
FORMCHECKBOX
yes FORMCHECKBOX
no
Additional comments: ________________________________________
Text links include the URL and the location (bookmark) on the page, if applicable
C. Images
Working deck, including images, has been forwarded to QA
FORMCHECKBOX
yes FORMCHECKBOX
no
Additional comments: ________________________________________
Working deck must include image names, links (if applicable) and destination.
Does the image display? Is the correct image displayed? Is the image clear? Has image content and placement been checked against the deck? Do image links function correctly? Does image load time compromise the site's usability. Are images rotating (if applicable)?
D. Tables
Does the page include any tables
FORMCHECKBOX
yes FORMCHECKBOX
no
Additional comments: ________________________________________
Is the information displayed readable? Are columns wide enough or does text wrap around? Are rows too high? If the table contains scroll bars do they function correctly?
E. Links
Should any links open pop up windows
FORMCHECKBOX
yes FORMCHECKBOX
no
If yes, is it clearly defined which links
FORMCHECKBOX
yes FORMCHECKBOX
no
Additional comments: ________________________________________
Are visited / unvisited links required to be a certain color
FORMCHECKBOX
yes FORMCHECKBOX
no
If yes, is this clearly defined
FORMCHECKBOX
yes FORMCHECKBOX
no
Additional comments: ________________________________________
Do links direct the user to the correct page? Is the page you are linking to found? Can users return to the previous page? Is the color of text link correct? Do active and visited links change color? If so, is color correct?
F. Forms
Does site contain any forms
FORMCHECKBOX
yes FORMCHECKBOX
no
If yes, is field validation required
FORMCHECKBOX
yes FORMCHECKBOX
no
If yes, has field requirements been forwarded to QA
FORMCHECKBOX
yes FORMCHECKBOX
no
Additional comments: ________________________________________
What is valid/invalid input for text areas? Can text fields accept numeric entries? Can numeric fields accept symbols? Are character limitation rules enforced? Do Submit and Reset buttons function? Can only one option box be selected from a group? Do check boxes, list boxes, drop down menus, scroll bars and arrows function correctly?
G. Applets
Does site contain any applications or applets
FORMCHECKBOX
yes FORMCHECKBOX
no
If yes, has logic flow been forwarded to QA
FORMCHECKBOX
yes FORMCHECKBOX
no
If yes, has error trapping matrix been forwarded to QA
FORMCHECKBOX
yes FORMCHECKBOX
no
Does application contain any calculated dates
FORMCHECKBOX
yes FORMCHECKBOX
no
If yes, will it require Y2K testing
FORMCHECKBOX
yes FORMCHECKBOX
no
Additional comments: ________________________________________
What is valid/invalid input for fields? Is user input verified against business rules? If so, is verification performed as specified in the Logic Flow? Does Error Handling perform as specified in the Error Trapping Matrix?
H. Operating systems
What operating systems are required for testing?
FORMCHECKBOX
Macintosh
FORMCHECKBOX
Windows NT
FORMCHECKBOX
Windows 95
FORMCHECKBOX
Windows 98
FORMCHECKBOX
Solaris
Additional comments: ________________________________________
I. Browser Configurations
What browsers are required for testing?
FORMCHECKBOX
Netscape
FORMCHECKBOX
Netscape
FORMCHECKBOX
IE
FORMCHECKBOX
IE
FORMCHECKBOX
IE
FORMCHECKBOX
AOL
Do browser defaults require certain settings?
FORMCHECKBOX
yes FORMCHECKBOX
no
Additional comments: ________________________________________
What specific browsers, if any, is the site designed for? Is it optimized for a particular browser(s)? How many separate browser configurations are required for testing?
J. Printing
Is user required to print the page (as in a form)
FORMCHECKBOX
yes FORMCHECKBOX
no
If yes, does form have a specific layout
FORMCHECKBOX
yes FORMCHECKBOX
no
If yes, has form layout been forwarded to QA
FORMCHECKBOX
yes FORMCHECKBOX
no
Additional comments: ________________________________________
Does the page allow for printing? If so, do you know the specifications? Are printed pages formatted correctly? Does all of the information, which should, display on the printed page?
K. Plug-ins
Does the site require any plug-ins
FORMCHECKBOX
yes FORMCHECKBOX
no
If yes, list plug-ins here: _________________________________
Additional comments: ________________________________________
Are any plug-ins required to view the page? How does the page behave if the plug-ins aren’t installed? Or the wrong plug-ins are installed?
L. Accessibility to people with disabilities
Is site required to be accessible to people with disabilities?
FORMCHECKBOX
yes FORMCHECKBOX
no
Additional comments: ________________________________________
Does site provide text equivalents for all non-text elements (., images, animations, audio, video)? Are there summaries of graphs and charts? Is all information conveyed with color also available without color? Are there alternative content for features (., applets or plug-ins) that may not be supported?
M. Multiple resolutions
What resolution was this site developed in / designed for ___________
N. Legacy systems
Will site be integrated into any legacy systems
FORMCHECKBOX
yes FORMCHECKBOX
no
If yes, will QA be required to test after integration
FORMCHECKBOX
yes FORMCHECKBOX
no
Additional comments: ________________________________________
O. Load testing
Is load testing required for this site
FORMCHECKBOX
yes FORMCHECKBOX
no
If yes, approximately how many users ___________
Additional comments: ________________________________________
Additional items to be tested: _______________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
Contact: ________________________ extension: ______________________
URL: ___________________________
