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

quality/mutation-gate

Mutation testing runs on the core

Severityinfo
Tiers1
Stacksany
Scoperoot
Kindoutcome
Sourcelibrary v0.0.0-20261011205826-ecb4e9b3ffd4
Selected byfleetlint-recommended@0.1.0

Requirement

A mutation testing tool runs on the core packages, in the task runner or a (scheduled) workflow: gremlins for Go, mutmut for Python, cargo-mutants for Rust, Stryker for TypeScript, Pitest for the JVM, mutation_test for Dart. 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.

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


Generated by fleetlint docs from catalog v0.0.0-20261011205826-ecb4e9b3ffd4.