|
QA Report Contents
|

This
table summarizes the information that needs to be part of the
report:
| QA Plan Sections for Small to Medium Websites |
Report Contents |
| a. Purpose |
Repeat the purpose statement from the original Quality
Assurance Plan, with any revisions that appeared helpful
as the site was developed. |
b. Tests |
List and describe the tests that were carried out, tools,
techniques, and methodologies used (from the "Tools,
Techniques, and Methodologies" section of the QA
Plan). For each test, detail the pages and/or features
that were tested. |
c. Problem reporting and corrective
action |
List each test again, detailing whether the test revealed
any problems. If problems were revealed, explain them
and suggest corrective action that needs to be taken.
This is the section that is supposed to go to the Project
Manager so that resources can be assigned for correcting
the problems. |
[d. Tools, techniques and methodologies] |
(Include this in section b, "Tests".) |
e. Training |
If training was considered necessary, what training was
adiminstered and how the staff assessed its success.. |

|
|
Example:
|
Quality Test Findings
Purpose: Quality Assurance (QA) testing is carried out
to ensure that code is well-formed and valid, that all links are
operational, and that both users and customers are satisfied with
the appearance and functioning of the site on various computer
system and with various browsers.
Tests: The following aspects were tested:
- All links: tested for operability by manually following the
links
- All code: validated against W3C standards for XHTML 1.0 and
CSS level 2, using W3C validators (http://validator.w3.org/)
- Compatibility: site rendering will be checked on the following:
- Windows:
- Internet Explorer 5.5 and 6.0
- Netscape 4.7and 7.0. both on Windows and Macintosh
systems
- Macintosh:
- Internet Explorer 6.0
- Netscape 7.0
- Customer satisfaction has been an issue of ongoing importance
throughout development. The Web developers have been in contact
several times weekly with the staff of the Stony Creek Historical
Museum.
Problem reporting and corrective action: The following
issues were noted and are referred to the Project Manager for
resolution:
- Non-validating pages, which need to be corrected and re-validated:
- Home page
- Agricultural machinery page
- Volunteer duties page
- [etc.]
- Inoperable links, which need to be researched, verified, and
re-coded:
- On Home page:
- Michigan Historical Society
- Lincoln School District
- Donors' page
- [etc.]
- On Volunteers' page:
- [etc.]
- Content corrections: see attached printouts.
|
|
Procedure for Submitting Materials
|
- Individual team members get their part of this assignment
to the Team Leader by email attachment, or some other method
mutually agreed upon in discussion.
- Team Leader makes sure all documents in the milestone
of which this is a part are gathered together in a compatible
form.
- Team Leader and/or content specialist check
for correct spelling and English usage.
- Team leader verifies that material submitted meets
the requirements.
- Team leader or content specialist FTP the
material to the team's Web site, informing the instructor
and other team members by emailing to them the URI.
|
Original: 14 November 2003; Last modification:
Monday, 31-Aug-2009 11:48:07 EDT