Traceability matrix in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of a Traceability Matrix

What is the main purpose of a traceability matrix in software testing?

A To document the project schedule and milestones

B To list all bugs found during testing with their severity

C To track the number of test cases executed per day

D To map requirements to test cases ensuring all requirements are tested

💡 Hint

Think about how testers ensure every requirement is covered by tests.

A traceability matrix links requirements to their corresponding test cases. This ensures that all requirements have been tested and nothing is missed.

❓ Predict Output

intermediate

Traceability Matrix Coverage Count

Given the following traceability matrix represented as a dictionary where keys are requirement IDs and values are lists of test case IDs, how many requirements have no test cases linked?

Testing Fundamentals

traceability_matrix = {
  'REQ-1': ['TC-1', 'TC-2'],
  'REQ-2': [],
  'REQ-3': ['TC-3'],
  'REQ-4': []
}

count = sum(1 for tests in traceability_matrix.values() if len(tests) == 0)
print(count)

A 2

B 1

C 3

D 0

💡 Hint

Count how many requirements have empty test case lists.

REQ-2 and REQ-4 have empty lists, so 2 requirements have no test cases linked.

❓ assertion

advanced

Valid Assertion for Traceability Matrix Completeness

Which assertion correctly verifies that every requirement in the traceability matrix has at least one test case linked?

Testing Fundamentals

traceability_matrix = {
  'REQ-1': ['TC-1'],
  'REQ-2': ['TC-2', 'TC-3'],
  'REQ-3': ['TC-4']
}

A assert any(len(tests) == 0 for tests in traceability_matrix.values())

B assert len(traceability_matrix) == 0

C assert all(len(tests) > 0 for tests in traceability_matrix.values())

D assert all(len(tests) == 0 for tests in traceability_matrix.values())

💡 Hint

Think about how to check that no requirement has zero test cases.

Using all(len(tests) > 0) ensures every requirement has at least one linked test case.

🔧 Debug

advanced

Find the Bug in Traceability Matrix Test Coverage Code

Identify the error in the following code snippet that aims to print requirements without test cases:

Testing Fundamentals

traceability_matrix = {
  'REQ-1': ['TC-1'],
  'REQ-2': [],
  'REQ-3': ['TC-2']
}

for req, tests in traceability_matrix.items():
  if tests == None:
    print(req)

A The loop should iterate over traceability_matrix.keys() instead of items()

B The condition should check if tests is an empty list, not None

C The print statement should be outside the loop

D The dictionary keys are invalid and cause a runtime error

💡 Hint

Think about what value an empty list has compared to None.

The code checks if tests == None, but empty lists are not None. It should check if tests is empty using if not tests: or if len(tests) == 0:.

❓ framework

expert

Traceability Matrix Integration in Test Automation Framework

In a test automation framework, which approach best integrates a traceability matrix to ensure all requirements are tested automatically?

A Use a mapping file linking requirement IDs to test case IDs, and generate reports showing coverage after test runs

B Manually check test cases against requirements after each test run without automation

C Store test cases and requirements separately without linking, relying on testers to verify coverage

D Only automate test execution without tracking requirement coverage

💡 Hint

Consider how automation can help track coverage and generate reports.

Using a mapping file to link requirements and test cases allows automated coverage reports, ensuring traceability and completeness.

Practice

1. What is the main purpose of a traceability matrix in software testing?

easy

A. To link requirements to test cases ensuring coverage

B. To write code for automated tests

C. To track bugs found during testing

D. To manage project deadlines

Solution

1. Step 1: Understand the role of a traceability matrix

   A traceability matrix connects requirements with their corresponding test cases to ensure all requirements are tested.

2. Step 2: Compare options with this role

   Only To link requirements to test cases ensuring coverage describes linking requirements to tests, which is the main purpose.

3. Final Answer:

   To link requirements to test cases ensuring coverage -> Option A

4. Quick Check:

   Traceability matrix = links requirements to tests [OK]

Hint: Traceability matrix links requirements and tests [OK]

Common Mistakes:

• Confusing traceability matrix with bug tracking
• Thinking it manages project schedules
• Assuming it writes test code automatically

2. Which of the following is the correct way to represent a traceability matrix?

easy

A. A table mapping requirements IDs to test case IDs

B. A list of all bugs found during testing

C. A flowchart of the software architecture

D. A document describing user manuals

Solution

1. Step 1: Identify the format of a traceability matrix

   A traceability matrix is typically a table that maps requirement IDs to their corresponding test case IDs.

2. Step 2: Eliminate unrelated options

   Options A, C, and D describe bug lists, architecture diagrams, and manuals, which are not traceability matrices.

3. Final Answer:

   A table mapping requirements IDs to test case IDs -> Option A

4. Quick Check:

   Traceability matrix = table mapping requirements to tests [OK]

Hint: Traceability matrix is a mapping table [OK]

Common Mistakes:

• Confusing it with bug reports
• Thinking it is a flowchart or diagram
• Mixing it up with user documentation

3. Given the following traceability matrix snippet:

Requirement ID | Test Case ID
R1             | TC1
R2             | TC2
R3             | TC3, TC4

Which requirement has multiple test cases linked?

medium

A. R1

B. R2

C. R3

D. None

Solution

1. Step 1: Read the traceability matrix snippet

   Requirement R3 is linked to two test cases: TC3 and TC4.

2. Step 2: Identify which requirement has multiple test cases

   Only R3 has multiple test cases; R1 and R2 have one each.

3. Final Answer:

   R3 -> Option C

4. Quick Check:

   Multiple test cases linked = R3 [OK]

Hint: Look for multiple test cases per requirement [OK]

Common Mistakes:

• Ignoring multiple test cases listed
• Choosing requirement with single test case
• Misreading the table rows

4. A tester finds that some requirements are missing test cases in the traceability matrix. What is the best way to fix this?

medium

A. Ignore the missing test cases and proceed

B. Add test cases for the missing requirements

C. Remove those requirements from the project

D. Delete the entire traceability matrix and start over

Solution

1. Step 1: Understand the problem

   Missing test cases for requirements means incomplete test coverage.

2. Step 2: Choose the corrective action

   The best fix is to add test cases for those missing requirements to ensure coverage.

3. Final Answer:

   Add test cases for the missing requirements -> Option B

4. Quick Check:

   Fix missing tests by adding them [OK]

Hint: Add missing test cases to cover all requirements [OK]

Common Mistakes:

• Ignoring missing tests
• Removing requirements without discussion
• Deleting matrix unnecessarily

5. You have a traceability matrix with these entries:

Req ID | Test Case ID
R1     | TC1
R2     | TC2
R3     | TC3
R4     | TC4
R5     | TC5

During testing, TC3 and TC5 fail. What should you do to maintain traceability and quality?

hard

A. Delete all test cases and start testing again

B. Remove R3 and R5 from the matrix since tests failed

C. Ignore failures and mark all requirements as passed

D. Update the matrix to mark R3 and R5 as failed and create defect reports

Solution

1. Step 1: Analyze test results and traceability

   Failures in TC3 and TC5 mean requirements R3 and R5 are not met.

2. Step 2: Maintain traceability and quality

   Update the matrix to reflect failed tests and create defect reports for fixing issues.

3. Final Answer:

   Update the matrix to mark R3 and R5 as failed and create defect reports -> Option D

4. Quick Check:

   Mark failures and report defects to maintain quality [OK]

Hint: Mark failed tests and report defects promptly [OK]

Common Mistakes:

• Removing requirements due to test failure
• Ignoring test failures
• Restarting testing without tracking defects