Line coverage
The share of executable lines executed at least once by the suite.
at / above target
Coverage Metrics Handbook
A field reference for the metrics the framework reports — what each one measures, how it is calculated, and where the line sits.
- pass — at or above target
- warn — trending below
- fail — below threshold
Branch coverage
The share of decision branches — true and false paths — that have been taken.
at / above target
Mutation coverage
How many seeded code mutations the suite detects. The strongest signal that tests fail when behaviour breaks.
trending below
Flow coverage
The share of end-to-end user workflows exercised by the suite, mapped from the code, not the ticket list.
at / above target
Requirement traceability
How many requirements have at least one automated case linked to them and a passing result.
at / above target
Regression detection rate
The share of introduced regressions the suite catches before the gate, measured across runs.
at / above target
Gate pass rate
The share of runs that pass the coverage gate on the first attempt. Rising is good; falling is a smoke signal.
trending below
Time-to-gate
How long the pipeline takes from push to gate decision. The number that keeps coverage fast enough to matter.
at / above target
the principle
Measure what ships, not what runs.
Coverage numbers mean nothing if they come from tests that never gate a release. The framework measures the suite that actually runs in your pipeline — and the gate enforces the target on every push. The baseline promise: 80% automated coverage within four months, measured against these metrics.
See the metrics on your code.
The first coverage-gate report comes with the first week of the engagement.