A test Summary Report is a kind of document that contains the summary of all types of test activities carried out and the final test results of a project under test. Test summary reports can be considered as an assessment of how well the testing activities are performed. Stakeholders can assess the quality of the tested software and consider the same for the decisions regarding product release.
- To know the status of the software and to decide the quality of the software.
- By having a test summary report, business clients or Stakeholders can take corrective action.
- It is considered to be the final document to make a critical decision about the release of the product.
This report is generated at the end of the testing cycles.
An effective test summary report must be relevant and concise. It is important to customize/adjust the test summary report after analyzing the same precisely what is required and what isn’t. The best practice for it is to define a template for the test summary report, however, never forget to remove the sections that are blank or where data is not applicable to give it a comprehensive look.
The below list can be included:
The objective of the test
Here the purpose of testing is included. Generally, it is to verify that a tester who conducted testing understood the requirements and expectations.
Areas Tested
This point highlights all the features and functionalities that are tested. It is not required to be as detailed as a test scenario however high-level information should be included if in case, say, one is testing an eLearning website, and it must outline and verify the flow to add a course, register, pay, and launch.
Areas Not Tested
The other important aspect of the test summary is to include the areas/functionalities/ features that are not tested. Anything that is not covered under testing will raise an alarm at the end of the client so it is vital to make a note or explanation of the same.
Platform details
Testing is carried out at various platforms and environments. So, it's highly recommended to include information regarding every single platform and environment tested.
Defect Report
This is included in the bug report however it is recommended to attach the same in the test summary report.
Testing Metrics (Optional)
Metrics, like the total number of defects with a level of severity, can be highly helpful. If applicable, also include additional metrics regarding test cases prepared and executed.
Overall Summary
Here the status of the software tested should be included as the feedback of the same. It must include all the details about the critical issues or blockages so that it can be helpful for the client to decide on product release.