fleetlint Policy for a fleet of repositories
v0.4
Getting started

quality/coverage-threshold

A coverage floor is enforced

A capability: each stack checks it with its own tools. Implemented for any, cpp, dotnet, flutter, go, hugo, java, kotlin, node, php, python, ruby, rust.

Severitywarning
Tiers1, 2
Stacksany
Scopeeach
Kindcapability
Sourcelibrary v0.1.0
Selected byfleetlint-recommended@v0.1.0

Requirement

Tests fail below a coverage floor: the stack’s coverage tool configured with a minimum, a threshold in the cover recipe, diff-cover --fail-under, or a codecov target. Comments and echo lines do not count. For a workspace member the repository’s CI and configuration files in parent directories count as well.

Why

A coverage number nobody enforces drifts down one “quick fix” at a time.

Fix

Make make cover fail below the floor (diff-cover –fail-under=80 is the stack-neutral option).

Agent instruction: Add a threshold to the cover recipe using the stack profile’s tool (go: go-test-coverage or a cover script with a minimum; python: –cov-fail-under; node: coverageThreshold; rust: cargo llvm-cov –fail-under-lines; kotlin: kover verify).

See: https://fleetlint.org/baseline/#tests


Generated by fleetlint docs from catalog v0.1.0.