mutastic explain

Everything known of one mutant, with its tests run. Its card, the change in its bytecode, what its operator does, and its result in the last full run.

Usage

mutastic explain ID [DIR] [:MODULE]

The build plugins run the same command, with each option as a mutastic. property of the same name.

./gradlew mutasticExplain \
  -Pmutastic.mutant=m855c8e3c

mvn mutastic:explain \
  -Dmutastic.mutant=m855c8e3c

mutastic explain m855c8e3c

Options

`--tests-from=MODULE`

Also run this module's tests over what this one's miss: :app, or dependents for every module that depends on it.

Gradle	`-Pmutastic.testsFrom=MODULE,…` or `testsFrom = …` in `mutastic { }`
Maven	`-Dmutastic.testsFrom=MODULE,…` or `<testsFrom>…</testsFrom>` in the plugin's configuration
Command line	`--tests-from=MODULE`

./gradlew :core:mutasticRun \
  -Pmutastic.testsFrom=dependents

mutastic {
    testsFrom = listOf("dependents")
}

mvn mutastic:run \
  -Dmutastic.testsFrom=dependents \
  -pl core

<configuration>
  <testsFrom>
    <module>dependents</module>
  </testsFrom>
</configuration>

mutastic run \
  . \
  :core \
  --tests-from=dependents

`--workers=N`

How many workers run side by side; half the cores, from 1 to 4, unless set.

Gradle	`-Pmutastic.workers=N` or `workers = …` in `mutastic { }`
Maven	`-Dmutastic.workers=N` or `<workers>…</workers>` in the plugin's configuration
Command line	`--workers=N`

./gradlew mutasticRun \
  -Pmutastic.workers=2

mutastic {
    workers = 2
}

mvn mutastic:run \
  -Dmutastic.workers=2

<configuration>
  <workers>2</workers>
</configuration>

mutastic run --workers=2

`--confirm-catches`

Run each catching test again on its own, to confirm the catch.

Gradle	`-Pmutastic.confirmCatches` or `confirmCatches = true` in `mutastic { }`
Maven	`-Dmutastic.confirmCatches` or `<confirmCatches>true</confirmCatches>` in the plugin's configuration
Command line	`--confirm-catches`

./gradlew mutasticRun \
  -Pmutastic.confirmCatches

mutastic {
    confirmCatches = true
}

mvn mutastic:run \
  -Dmutastic.confirmCatches

<configuration>
  <confirmCatches>true</confirmCatches>
</configuration>

mutastic run --confirm-catches

`--no-suggestions`

Don't look for a test to suggest for each missed mutant.

Gradle	`-Pmutastic.suggestions=false` or `suggestions = false` in `mutastic { }`
Maven	`-Dmutastic.suggestions=false` or `<suggestions>false</suggestions>` in the plugin's configuration
Command line	`--no-suggestions`

./gradlew mutasticRun \
  -Pmutastic.suggestions=false

mutastic {
    suggestions = false
}

mvn mutastic:run \
  -Dmutastic.suggestions=false

<configuration>
  <suggestions>false</suggestions>
</configuration>

mutastic run --no-suggestions

`--vocabulary=WORDS`

plain says caught and missed; classic says killed and survived.

One of plainclassic

Gradle	`-Pmutastic.vocabulary=WORDS`
Maven	`-Dmutastic.vocabulary=WORDS`
Command line	`--vocabulary=WORDS`
Environment	`MUTASTIC_VOCABULARY`

./gradlew mutasticRun \
  -Pmutastic.vocabulary=classic

mvn mutastic:run \
  -Dmutastic.vocabulary=classic

mutastic run --vocabulary=classic

`--color=WHEN`

Colour: auto uses it on a terminal that wants it.

One of autoalwaysnever

Gradle	`-Pmutastic.color=WHEN`
Maven	`-Dmutastic.color=WHEN`
Command line	`--color=WHEN`
Environment	`NO_COLOR, FORCE_COLOR`

`--hyperlinks=WHEN`

File locations as links a terminal can open: auto uses them on a terminal.

One of autoalwaysnever

Gradle	`-Pmutastic.hyperlinks=WHEN`
Maven	`-Dmutastic.hyperlinks=WHEN`
Command line	`--hyperlinks=WHEN`

`--progress=STYLE`

Progress on stderr: a bar on a terminal, counter lines in logs, none for agents.

One of autobarcounternone

Gradle	`-Pmutastic.progress=STYLE`
Maven	`-Dmutastic.progress=STYLE`
Command line	`--progress=STYLE`