 Create the Test
Summary
When the testing is finally completed, it is necessary to
write a Test Summary report, and distribute this to all the stakeholders.
Remember that the point of the testing was to determine the risk
of going live with this software, so there must be a section
clearly defining the risk.
In your document, you want the following as a minimum:
- Cover page, titled "<Project Name> Test
Summary Report", with a date and version number. Usually,
your company logo or department name is at the top. Don't forget
to list yourself as author, as well.
- Table of Contents.
- Introduction, saying what this test project was all
about.
- Stakeholders, listing all people with an interest
in this project. This is usually shown as a simple matrix with
two columns as follows; note that "Audience" is often
used instead of "Stakeholder".
|
Stakeholder |
Purpose |
|
Project Manager |
To be informed of the results of <Project Name> Testing
and any risks associated with this release. |
|
Application Team Leader |
To be informed of the results of <Project Name> Testing
and any risks associated with this release. |
|
Financial Controller |
To be informed of the results of <Project Name> Testing
and any risks associated with this release. |
- Version Control, which is a simple matrix as follows,
to keep track of changes to the document:
|
Version |
Date |
Author |
Reviewed by |
Changes |
|
0.1 |
19/9/2000 |
J. Doughy |
F. Flintstone |
initial creation of document |
- Approvals, which is a simple matrix showing who has
approved the document and allowing space for a signature and
date:
M. Maximillian
ABC Project Manager |
|
|
Date |
|
- Methodology, describing the techniques used to test
the software.
- Summary of Results, showing in summary what happened.
You could include the Test Logs here, or preferably include them
in an Appendix.
- Statement of Risk, which is a clear statement of the
risk associated with putting this software into production. Example:
"The Test Group has determined that the risk to the company
of putting this software release into production is low;
however, approximately 5% of customers will be adversely affected
by etc etc etc..... This problem should be addressed as soon
as possible."
|
|