Traceability matrix in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Traceability Matrix in software testing?

A Traceability Matrix is a document that links requirements to their corresponding test cases. It helps ensure that all requirements are tested.

beginner

Why is a Traceability Matrix important?

It helps track coverage of requirements, ensures no requirement is missed, and assists in impact analysis when requirements change.

intermediate

What are the main columns typically found in a Traceability Matrix?

Common columns include Requirement ID, Requirement Description, Test Case ID, Test Case Description, and Status.

intermediate

How does a Traceability Matrix help during regression testing?

It identifies which test cases need to be re-executed based on changed or impacted requirements, saving time and effort.

advanced

Can a Traceability Matrix be used for both forward and backward traceability? Explain.

Yes. Forward traceability maps requirements to test cases to ensure coverage. Backward traceability maps test cases back to requirements to avoid unnecessary tests.

What does a Traceability Matrix primarily link together?

A Test Plans and Test Reports

B Test Cases and Defects

C Developers and Testers

D Requirements and Test Cases

A Traceability Matrix links requirements to their corresponding test cases to ensure coverage.

Which of the following is NOT typically a column in a Traceability Matrix?

A Developer Name

B Test Case Description

C Requirement ID

D Test Case Status

Developer Name is not usually part of a Traceability Matrix; it focuses on requirements and test cases.

How does a Traceability Matrix assist in impact analysis?

A By tracking developer assignments

B By listing all defects found

C By showing which requirements are linked to which test cases

D By scheduling test execution

It helps identify which test cases are affected when requirements change.

What type of traceability ensures all requirements have test cases?

A Forward Traceability

B Backward Traceability

C Horizontal Traceability

D Vertical Traceability

Forward traceability maps requirements to test cases to ensure coverage.

When is a Traceability Matrix most useful?

A Only after product release

B Throughout the testing lifecycle

C During test execution only

D Only during requirement gathering

It is useful throughout the testing lifecycle to track coverage and changes.

Explain what a Traceability Matrix is and why it is important in software testing.

Think about how testers make sure nothing is missed.

Describe the difference between forward and backward traceability in a Traceability Matrix.

Consider the direction of mapping.