A test summary report is a testing work product that formally summarizes the results of all testing on an endeavor.
Why Required?
- Summarizes all of the testing that was performed since the previous test summary report.
- Enables project management and customer to know the status of project testing.
Benefits
Project Management and end customer can:
- Get project testing status
- Get application quality status
- Take corrective actions, if required
Guidelines
1. It should be in metrics, charts and table forms, if possible
2. To write a test summary report, pre requisites are required – test plan should be completed, test execution should occur and respective test reports should be available.
Test Summary Report
1.0
Overview
Provide a high level description of
the overall testing and results.
2.0
Test
Coverage/Results
Describe the specific functionality
(area) tested and the results of the testing.
3.0
Functionality
NOT Tested
Document any functionality
that should have been tested, but was either not tested or did not receive
adequate testing. Provide reason why
testing was not accomplished. Such as:
.
Late delivery of product
.
No impact from changes to this functionality based on
. Development
assessment
. Not enough time
for testing –
. Project Manager
approved deferral of testing until next release
4.0
Test
Confidence
Describe the confidence level of
the testing that was performed. As an
outline for now we can use the following levels:
.
Extremely High
.
High
.
Medium
.
Low
Provide the reason for the rating
if not Extremely High or High.
5.0
Test Issues
and Concerns
Document any issues or concerns you
may have about the release. This may
encompass things such as:
. No documentation of changes in
area xxxx made testing pretty darn difficult.
.
Late delivery of release caused impact to available resources.
.
Slip of code complete caused a one-week impact to the test schedule
No comments:
Post a Comment