Testing
Coverage & traceability
Map requirements to tests and identify coverage gaps.
Overview
Coverage and traceability in Zof map requirement IDs to scenarios, cases, and execution evidence, highlighting gaps that represent unvalidated risk. Unlike code coverage alone, requirement coverage answers whether planned behavior has associated validation and recent run history.
Release readiness reviews use coverage matrices to separate "tests exist" from "requirements are validated." Export gap reports for stakeholders who approve risk acceptance when deadlines preclude full mapping.
Coverage is only as accurate as scenario naming and library maintenance. Orphan tests without requirement IDs inflate noise; missing IDs in requirements prevent mapping even when tests exist.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
Prerequisites
- Requirements with stable IDs in specifications or project attachments
- Scenarios following SCN-<REQID>-* naming where possible
When to use this workflow
- Pre-release audits with compliance or PM stakeholders
- Sprint planning to prioritize test authoring for unmapped requirements
- Post-generation validation that AI output covered the intended PRD scope
Traceability matrix usage
Traceability matrix usage
Typical flow from matrix review to gap closure before gate sign-off.
Step-by-step procedure
Open Quality → Coverage
Navigate via left nav or ⌘K → "Coverage".
Select specification, project, or release filter matching your review scope.
Confirm requirement ID column displays expected catalog IDs.
Interpret matrix columns
Requirement ID, authoritative rule from specification.
Scenario mapping, linked SCN-* records validating the requirement.
Case mapping, executable cases with review status indicators.
Last run evidence, recency signal; unmapped or stale rows flag risk.
Export and distribute gap reports
Export CSV or PDF gap list for release readiness meetings.
Sort by risk priority (payments, auth) when timeboxed remediation is required.
Attach gap report to change ticket for audit retention.
Close gaps deliberately
Author or generate cases for unmapped requirements; avoid checkbox testing without assertions.
Link orphan tests to requirement IDs or deprecate obsolete inventory.
Schedule staging runs to populate last-run evidence before gate evaluation.
Handle explicit risk acceptance
When deadlines preclude full coverage, document approved exceptions in governance tools.
Reference requirement IDs in risk acceptance records for traceability.
Set follow-up sprint goals to burn down accepted gaps.
Refresh matrix before sign-off
Re-open Coverage after remediation runs complete.
Verify last-run timestamps updated for previously stale rows.
Obtain sign-off from QA lead or compliance delegate per organizational policy.
Key concepts
- Organization scope
- All Zof Console and API operations are isolated to your authenticated tenant.
- Governed execution
- Agent output and remediation follow policy packs with human approval when configured.
Best practices
- Make coverage review a gate before executive release briefings
- Reject release sign-off when P0 requirements lack mapped P0 cases
- Pair coverage exports with Test Health summaries for credible risk narrative
- Reconcile orphan tests quarterly to prevent library drift
Common issues
- High case count but coverage gaps remain
- Cases may lack requirement ID linkage. Fix scenario titles and metadata, then refresh matrix.
- Mapped but last run stale
- Execute targeted suite for stale rows before accepting release readiness.
Illustrative traceability matrix excerpt
REQ-ID | Scenario | Cases | Last run REQ-PAY-014 | SCN-REQ-PAY-014-refund-elig. | 3 | 2025-05-19 Passed REQ-PAY-015 |, | 0 |, REQ-AUTH-003 | SCN-REQ-AUTH-003-session-timeout | 2 | 2025-05-18 Failed
Was this page helpful?