redundant-test
Two tests that kill exactly the same mutants.
0 / 12 true, 95% Wilson interval 0.00 to 0.24, on 5 open-source projects.
Shown with --all. Never gates, even with an override.
Hidden by default
Its review dropped it: none of its decided findings held. Tests that kill the same mutants still differed in what they checked.
It still runs: spirolo check --all shows its findings, labelled, and it never fails the build, even with an override.
What it reports
In a Stryker mutation report, these tests kill exactly the same mutants, so deleting all but one would lose nothing the suite checks.
What to do
Merge them into one test, or delete the extras.
What it reads
The rule reads mutation reports named in inputs.mutation (by default **/reports/mutation/mutation.json). It never runs a mutation engine.
spirolo explain redundant-test prints the same claim and status from your installed binary.