A test closure report is a report that describes the testing activities performed by a QA team. It is created once the testing phase is completed successfully or until the product being tested meets the exit criteria. Test closure reports are created by lead QA engineers and are reviewed by all other stakeholders.
Test closure reports provide a detailed analysis of the types of testing carried out, processes followed, the number of test cycles performed, the status of bugs found, and open defects details. Every QA team prepares test closure reports to ensure that the product release is stable.
Key points to cover in a test closure report:
- Project Summary: This will include a brief introduction to the project.
- Test Environment Details/Build Information: It will include browser/device information on which testing was carried out.
- Features Tested (In Scope): This section defines which modules/functionalities were tested in the project.
- Out of Scope: This section covers what was not covered in testing and why.
- Test Execution Details: This section is represented in a table where the total cycle, as well as the total number of test cases that were executed, passed, failed, and blocked, are mentioned. Also if any test cases were not executed, then the details about the same are also covered.
- Defect Matrix: In this section, defects are categorized according to their resolution and priority.
- Open Bugs Details: Open defect details should be mentioned like test case Id, summary, and priority.
- QA Notes/Learnings: QA engineers can write additional remarks here as new findings and learnings from the project.
- Conclusion: In this section, QA signs off the release and mentions if the release is stable (Stability % can also be mentioned).
Post a Comment