Thread: Usage of Traceability Matrix in Manual testing

can you explain what is traceability metric and how it is usefull in manual testing?

Test cases will be written for the requirement specification document. Once the requirement document is received it will be splitted into smaller parts for the identification of Test scenarios. For the scenarios identified test cases are written. Once the test cases are written we need to know whether the test cases are traceable to the requirements. For this purpose Traceability matrix is used.

Traceability Matrix is a Excel sheet which has the following fields.

1. Requirement ID/ Name
2. Build / Version
3. Test case Name
4. Name of the Tester
5. Req. received date
6. Defect Associated (if, any)
7. Module Name

In this sheet the test cases written are mapped against the requirement ID and is checked whether for all the functionalities the test cases are written and is traceable to the specifications.

This is process followed for the usage of RTM in both the manual and automation testing.

Hi devic8 a traceability matrix or requirement traceablility matrix (rtm) as it is often addressed is a document used to trace if our testcases cover all requirements in scope for testing. As specified by ganesh, when requirements are drilled down to smaller identifiable parts of which test scenarios are derived and further on testcases, it is quite possible that the user might miss out on some requirement. Thus a document typing up testcases to requirements and vice-versa in format - requirement id / change request id, req description build number testcase name / number module / functionality associated comments is created. Such a traceability matrix is possible using test managements tools like test director as well. Cheers.