As a QA, I spend a considerable amount of time in finding and implementing tools that make our work easier and more efficient. RTM and test closure report, both are some of those tools I use in my daily work. RTM is a document that maps and co-relates requirements with test cases. It is used to track the requirements and to check if the requirements are met or not. This single document keeps record of all the issues, tests, test results, client demands and validates that all the requirements are checked during software testing. A test closure report is created once the testing of a software is completed successfully, and the product has met the exit criteria. This report describes the testing activities performed by QA. Test closure report is created by a QA engineer and is reviewed by all the stakeholders. Test closure reports provide a detailed analysis of the types of testing performed, process followed, the status of bugs, and the details of the open defects. Every QA team prepares this report to ensure that the product release is stable.

1. Usage of RTM and Test
Closure Report

2. Gurzu Confidential
• What is RTM?
• Purpose of RTM
• Parameters included in RTM
• Benefits of RTM
• Test Closure Report
• Parameters included in Test Closure Report
• Test Metrics
• Benefits of Test Closure Report
2
CONTENT

3. Requirement
Traceability
Matrix (RTM)

4. Gurzu Confidential
What is RTM?

5. Gurzu Confidential
5
Purpose of RTM
Tracing
Monitoring
Mapping

6. Parameters included in RTM

7. Gurzu Confidential
1. All the data in a single document.
1. It confirms the full test coverage of the product.
1. It also connects contributors and stakeholders to the requirements. Through this
document stakeholders and customers can also walk through the status of the
requirements and make decisions accordingly.
1. It also analyzes the QA’s work of revising the test cases.
Benefits of RTM
7

8. Test Closure
Report

9. Gurzu Confidential
9
Introduction
Test closure reports provide a detailed
analysis of the types of testing carried
out, processes followed, the status of
bugs found, and open defects details.

10. Points to cover in Test Closure Report

11. Gurzu Confidential
Test Metrics in Test Closure Report
11

12. Why Is Test Closure Required?
• Formally Announce Closure
• Combine all results
• Provide Detail Analysis
• Present Test Metric
• Adjudge Risks To Client