Skip to content
Skills Library
Programming · Testing

mutation-testing-setup

/mutation-testing-setup

Set up mutation testing for a project: pick the tool for the stack (Stryker for JS/TS and .NET, PIT for Java/Kotlin, mutmut or cosmic-ray for Python, Infection for PHP, go-mutesting for Go), scope it to business-critical code, configure timeouts and reporters, and run a first baseline. Use when starting with mutation testing or when coverage is high but bugs still slip through.

Licence
MIT
Last repository change
10.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Set up mutation testing for a project: pick the tool for the stack (Stryker for JS/TS and .NET, PIT for Java/Kotlin, mutmut or cosmic-ray for Python, Infection for PHP, go-mutesting for Go), scope it to business-critical code, configure timeouts and reporters, and run a first baseline. Use when starting with mutation testing or when coverage is high but bugs still slip through.

Original author description

Set up mutation testing for a project: pick the tool for the stack (Stryker for JS/TS and .NET, PIT for Java/Kotlin, mutmut or cosmic-ray for Python, Infection for PHP, go-mutesting for Go), scope it to business-critical code, configure timeouts and reporters, and run a first baseline. Use when starting with mutation testing or when coverage is high but bugs still slip through.

How it works

  1. Tool per stack
  2. Steps
  3. Output
Original SKILL.md headings · 24 lines, 182 words
SKILL.md preview
---
name: mutation-testing-setup
description: "Set up mutation testing for a project: pick the tool for the stack (Stryker for JS/TS and .NET, PIT for Java/Kotlin, mutmut or cosmic-ray for Python, Infection for PHP, go-mutesting for Go), scope it to business-critical code, configure timeouts and reporters, and run a first baseline. Use when starting with mutation testing or when coverage is high but bugs still slip through."
---

# Mutation testing setup

Line coverage says the code ran; the mutation score says a test would fail if the code were wrong.

## Tool per stack
| Stack | Tool | First run |
|---|---|---|
| JS / TS | StrykerJS | `npx stryker init` then `npx stryker run` |
| .NET | Stryker.NET | `dotnet tool install -g dotnet-stryker` then `dotnet stryker` |
| Java / Kotlin | PIT (pitest) | `mvn org.pitest:pitest-maven:mutationCoverage` or the Gradle plugin |
| Python | mutmut / cosmic-ray | `mutmut run --paths-to-mutate src/billing` |
| PHP | Infection | `vendor/bin/infection` |

## Steps
1. **Scope**: one package with business logic (pricing, rules, calculations). Exclude generated code, DTOs, logging.
2. **Configure**: test command, timeout factor, concurrency, the JSON reporter (`mutation-testing-report-schema` for Stryker, `XML`/`HTML` for PIT).
3. **Baseline**: run once, record the score and duration.
4. **Read the report** with `mutation-report-digest`, then triage with `surviving-mutant-triage`.
5. Make it part of the routine: nightly on critical packages, or incremental on PRs (`mutation-score-gate`).

## Output
Config file, commands, baseline score and duration, and the 10 most important survivors.

Versions

RepositoryScoreLicence
This page · RobinBeraud/claude-qa-skills90MIT
stefanthecode/dotnet-ai-toolkit100MIT

Database snapshot: 13.11.2026 · package version cb7084fff5f2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100mutation-testing
    When the user wants to measure or improve the *quality* of their existing test suite via mutation testing. Use when the user mentions "mutation testing," "mutation score," "Stryker," "PIT," "PITest," "mutmut," "go-mutesting," "Mutmut," "mutator," "killed mutant," "surviving…
  • 100mutation-testing
    Mutation testing with Stryker (TS/JS) and mutmut (Python). Use when finding weak tests that pass on mutated code, or improving test quality through mutation analysis.
  • 90mutation-test-runner
    Runs mutation testing on already-covered code and turns each surviving mutant into a specific missing assertion, exposing tests that execute code but verify nothing. Use when line coverage is high yet a bug slipped through, when reviewing a critical module (pricing, permissions,…
  • 90infection-mutation-testing
    Use when the user asks to run Infection mutation testing, check the mutation score (MSI), find out why mutants escaped, or write tests that kill escaped mutants in a PHP project. Not for general PHPUnit runs or coverage questions.
  • 95wicked-garden-qe-mutation-test-engineer
    Mutation-testing specialist — Stryker (JS/TS), Mutmut (Python), Pitest (Java), go-mutesting (Go). Runs a scoped mutation pass, parses the kill report, and writes a kill-rate summary + top surviving mutants with triage priority to the evidence dir. Records a verdict row that…
  • 100stryker-net-mutation
    Configures Stryker.NET for mutation testing of .NET Core / .NET Framework projects - installs `dotnet-stryker` global tool, scopes mutation to specific csproj, supports xUnit / NUnit / MSTest, authors `stryker-config.json` with thresholds, runs in CI. Use when a .NET test suite…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.