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: Mutation Testing — Campaign Configuration (mewt/muton)4---56# Mutation Testing — Campaign Configuration (mewt/muton)78> **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`.910## When to Use1112Use this skill when the user:13- Mentions "mewt", "muton", or "mutation testing"14- Needs to configure or optimize a mutation testing campaign15- Wants to run `mewt run` and needs help getting set up first1617## When NOT to Use1819Do not use this skill when the user:20- Wants to analyze or report on completed campaign results21- Asks about tests or coverage without mentioning mutation testing2223---2425## Quick Start2627Load [workflows/configuration.md](workflows/configuration.md) — a 5-phase guide from `mewt init` to a validated, ready-to-run campaign.2829**General question or unfamiliar command?**30Run `mewt --help` or `mewt <subcommand> --help`, then assist.3132---3334## Reference Index3536| File | Content |37|------|---------|38| [workflows/configuration.md](workflows/configuration.md) | 5-phase guide: init, scope, optimize, validate, run |39| [references/optimization-strategies.md](references/optimization-strategies.md) | Per-file targeting, two-phase campaigns, mutation type filtering |4041---4243## Essential Commands4445```bash46# Initialize and mutate47mewt init # Create mewt.toml and mewt.sqlite48mewt mutate [paths] # Generate mutants without running tests49mewt run [paths] # Run the full campaign5051# Inspect configuration and scope52mewt print config # View effective configuration53mewt print targets # Table of all targeted files54mewt print mutations --language [lang] # Available mutation types55mewt status # Mutant count and per-file breakdown5657# Investigate specific mutants58mewt print mutants --target [path] # All mutants for a file59mewt print mutants --severity high # Filter by severity60mewt print mutant --id [id] # View mutated code diff61mewt test --ids [ids] # Re-test specific mutants62```6364---6566## What Results Mean6768- **Caught/TestFail**: Tests detected the mutation (good)69- **Uncaught**: Mutation survived — indicates untested logic70- **Timeout**: Tests took too long, inconclusive71- **Skipped**: A more severe mutant already failed on the same line
DojoGenesis