Test Coverage
Metric indicating what share of a program is actually executed during a test run.
Test coverage measures what share of the source code – counted, for example, by lines, branches or functions – is run through at least once when the test suite is executed. The result is usually output as a percentage, for example by PHPUnit or Jest.
Values such as 80 percent are often circulated as a benchmark, but are convention and not a norm – they appear in no specification and do not fit every project equally well. Above all, high test coverage says nothing about whether the tests really check what they are supposed to check: code can be run through and still remain unchecked if the assertions in the test are missing or too weak.
What Provimedia uses it for
Provimedia watches test coverage as a rough indicator but does not rely on the number alone for the actual quality of testing.
Want to use Test Coverage for your project?
In a free conversation, let's find out how we can implement this for you.
More from Software quality
Clean Code
Guiding idea for code that is designed to be understandable for humans and not just for the compiler.
Learn moreCode Review
Systematic examination of code by other developers before it is merged into the main branch.
Learn moreCode Smell
Conspicuous pattern in code that is not necessarily wrong but points to a deeper problem.
Learn moreDefinition of Done
Written list of criteria agreed in the team that a task must meet in order to count as done.
Learn moreLinting
Automated checking of code for style and formatting errors according to fixed rules.
Learn moreMutation Testing
Technique that deliberately introduces small errors into the code to check how meaningful the tests are.
Learn moreQuality Gate
Check stage in the development pipeline that lets a change pass only if fixed criteria are met.
Learn moreRefactoring
Targeted restructuring of existing code without changing its external behavior.
Learn more