Skip to content
Open core software, built in Singapore Established 2018  /  Five utilities
Jering
Talk to us

Code Coverage

DevOps.AzurePipelines Jering documentation Open source Pipeline templates
Documentation menu

Code coverage is a diagnostic, not a score. The templates generate and publish coverage so a trend is visible without turning a threshold into a game.

Collect

Use a coverage collector that supports the test framework and the target framework. Produce a report format that the build can publish and a human can read.

Interpret

Coverage shows which lines were executed, not whether the assertions are meaningful. A high number with weak tests is worse than a lower number with tests that exercise the contract.

Publish

Attach the report to the build and keep it with the artifact. Review the trend during release planning, not on every commit.

Reference shelf