What is test coverage?
Test coverage describes how much of an application, its code or its requirements is exercised by tests.
Code coverage measures the percentage of lines or branches executed by tests. Feature or journey coverage measures how many important user flows and requirements are tested.
High code coverage does not guarantee quality, because tests can run code without checking the right outcomes. Journey coverage is usually a better signal of release confidence.
Example
A product has 85% code coverage, but its refund journey has no tests at all. Mapping journeys reveals the gap that the code metric hid.
Best practices
- Track journey coverage for critical flows
- Use code coverage to find untested logic
- Review what tests assert, not just what they run
- Set coverage goals per risk area
Ship without fear.
Start testing free in minutes, or let a QAShift engineer deliver your first morning report within 5 days.