In a typical CI pipeline, what does a "code coverage" metric measure, and what is its main limitation?
Correct! Well done.
Incorrect.
The correct answer is A) It measures the percentage of source code lines or branches exercised by automated tests; high coverage shows code was executed during tests, but it does not guarantee the tests actually assert correct behavior
Correct Answer
It measures the percentage of source code lines or branches exercised by automated tests; high coverage shows code was executed during tests, but it does not guarantee the tests actually assert correct behavior
Code coverage tools (Istanbul, JaCoCo, PHPUnit coverage) report what percentage of code paths ran during tests. A high number means code was executed, but tests without meaningful assertions can still show 100% coverage while verifying nothing — coverage is a useful signal, not a quality guarantee.