Audit test coverage against user flows
Choose a feature with an existing test suite. Map every test against the feature's user flows using a mind map or table. Identify three coverage gaps; scenarios that users can exercise but no test covers. Write a charter for each gap and estimate the business risk of leaving each one untested.
Why this matters
Code coverage metrics lie. A test suite with 90% line coverage can miss the three most important user journeys entirely. Coverage auditing against user flows rather than lines of code is how senior QA engineers demonstrate strategic value; it connects testing decisions to business risk in language that product managers and engineers both understand.
Before you start
- A feature with a real test suite (a GitHub repository with tests you can read)
- Documentation or understanding of the feature's user flows
- A mind-mapping tool or a simple table (Miro, draw.io, or even pen and paper)
- Understanding of what a user flow is and how it differs from a test case
Step-by-step guide
- 1
Map the user flows
Write down every path a user can take through the feature: the happy path, the error paths, the edge cases (what if they navigate back mid-wizard?), and the permission-based variations (what can admin do that a regular user cannot?). This list is your coverage target.
- 2
Map each existing test to a flow
For each test in the suite, identify which user flow it covers (or partially covers). Mark the flow as covered once any test exercises it end-to-end. Be strict; a unit test for a validation function does not count as coverage for the user flow that triggers that validation.
- 3
Identify the gaps
Flows that appear in your map but have no test mapped to them are gaps. Highlight three gaps with the highest potential business impact. Common gaps: error recovery flows (user gets an error, retries), concurrent user scenarios, and feature interactions (using feature A immediately after feature B).
- 4
Write a charter for each gap
For each gap, write an exploratory charter: Explore [the uncovered flow] with [the relevant part of the application] to discover [whether the system handles it correctly]. Execute at least one of the three charters immediately; coverage gaps are most valuable when they find bugs, not just when they are documented.
- 5
Estimate and communicate risk
For each gap, write one sentence quantifying the business risk: 'If this flow fails in production, users cannot complete checkout; this is a direct revenue impact'. Present the three gaps to a product manager or engineer and get agreement on which to prioritise for automation.