Skip to content
Skills Library
Programming · Testing

mutation-testing-setup

/mutation-testing-setup

Set up mutation testing with Stryker.NET to measure whether tests actually catch bugs, and interpret the mutation score and surviving mutants. Use this skill whenever the user wants mutation testing, Stryker, to know if their tests are any good, test quality beyond coverage, surviving mutants, or asks "are my tests actually testing anything / mutation score / Stryker setup". Always use this skill for mutation-testing requests; it configures Stryker and explains the results.

Licence
MIT
Last repository change
09.08.2026

Assessment and security

100/ 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.
Content35 / 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
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.08.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 with Stryker.NET to measure whether tests actually catch bugs, and interpret the mutation score and surviving mutants. Use this skill whenever the user wants mutation testing, Stryker, to know if their tests are any good, test quality beyond coverage, surviving mutants, or asks "are my tests actually testing anything / mutation score / Stryker setup". Always use this skill for mutation-testing requests; it configures Stryker and explains the results.

Original author description

Set up mutation testing with Stryker.NET to measure whether tests actually catch bugs, and interpret the mutation score and surviving mutants. Use this skill whenever the user wants mutation testing, Stryker, to know if their tests are any good, test quality beyond coverage, surviving mutants, or asks "are my tests actually testing anything / mutation score / Stryker setup". Always use this skill for mutation-testing requests; it configures Stryker and explains the results.

How it works

  1. Input — point it at your project
  2. Setup
  3. Reading results
  4. Principles
  5. How to use it & best prompts
Original SKILL.md headings · 42 lines, 277 words
SKILL.md preview
---
name: mutation-testing-setup
description: Set up mutation testing with Stryker.NET to measure whether tests actually catch bugs, and interpret the mutation score and surviving mutants. Use this skill whenever the user wants mutation testing, Stryker, to know if their tests are any good, test quality beyond coverage, surviving mutants, or asks "are my tests actually testing anything / mutation score / Stryker setup". Always use this skill for mutation-testing requests; it configures Stryker and explains the results.
category: Testing
version: 1.0.0
---

# Mutation Testing Setup (Stryker.NET)

Measure whether your tests actually catch bugs — not just execute code — with Stryker.NET, and turn surviving mutants into better tests.

## Input — point it at your project
Works on a target: a **project/test project** or **GitHub URL**. Find the test project: `find <target> -iname "*.Tests.csproj"`.

## Setup
```
dotnet tool install -g dotnet-stryker
cd path/to/Tests.Project
dotnet stryker
```
`stryker-config.json` (scope it so runs are fast):
```json
{
  "stryker-config": {
    "project": "MyApp.csproj",
    "test-projects": ["MyApp.Tests.csproj"],
    "mutate": ["**/Core/**/*.cs", "!**/Migrations/**"],
    "thresholds": { "high": 80, "low": 60, "break": 50 }
  }
}
```

## Reading results
- **Mutation score** = killed mutants / total. Higher = tests catch more injected bugs.
- **Surviving mutant** = Stryker changed the code (e.g. flipped `>` to `>=`, removed a statement) and **no test failed** → a real gap in your assertions.
- **Timeout/no-coverage** mutants = code not exercised at all (a coverage gap, see `test-coverage-gap-finder`).

For each meaningful survivor: add or strengthen an assertion so the mutation would be caught. A test that runs code without asserting its effect lets mutants survive.

## Principles
- **Coverage says code ran; mutation says tests would catch a bug.** Mutation is the truer quality signal.
- Scope mutation runs to important code (it's slow) — don't mutate the whole solution every CI run.
- Don't chase 100% — focus survivors in critical logic.
- Treat survivors as "missing assertion", not "add a test for coverage".

## How to use it & best prompts
"Set up Stryker mutation testing", "are my tests actually catching bugs", "explain these surviving mutants", "improve my tests so these mutants die". Pairs with `test-coverage-gap-finder` and `xunit-test-generator`.
Files in this package (2)
  • SKILL.md 2 KB
  • USAGE.md 1 KB

Versions

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

Database snapshot: 13.11.2026 · package version 6b5bbb77e0ba (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
    Set up and run mutation testing with Stryker, including full-project and focused diff runs against the current review base, then use surviving mutants to strengthen weak or missing tests. Use as the end-of-phase PR-readiness gate after implementation and refactoring are…
  • 100mutation-testing
    Mutation testing quality gate with scenario coverage enforcement and structured evidence output. Detects project type and runs the right tool (cargo-mutants, Stryker, mutmut, Muzak), analyzes surviving mutants by mutation type (arithmetic, comparison, boolean, return value,…
  • 100stryker
    Use the open-source free `Stryker.NET` mutation testing tool for .NET. Use when a repo needs to measure whether tests actually catch faults, especially in critical libraries or domains. USE FOR: the repo uses or wants Stryker.NET; mutation testing is needed for high-risk code.…
  • 100mutation-testing
    Use when entering COMMIT & VERIFY phase, killing surviving mutants, verifying test quality via mutation score, or analyzing supported Stryker.NET, Node TAP StrykerJS, TypeScript StrykerJS with the Vitest runner or Python cosmic-ray results after the test baseline is green
  • 100mutation-testing
    Finds weak or missing tests by checking whether small code changes (mutants) would be caught by the test suite, then hands the gaps to TDD. Use when verifying test effectiveness, asking "would my tests catch this bug?", hunting surviving mutants, or checking changed code after…
  • 100mutation-test
    Runs StrykerJS mutation testing on the business logic delivered for a use case to measure whether the unit tests actually detect broken behaviour, not just execute it. Reports the mutation score and every surviving mutant with the assertion that would kill it. Runs automatically…

Feedback and reports

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