Traceability shows how testing work connects. Coverage shows whether important work is tested well enough.
Use requirements to describe what needs validation. Link repository test cases to requirements so coverage is visible and reusable across releases, test runs, and defect review.
Learn more in Requirement Usages.
Select test cases intentionally for release executions and standalone test runs.
Good selection sources include:
This keeps execution scope explainable.
When a test fails, create or link a defect from the execution flow when possible.
Defect traceability should make it clear:
Labels help teams filter and compare related work across supported areas.
Use labels for feature areas, risk areas, release themes, or ownership patterns that need quick filtering.
Before major testing milestones, review:
Coverage is a confidence tool, not a checkbox exercise.