nw-mutation-test

Featured

Runs feature-scoped mutation testing to validate test suite quality. Use after implementation to verify tests catch real bugs (kill rate >= 80%).

Testing & QA 636 stars 68 forks Updated today MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# NW-MUTATION-TEST: Feature-Scoped Mutation Testing **Wave**: QUALITY_GATE **Agent**: Crafter (nw-software-crafter) ## Overview Run mutation testing against implementation files from the current feature. Extracts targets from execution-log.json|generates feature-scoped configs|delegates to software-crafter. Uses cosmic-ray (Python)|PIT (Java)|Stryker (JS/TS/C#). ## Context Files Required - `docs/feature/{feature-id}/deliver/execution-log.json` - Implementation file extraction - `scripts/mutation/generate_scoped_configs.py` - Automated config generation (if available) ## Pre-Invocation Orchestrator performs before delegating: 1. **Extract files** — Read `execution-log.json`, extract implementation files from `completed_steps[].files_modified.implementation`. Gate: file list non-empty. 2. **Verify on disk** — Check all extracted files exist on disk. Gate: zero missing files. 3. **Detect language** — Scan config files (pyproject.toml, pom.xml, package.json, etc.) to select tool. Gate: language identified. 4. **Confirm tests pass** — Run `pytest -x {test_scope}` (or equivalent). Gate: exit code 0, no failures. 5. **Ensure mutation venv** — For Python, verify `.venv-mutation/` exists with cosmic-ray installed. Gate: `cosmic-ray --version` succeeds. ## Agent Invocation @nw-software-crafter Execute mutation testing for project {feature-id}. **Context to pass inline (agent has no Skill access):** - Project ID - Implementation file list (from execution-log.json) - Test sco...

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

Testing & QA Listed

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.

5 Updated 4 weeks ago
aks-builds
Testing & QA Listed

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.

0 Updated 2 months ago
jonfazzaro
Code & Development Listed

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.

7 Updated today
greglas75