Workspace test-coverage measurement¶
Standing tooling that measures line coverage across the workspace, so coverage is a repeatable verification artifact rather than a one-off number.
Motivation. No coverage measurement exists in the repository today — no tool, no script, no CI job. For a project building a safety argument, test coverage is a standing verification artifact: it must be cheap to re-measure and produce comparable numbers run over run, which means the invocation (feature set, exclusions, test-thread discipline) has to be pinned in tooling, not folklore. Scope. A repeatable local entrypoint ( Non-goals (deferred until a baseline exists). CI integration
(runner choice, artifact upload, Codecov); coverage thresholds or
gates; doctest coverage (requires nightly |
The repository shall provide |
The coverage run shall compile and test the workspace with
|
The coverage run shall pass |
The coverage report shall exclude build-script-generated sources
( |
The script shall emit a per-crate terminal summary, an HTML report,
and an lcov trace file, all under |
When |
|