fleetlint Policy for a fleet of repositories
v0.11 (latest)
Getting started

quality/coverage-threshold

A coverage floor is enforced

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

Severitywarning
Tiers1, 2
Stacksany
Scopeeach
Kindcapability
Sourcelibrary v0.8.0
Selected byfleetlint-recommended@v0.8.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 the cover target fail below the floor with the stack’s coverage tool, or run diff-cover --fail-under=80 on its report (any stack).

Agent instruction: Add a threshold to the cover recipe with the coverage tool of the stack profile (https://fleetlint.org/stacks/), or run diff-cover –fail-under on the coverage report.

Sources


Generated by fleetlint docs from catalog v0.8.0.