Code coverage
Measure of source code testing
In software engineering, code coverage, also called test coverage, is a percentage measure of the degree to which the source code of a program is executed when a particular test suite is run. A program with high code coverage has 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 code coverage.
Nº Q1211721 ★
Common · Knowledge
Code coverage
Measure of source code testing
In software engineering, code coverage, also called test coverage, is a percentage measure of the degree to which the source code of a program is executed when a particular test suite is run. A program with high code coverage has 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 code coverage.
Last price
—
Floor price
—
7-day median
—
30-day sales
0
30-day range
—
In circulation
0
Price history
median
low – high
sales
No sales in this period
Show table
| Date | median | Low | High | sales |
|---|
Sales history
- Last sale
- —
- 30-day average
- —
- 30-day low
- —
- 30-day high
- —
- Sales 7d
- 0
- Sales 30d
- 0
No sales yet.
Anonymous sales: no buyer or seller shown. Figures count player-to-player sales only.
From Wikipedia
In software engineering, code coverage, also called test coverage, is a percentage measure of the degree to which the source code of a program is executed when a particular test suite is run. A program with high code coverage has 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 code 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. Code 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.
Text: Wikipédia, CC BY-SA 4.0. · Image: Matthew (WMF) (CC BY-SA 3.0) ·
Related cards
Source code
Collection of computer instructions written using some human-readable computer language
Nº Q128751 ★★★
Cohen's kappa
Statistic measuring inter-rater agreement for categorical items
Nº Q1107106 ★★
Proof of concept
Realization of a certain method or idea in order to demonstrate its feasibility
Nº Q1201019 ★★★
Buffer overflow
Anomaly in computer security and programming that could be exploited as a security vulnerability
Nº Q19423 ★★
Smoke testing (software)
Preliminary software testing to reveal simple failures to aid assessment of whether main functions of the software appear to work correctly
Nº Q17143088 ★★
Percent-encoding
Mechanism for encoding information in a Uniform Resource Identifier
Nº Q1046948 ★★★