Product / Coverage
See which product states still need a test.
Define roles, devices, data states, and constraints, then compare supplied observations with the resulting state map.
- Identity
- Signed-in member
- Data
- Unsaved profile change
- Network
- Connection interrupted
- Coverage
- Needs a recovery test
Coverage
Know which states nobody has tested yet.
Define the roles, devices and data states that matter, then see which of them your observations actually cover and which are still assumptions.
Which profile states still need a test?
Walking the state map
Comparing the observations you supplied with the roles, devices and data states on the record.
Signed-in member, unsaved change, connection interrupted Recovery after an interrupted save
No observation supplied. This state is still untested.
Unsaved change carried to a new session
Covered by the session recovery run you attached.
Why use Coverage?
A successful happy path leaves many combinations unexplored. Make the gaps explicit so testing effort has a clear next target.
Map the relevant combinations
Describe dimensions and exclude combinations that cannot occur.
Find gaps in observations
See which states have supporting evidence and which remain untested.
Plan the next test
Use the state map to select the conditions your next test should exercise.
How Coverage fits your work
- 01
Define the dimensions
Describe relevant identities, devices, data, and network conditions.
- 02
Add constraints and evidence
Exclude impossible states and supply observations from completed tests.
- 03
Review remaining coverage
Choose the next states to exercise and add the resulting evidence.
What to know before you start
A state map does not run a browser test. Coverage depends on the model and observations you supply.
Use your workspace or a compatible agent connected through MCP. Read the connection guide.