Business analysis glossary
Test Coverage
What it is
Test coverage measures how much of something has been tested, for example the percentage of requirements with at least one test, the share of business rules or scenarios tested, or the proportion of code run by automated tests. It shows where testing is thin.
Why it matters
High coverage does not prove quality, but low coverage proves risk. Requirement coverage is especially useful for analysts: every requirement should trace to at least one meaningful test, and critical ones to several, including negative cases. A traceability matrix makes the gaps visible.
Example
The analyst checks the traceability matrix before UAT and finds that ninety percent of requirements are covered, but the three requirements about refunds to closed accounts have no tests. She adds four test cases, including the boundary where the account closed on the same day as the refund.