Requirement Traceability Matrix

Learning objectives#

• Build an RTM
• Use it to find coverage gaps
• Trace defects back to requirements
• Explain forward and backward traceability

Explanation#

Rows are requirements (or user stories); columns list linked test cases, execution status and defects.

Forward traceability: requirement → tests (is everything covered?). Backward: test → requirement (does each test have a purpose?).

Tools like Jira with Xray/Zephyr, Azure Test Plans or a simple spreadsheet can hold the RTM.

Code example: RTM for a login feature#

1Req ID   Requirement                         Test cases                Status       Defects
2REQ-01   Login with email and password       TC-01, TC-02, TC-03       Passed       —
3REQ-02   Lock account after 5 failures       TC-04                     Failed       BUG-207
4REQ-03   "Remember me" keeps session 30 days  (none)                    NOT COVERED  —
5REQ-04   Show/hide password toggle           TC-05                     Passed       —
6

7Coverage: 3 of 4 requirements tested → write cases for REQ-03 before release

The matrix exposes an untested requirement and links a failure to its bug.

This example is illustrative. Copy or download it and run it in your own environment; the expected output is shown above.

Step-by-step explanation#

1. List every requirement with an ID.
2. Link each to its test cases.
3. Add execution status and defects.
4. Act on gaps and failures.

Real-world use case#

Common mistakes#

Best practices#

• Give every requirement an ID
• Link tests and defects in your tool
• Review coverage before release
• Use it for impact analysis

Remember this#

Practice exercise#

1It shows TC-04 (and BUG-207) are linked to REQ-02, so you know exactly which tests to update and re-run.

Mini quiz#

Want more? Practise all Manual Testing MCQs · Manual Testing interview questions

Related topics#

My notes#

Saved in this browser.