mutastic ignore

Record a decision not to test one mutant. It goes in .mutastic/ignores.yaml with its line and the reason, to commit and review, and lapses when that line changes. --remove takes one back; ignore --prune takes away every one that has lapsed.

Usage

mutastic ignore ID [DIR] [:MODULE] --reason=WHY

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

./gradlew mutasticIgnore \
  -Pmutastic.mutant=m855c8e3c \
  -Pmutastic.reason="only logs"
./gradlew mutasticIgnore \
  -Pmutastic.mutant=m855c8e3c \
  -Pmutastic.remove
./gradlew mutasticIgnore \
  -Pmutastic.prune

mvn mutastic:ignore \
  -Dmutastic.mutant=m855c8e3c \
  -Dmutastic.reason="only logs"
mvn mutastic:ignore \
  -Dmutastic.mutant=m855c8e3c \
  -Dmutastic.remove
mvn mutastic:ignore -Dmutastic.prune

mutastic ignore \
  m855c8e3c \
  --reason="only logs"
mutastic ignore --remove m855c8e3c
mutastic ignore --prune

Options

`--reason=WHY`

Why the mutant isn't worth a test: every ignore says.

Gradle	`-Pmutastic.reason=WHY`
Maven	`-Dmutastic.reason=WHY`
Command line	`--reason=WHY`

./gradlew mutasticIgnore \
  -Pmutastic.mutant=m855c8e3c \
  -Pmutastic.reason="only logs"

mvn mutastic:ignore \
  -Dmutastic.mutant=m855c8e3c \
  -Dmutastic.reason="only logs"

mutastic ignore \
  m855c8e3c \
  --reason="only logs"

`--remove`

Take the mutant's ignore away, so it runs again.

Gradle	`-Pmutastic.remove`
Maven	`-Dmutastic.remove`
Command line	`--remove`

./gradlew mutasticIgnore \
  -Pmutastic.mutant=m855c8e3c \
  -Pmutastic.remove

mvn mutastic:ignore \
  -Dmutastic.mutant=m855c8e3c \
  -Dmutastic.remove

mutastic ignore --remove m855c8e3c

`--prune`

Take away every ignore whose code has changed.

Gradle	`-Pmutastic.prune`
Maven	`-Dmutastic.prune`
Command line	`--prune`