What Qaptly Considers Coverage
Coverage in Qaptly is not about how many scripts ran. It is about how much of your product’s behavior is understood.What Qaptly Measures
Qaptly tracks coverage across three dimensions:States
Which screens and situations were seen
Transitions
Which paths were taken
Conditions
Which behavior variants occurred
The Coverage Dimensions
State Coverage
State Coverage
What it measures:
- How many distinct states have been observed
- Which screens or views have been visited
- What error states have been encountered
Transition Coverage
Transition Coverage
What it measures:
- How many state changes have occurred
- Which user paths have been exercised
- What navigation flows have been verified
Condition Coverage
Condition Coverage
What it measures:
- How many behavior variants have been triggered
- Which conditions affect state transitions
- What edge cases have been exercised
Why This is Better Than Script Coverage
A script may run, but never trigger an important condition.Qaptly can show you exactly:
- ❌ Which paths were never taken
- ❌ Which error states were never seen
- ❌ Which combinations were never exercised
Script Coverage vs. Behavior Coverage
Coverage You Can Trust
Because Qaptly’s coverage is built from real evidence, it reflects what your product has actually done — not what someone hoped it would do.This is how Qaptly turns testing into measurable product understanding.
Related Articles
From Flows to Scenarios
How flows are identified
From Conditions to Cases
How cases are generated
Evidence-Based Results
Proving quality with coverage