How-to Guide
Map requirements to tests
Use coverage traceability to link requirements and cases.
Objective
Use coverage traceability to link requirements and cases.
Prerequisites
- Requirements and cases exist
Procedure
Open Coverage
Quality → Coverage.
Navigation: Quality → Tests, Coverage, or Test Health. Link work to a project when validating generation or traceability.
Verification: Confirm organization and team context in the Console header before making changes.
Review traceability tab
Map requirement records to test cases.
Navigation: Quality → Tests, Coverage, or Test Health. Link work to a project when validating generation or traceability.
Verification: Note project, run, or agent IDs if you may need support escalation.
Address gaps
Generate or author tests for uncovered requirements.
Navigation: Quality → Tests, Coverage, or Test Health. Link work to a project when validating generation or traceability.
Verification: Confirm UI state matches your runbook. Retry once on transient errors before opening a ticket.
Verification checklist
- Confirm expected UI state or API response after each critical step
- Document run ID, project ID, or agent ID for support escalation if needed
- Notify stakeholders if the workflow affects release gates or production validation
Expected result
Traceability matrix reflects requirement coverage.
Was this page helpful?