Stop 03 · Test Planning & StrategyTopics · 8/9

Traceability Matrix

In short

Has every requirement got at least one test? Without a traceability matrix you're guessing. With one, gaps jump out in seconds.

A document tracking each requirement to its corresponding test case, ensuring nothing goes untested and nothing gets tested without a clear reason — the QA-specific application of the same concept from business analysis.

The purple blob ticks off names on a long list next to a pile of wedding invitation envelopes.

Think of it like this

The wedding card list

Before a wedding, the family keeps a list: every relative, and a tick when their card is delivered. One glance shows who's been missed. A traceability matrix is that list, with requirements and their tests.

Watch it happen

Requirements traced to tests

Coupon feature

REQ-1 apply

REQ-2 expiry

REQ-3 one only

TC-01, TC-02

TC-03

No test yet

1/4REQ-1 is covered by two test cases. Both passed, so this requirement is verified.

The big ideas

What you need to know

Forward and backward

Forward: requirement to tests, finds gaps. Backward: test to requirement, finds tests with no purpose.

Link bugs too

Adding bug IDs shows which requirements are failing and blocks release decisions.

Change impact

When a requirement changes, the matrix shows exactly which tests need updating.

See it in code

A tiny example

text

1Req     Description            Tests          Status2REQ-1   Apply valid coupon     TC-01, TC-02   Pass3REQ-2   Reject expired coupon  TC-03          Fail (BUG-88)4REQ-3   One coupon per order   -              NOT COVERED

A simple matrix, often kept in a sheet or generated by a test management tool.

Save yourself the pain

Common mistakes

Oops

Building the matrix once and never updating it.

Do this instead

Update it when requirements or tests change, or it quickly becomes misleading.

Oops

Counting 'has a test' as 'is tested well'.

Do this instead

One weak test still counts as covered. Review that key requirements have strong tests too.

Your mission

Trace a small feature

~20 min

Quick check

Your matrix shows a test case linked to no requirement. What could that mean?

Go deeper

1Build a simple traceability matrix linking 5-8 requirements to their corresponding test cases.
2Learn why an RTM is especially valuable in regulated or compliance-heavy industries.
3Practice using an RTM to identify a requirement that currently has no test coverage.