This document is prepared during the end of release to give information on testing activity. It consists of the following reports.
General information
| System or program i.d/acronym | Test project | Creation date | Date |
| Author(s) |
Revision history
The test manager will maintain this information and provide updates as required.
| Revision date | Author | Section | Summary |
Test summary overview
In this section we have update the phase wise test activities and summary.
| Test cycle no: | #test planned | #test executed | #test passed | Pass percentage | #test failed | Fail percentage |
| Unit testing | ||||||
| Integration testing | ||||||
| System testing | ||||||
| Acceptance testing |
Here it is clearly documented where the test results really met, the go/no go with respect to exit criteria defined in the test plan.
- Defect data analysis.
- Defect data metrics
| Priority | opened | closed | hold | rejected | outstanding |
| Critical | |||||
| High | |||||
| Medium | |||||
| Low |
Here the data is categorized into their level of priority and the status.
Outstanding issue
| Defect i.d | Description | Severity/impact | Action plan |
Here the defect is described and an action plan to rectify it is mentioned.
Change requests
If any change request details are there it has been mentioned here.
Exit criteria status
The project will be adhering to the exit criteria listed here as the main criteria in the go/no go and stage exit decisions.
| Exit criteria | Criteria met Yes/no | If no, describe plan of action |
| All tests have been successfully executed. | ||
| All expected and actual results are captured and documented with test script(s) | ||
| All identified critical or high severity defects have been corrected and retested. | ||
| Any unresolved defects are documented and signed off by the project manager. | ||
| Pass Rate. |