mutation-testing

Featured

Configures mewt or muton mutation testing campaigns — scopes targets, tunes timeouts, and optimizes long-running runs. Use when the user mentions mewt, muton, mutation testing, or wants to configure or optimize a mutation testing campaign.

Testing & QA 8,273 stars 715 forks Updated 6 days ago CC-BY-SA-4.0

Install

View on GitHub

Quality Score: 93/100

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

Skill Content

# Mutation Testing — Campaign Configuration (mewt/muton) > **Note**: muton and mewt share identical interfaces but target different languages — mewt for general-purpose languages (Rust, Solidity, Go, TypeScript, JavaScript), muton for TON smart contracts (Tact, Tolk, FunC). All examples use `mewt` commands, but they work exactly the same with `muton`. File names change accordingly: `mewt.toml` → `muton.toml`, `mewt.sqlite` → `muton.sqlite`. ## When to Use Use this skill when the user: - Mentions "mewt", "muton", or "mutation testing" - Needs to configure or optimize a mutation testing campaign - Wants to run `mewt run` and needs help getting set up first ## When NOT to Use Do not use this skill when the user: - Wants to analyze or report on completed campaign results - Asks about tests or coverage without mentioning mutation testing --- ## Quick Start Load [workflows/configuration.md](workflows/configuration.md) — a 5-phase guide from `mewt init` to a validated, ready-to-run campaign. **General question or unfamiliar command?** Run `mewt --help` or `mewt <subcommand> --help`, then assist. --- ## Reference Index | File | Content | |------|---------| | [workflows/configuration.md](workflows/configuration.md) | 5-phase guide: init, scope, optimize, validate, run | | [references/optimization-strategies.md](references/optimization-strategies.md) | Per-file targeting, two-phase campaigns, mutation type filtering | --- ## Essential Commands ```bash # Initialize and mu...

Details

Author
trailofbits
Repository
trailofbits/skills
Created
10 months ago
Last Updated
6 days ago
Language
Python
License
CC-BY-SA-4.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

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
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

mutation-test

Proves a test actually checks something, by breaking the behaviour it claims to cover and confirming it goes red. Use when a test, fixture, assertion or guard has been reported as working and you want evidence rather than a green run, or to check a claim that some code is dead, unused or unreachable. Also use it to SCOPE that work to a PR or a diff — shortlisting the changed lines and giving you a throwaway checkout to break them in. It does not mutate anything for you. Triggers on "mutation test", "mutation testing", "prove it fails", "are these tests real", "does this test actually assert anything", "is that assertion live", "did you verify it's not vacuous", "which changed lines are tested", "is this PR actually covered", "are the changes in PR 123 tested", "check the coverage on this diff", "mutation test this PR", or any claim that a test passes being offered as evidence the behaviour is correct. Also use it proactively before reporting harness or fixture work as done.

1 Updated 3 days ago
LunarCommand