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

quality/mutation-gate

Mutation testing runs on the core

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

Severityinfo
Tiers1
Stacksany
Scoperoot
Kindcapability
Sourcelibrary v0.8.0
Selected byfleetlint-recommended@v0.8.0

Requirement

A mutation testing tool runs on the core packages of every stack, in the task runner or a (scheduled) workflow. Another tool is added with accept:.

Why

Coverage says a line ran; a surviving mutant says the tests would not notice if it were wrong.

Fix

Add the stack’s mutation tool for the core packages, as a mutate target run weekly or on release (see https://fleetlint.org/stacks/).

Agent instruction: Add a mutate target that runs the stack’s mutation tool on the core packages with a survivor threshold, and a weekly workflow that calls it.

Sources


Generated by fleetlint docs from catalog v0.8.0.