Code CoverageAvailable

A coverage number you can defend

For your board, your customers, and your auditors: a current, honest answer to how much of your product is actually tested.

Coverage report
Your product, area by area
Updated today
API routes
78%
62 of 80 covered
UI routes
64%
29 of 45 covered
TestedPartially testedNot tested
  • Checkout and paymentsTested
  • Sign-up and loginTested
  • Team invitationsPartially tested
  • Billing settingsTested
  • Reports and exportsNot tested
Illustrative
The model

Every route gets one honest label

The denominator is a full inventory of API and UI routes from your repository.

Covered

A scenario exercises the route with a linked assertion.

Partial

Touched, but not verified. Visible, not counted.

Uncovered

No scenario reaches it. Your next backlog.

Excluded

Intentionally out of scope, with a reason and approver.

Built against coverage theater

Honest by design

API and UI apart

Never blended into one flattering number.

Assertions required

A route hit is not a verified behavior.

No guessing

An incomplete inventory shows no percentage at all.

Deterministic

Same inputs, same report. No model judgment.

Comparisons explained

Scenario, code, and rule changes are labeled.

Gaps loop back

Uncovered routes launch straight into discovery.

Hand auditors a report, not a shrug

We show coverage reporting against an application you know well.