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 — 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 |
5-phase guide: init, scope, optimize, validate, run |
| references/optimization-strategies.md |
Per-file targeting, two-phase campaigns, mutation type filtering |
Essential Commands
# Initialize and mutate
mewt init # Create mewt.toml and mewt.sqlite
mewt mutate [paths] # Generate mutants without running tests
mewt run [paths] # Run the full campaign
# Inspect configuration and scope
mewt print config # View effective configuration
mewt print targets # Table of all targeted files
mewt print mutations --language [lang] # Available mutation types
mewt status # Mutant count and per-file breakdown
# Investigate specific mutants
mewt print mutants --target [path] # All mutants for a file
mewt print mutants --severity high # Filter by severity
mewt print mutant --id [id] # View mutated code diff
mewt test --ids [ids] # Re-test specific mutants
What Results Mean
- Caught/TestFail: Tests detected the mutation (good)
- Uncaught: Mutation survived — indicates untested logic
- Timeout: Tests took too long, inconclusive
- Skipped: A more severe mutant already failed on the same line
1---2name: mutation-testing3description: "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."4allowed-tools: Read Write Bash Grep5metadata:6 source: https://skillmd.com/skills/trailofbits/mutation-testing7---89# Mutation Testing — Campaign Configuration (mewt/muton)1011> **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`.1213## When to Use1415Use this skill when the user:16- Mentions "mewt", "muton", or "mutation testing"17- Needs to configure or optimize a mutation testing campaign18- Wants to run `mewt run` and needs help getting set up first1920## When NOT to Use2122Do not use this skill when the user:23- Wants to analyze or report on completed campaign results24- Asks about tests or coverage without mentioning mutation testing2526---2728## Quick Start2930Load [workflows/configuration.md](workflows/configuration.md) — a 5-phase guide from `mewt init` to a validated, ready-to-run campaign.3132**General question or unfamiliar command?**33Run `mewt --help` or `mewt <subcommand> --help`, then assist.3435---3637## Reference Index3839| File | Content |40|------|---------|41| [workflows/configuration.md](workflows/configuration.md) | 5-phase guide: init, scope, optimize, validate, run |42| [references/optimization-strategies.md](references/optimization-strategies.md) | Per-file targeting, two-phase campaigns, mutation type filtering |4344---4546## Essential Commands4748```bash49# Initialize and mutate50mewt init # Create mewt.toml and mewt.sqlite51mewt mutate [paths] # Generate mutants without running tests52mewt run [paths] # Run the full campaign5354# Inspect configuration and scope55mewt print config # View effective configuration56mewt print targets # Table of all targeted files57mewt print mutations --language [lang] # Available mutation types58mewt status # Mutant count and per-file breakdown5960# Investigate specific mutants61mewt print mutants --target [path] # All mutants for a file62mewt print mutants --severity high # Filter by severity63mewt print mutant --id [id] # View mutated code diff64mewt test --ids [ids] # Re-test specific mutants65```6667---6869## What Results Mean7071- **Caught/TestFail**: Tests detected the mutation (good)72- **Uncaught**: Mutation survived — indicates untested logic73- **Timeout**: Tests took too long, inconclusive74- **Skipped**: A more severe mutant already failed on the same line