Test coverage
The share of an explicitly defined set, such as executable statements or requirements, that has been tested.
Read the proportion with a clear denominator
Test coverage relates checked elements to a defined total set. For code coverage, these can be executable statements or branches. Requirements coverage instead considers named requirements. These measures are not freely interchangeable.
In a fictional calculation, tests execute 10 of 20 executable statements: 10 / 20 × 100 = 50 % statement coverage. This does not say whether results were meaningfully checked or all important inputs occurred. Executing all code still does not prove that tests check correctly or that every requirement is implemented. Compare only the same metric and scope, and investigate business-relevant gaps behind the number.
Sources
Related terms
- Unit testA focused check of a small, defined part of software, such as a rule or function.
- Regression testA check for unwanted effects of a change on behaviour that is still required.
- Test automationTools perform defined testing tasks, such as execution and comparison with expected results.
- Contract testA test of agreed messages between a consumer and a provider at an application interface.
- LinterA tool that examines code for particular problems using configured rules.
- Static code analysisExamining code, or a representation of it, without running the application’s workflows to do so.
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.