In computer science
, test coverage
is a measure used to describe the degree to which the source code
of a program
is executed when a particular test suite
runs. A program with high test coverage, measured as a percentage, has had more of its source code executed during testing, which suggests it has a lower chance of containing undetected software bugs
compared to a program with low test coverage.
Many different metrics can be used to calculate test coverage; some of the most basic are the percentage of program subroutines
and the percentage of program statements
called during execution of the test suite.
Test coverage was among the first methods invented for systematic software testing. The first published reference was by Miller and Maloney in Communications of the ACM in 1963.
To measure what percentage of code has been exercised by a test suite, one or more coverage criteria are used. Coverage criteria are usually defined as rules or requirements, which a test suite needs to satisfy.
There are a number of coverage criteria, the main ones being:
For example, consider the following C function:
Assume this function is a part of some bigger program and this program was run with some test suite.
This page was last edited on 21 March 2018, at 18:07.
under CC BY-SA license.