Which of the following is supported by good information traceability?

Question

Options

• APortability of test automation code
• BUnderstandability of test reports
• CDependability of test environments
• DStability of the system under test

• B
  91% (31)
• C
  6% (2)
• D
  3% (1)

Explanation

Good information traceability means you can link test cases to requirements, test results to test cases, and defects to both - creating a clear chain from requirements through to outcomes. This directly supports understandability of test reports (B) because stakeholders can follow that chain to see what was tested, why, and what happened, making reports far more meaningful than a bare pass/fail count.

A (Portability of test automation code) is wrong because portability depends on how automation code is written and structured - not on whether information is traceable across artifacts. C (Dependability of test environments) is an infrastructure concern about reliability and stability of servers, databases, and tooling - unrelated to traceability. D (Stability of the system under test) describes the behavior of the application itself, which traceability observes but does not influence.

Memory tip: Think "traceability = tracing the story." When you can trace from requirement → test case → result → defect, your test report tells a complete, readable story - that's understandability.

No community discussion yet for this question.