nw-mutation-test
FeaturedRuns feature-scoped mutation testing to validate test suite quality. Use after implementation to verify tests catch real bugs (kill rate >= 80%).
Install
Quality Score: 95/100
Skill Content
Details
- Author
- nWave-ai
- Repository
- nWave-ai/nWave
- Created
- 9 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
mutation-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 mutant," "mutation coverage," or "is our coverage strong." For line coverage see code-coverage. For overall strategy see test-strategy.
targeted-mutation-testing
Use when a changed production class or component has branching, lifecycle or asynchronous behavior, guards, error recovery, authentication, serialization, or an external-integration seam and needs file-scoped mutation testing before completion.
mutation-test
Mutation testing with two engines. Uses the project's NATIVE mutation runner (StrykerJS / Infection / mutmut / PIT / cargo-mutants) when one is configured — installing it on explicit consent when it is not — for a reproducible, comparable score; and an LLM-guided engine for the mutation classes native mutators cannot express: error-path removal, state mutation, async hazards, and security guard removal. Generates mutations, executes them against the relevant tests, and FIXES the tests whose gaps let a mutation survive — surviving mutants are closed in-run, not handed to another skill. Emits the cross-tool stryker-mutator.io/report.schema.json report alongside its own artifact. Flags: [path] (scope), full, --max N, --category, --runner auto|native|llm|hybrid, --break N, --no-install, --dry-run, --quick, --report-only.