Measure what your scenarios actually cover
TestHub correlates your authored scenarios with a complete inventory of the application's API and UI routes, and shows exactly what is tested, weakly tested, and still missing.
Every route gets one honest classification
The denominator is a complete inventory of your application's API and UI routes, generated from the connected repository. The numerator is your authored scenario set. Coverage is the difference, route by route.
Covered
At least one scenario exercises the route and includes a linked, relevant assertion.
Partial
A scenario touches the route without a deterministically linked assertion. Visible, but not counted as covered.
Uncovered
No scenario signal matches the route. This is your authoring backlog, prioritized.
Excluded
Framework-generated or intentionally omitted routes, removed from the denominator with a recorded reason.
Built against coverage theater
Honest metrics
API and UI coverage are reported separately, never blended into a single flattering percentage. If a route inventory is incomplete, the percentage is withheld rather than guessed.
Evidence-backed attribution
Every covered or partial route names the exact scenarios and steps responsible, with the reasoning visible for review.
Assertion strength matters
A route hit is not the same as a verified behavior. Coverage distinguishes strong, basic, and missing assertions so quantity never masquerades as quality.
Deterministic and repeatable
Classification is explicit, versioned logic, not model judgment. The same inputs always produce the same report.
Comparisons that explain themselves
Reports are snapshotted against your code and scenario set. Every comparison is labeled: scenario changes, repository changes, or rule changes, and only true same-baseline drops are flagged as regressions.
Exclusions with an audit trail
Non-testable routes stay visible with recorded reasons and approvers. They never silently disappear from the inventory.
Gaps become your next scenarios
High-priority uncovered and partial routes, such as authentication, payments, and destructive operations, surface as prioritized recommendations. Each recommendation launches straight into scenario discovery, so the path from measured gap to authored test is one click.
Coverage report → prioritized gaps → scenario discovery → authored scenarios → improved coverage
Explore all TestHub capabilities · Currently viewing: Code Coverage
See your application's real coverage number
Request a walkthrough and we will show coverage reporting against an application you know well.
Part of SolidX