What it does
Quantifies how much is actually covered and where the gaps are: structural (statement/branch), test-basis/requirements, risk, and coverage-item coverage, each compared against configured gates with a PASS/FAIL verdict. Read-only.
When to use it
When you need to know what is under-tested, at release endgame or in a quarterly health check.
Prerequisites
qa.config.yml (paths, tooling.unit/component, stack.api_spec_path, gates, risk_areas); a structural coverage artifact for the white-box dimension.
Output
ISO/IEC/IEEE 29119-3 Test Status Report (coverage metric) returned as a report; no file written.
Mechanics
How it works
- Resolve scope (default to risk_areas.critical if none given)
- Measure structural statement/branch coverage per module
- Map requirements and API endpoints to test cases via traceability
- Report risk coverage per tier and coverage-item coverage
- Apply gate thresholds as PASS/FAIL and prioritize gaps by risk
Why it works
The theory behind it
Monitoring via coverage measurement; coverage is a metric, not a target to game (absence-of-errors fallacy) and never proof of correctness.
CTFL v4.0 §5.3 · §4.3
Example
See it in use
> /qa:coverage-measure checkout✓ Correct when Reports structural plus requirements plus risk coverage and names the holes.
Related commands
Used by