Coverage
A metric in software testing that measures the proportion of code executed, including line coverage and branch coverage. It is computed by tools such as JaCoCo and Coverage.py and reflects the extent to which tests touch the code rather than the effectiveness of assertions.
Timeline (last 90 days)
Coverage usually refers to metrics such as line coverage and branch coverage, counted by tools such as JaCoCo and Coverage.py; it answers "which code was executed" rather than "whether the execution results were correctly asserted".
The video summarizes three core points: coverage does not equal correctness, probes must penetrate to real dependencies, and boundaries are the core battleground.
Deleting one line of the README once made coverage become 1.0; after the fix, patches with no code lines are marked as unmeasured for coverage, and cannot obtain MERGE on the basis of coverage.
The experiment used a pre-specified two-percentage-point margin for the coverage determination as the criterion for "substantial difference", in order to avoid treating Monte Carlo noise as a conclusion.
Coverage metrics measure how many components were checked but cannot reflect the actual consequences produced by an operation or its consumers, and may therefore conceal failures on critical paths
All Facts (5)
Coverage usually refers to metrics such as line coverage and branch coverage, counted by tools such as JaCoCo and Coverage.py; it answers "which code was executed" rather than "whether the execution results were correctly asserted".
50%UnverifiedThe video summarizes three core points: coverage does not equal correctness, probes must penetrate to real dependencies, and boundaries are the core battleground.
50%UnverifiedThe experiment used a pre-specified two-percentage-point margin for the coverage determination as the criterion for "substantial difference", in order to avoid treating Monte Carlo noise as a conclusion.
50%UnverifiedCoverage metrics measure how many components were checked but cannot reflect the actual consequences produced by an operation or its consumers, and may therefore conceal failures on critical paths
50%UnverifiedDeleting one line of the README once made coverage become 1.0; after the fix, patches with no code lines are marked as unmeasured for coverage, and cannot obtain MERGE on the basis of coverage.
50%