dotnet-stryker

Run Stryker.NET mutation testing on .NET projects to measure test suite fault detection.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/zhenpengLai/myuseskill --skill dotnet-stryker-zhenpenglai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-stryker
Source: https://github.com/zhenpengLai/myuseskill/tree/main/dotnet-stryker
Command: npx skills add https://github.com/zhenpengLai/myuseskill --skill dotnet-stryker-zhenpenglai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code coverage alone cannot tell whether tests actually catch bugs. This Skill configures and runs Stryker.NET mutation testing on .NET projects so teams can measure whether their test suites detect real faults in critical code. ## Core Features & Use Cases - Mutation Testing Execution: Run Stryker.NET against targeted projects or solutions with configurable mutation levels, thresholds, and reporters. - Scoped CI Integration: Set up incremental or scheduled mutation runs that stay out of the fastest PR path, with threshold gates tuned for new, legacy, or high-risk code. - Bootstrap and Verification: Detect existing tool manifests, install dotnet-stryker as a local tool, and produce reproducible commands with a structured status report. - Use Case: A team wants to validate tests for a critical domain layer. The Skill installs Stryker.NET locally, scopes mutations to the domain project, runs the analysis, and returns the mutation score with surviving-mutant guidance. ## Quick Start Ask the AI to add Stryker.NET mutation testing to a specific .NET project and report the mutation score for its critical code paths.

Frequently Asked Questions about dotnet-stryker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run mutation testing on a .NET project?▼

Install the dotnet-stryker tool with dotnet tool install dotnet-stryker, then run dotnet stryker in the project directory. You can target a specific project with --project MyProject.csproj or a solution with --solution MySolution.sln.

What is a good mutation score threshold for Stryker.NET?▼

Thresholds depend on context: new critical code often uses break at 70, established production code at 50, and high-risk domain logic at 85. Start conservative and raise the break threshold as test quality improves.

Should mutation testing run on every pull request?▼

Usually no, because full mutation runs are too slow for large solutions. Use incremental mode with --since --since-target main for changed code, and schedule full runs nightly or before releases.

Why do mutants survive even with high code coverage?▼

Survived mutants mean tests passed despite a code change, often due to missing assertions, weak boundary tests, untested error paths, or unverified side effects. Coverage measures execution, not fault detection.

When should I not use Stryker.NET mutation testing?▼

Avoid it when the test suite is flaky or slow, since mutation testing amplifies those problems, and when basic build, test, and coverage gates are not yet stable. It is also unnecessary for simple coverage collection.