Cucumber PIT integration plugin

Out of the box, the mutation testing tool Pitest does not run cucumber features and scenarios to kill mutants in your code.
This plugin enables PIT to run cucumber scenarios the same way it runs your regular junit tests.

Limitations

Today, PIT plugins require maven or Gradle. This plugin does not currently work with the PIT command line interface.

Usage

Maven

Just add this plugin as a maven dependency of PIT maven plugin. Below an example:

<build>
  <plugins>
    <plugin>
      <groupId>org.pitest</groupId>
      <artifactId>pitest-maven</artifactId>
      <version>1.5.1</version>
      <configuration>
        <testPlugin>Cucumber</testPlugin>
    <targetClasses>
      <param>your.sut.package.*</param>
    </targetClasses>
    <targetTests>
      <param>your.test.package.*Test</param>
    </targetTests>
    <outputFormats>
          <outputFormat>XML</outputFormat>
          <outputFormat>HTML</outputFormat>
    </outputFormats>
      </configuration>
      <dependencies>
        <dependency>
      <groupId>com.github.alexvictoor</groupId>
      <artifactId>pitest-cucumber-plugin</artifactId>
      <version>0.10.0</version>
    </dependency>
      </dependencies>
    </plugin>
  </plugins>
</build>

Then as usual you just need to run pit using the following command:

mvn org.pitest:pitest-maven:mutationCoverage

Gradle

Just create pitest configuration and add this plugin as a dependency in a buildscript block in your root Gradle project. Below an example:

buildscript {
   repositories {
       mavenCentral()
   }
   configurations.maybeCreate("pitest")
   dependencies {
       classpath 'info.solidsoft.gradle.pitest:gradle-pitest-plugin:1.4.9'
       pitest 'com.github.alexvictoor:pitest-cucumber-plugin:1.0'
   }
}

Then as usual you just need to run pit using the following command:

gradle pitest

See PIT plugin for Gradle README for more general configuration parameters.

Compatibility Matrix

Pitest Cucumber Plugin	tested against Cucumber	with Pitest Maven Plugin	notes
0.1	1.1.8	1.1.5
0.2	1.2.2	1.1.5
0.3	1.2.2	1.1.5
0.4	1.2.2	1.1.11
0.5	1.2.2	1.4.2
0.6	2.0.0 - 3.0.2	1.4.2
0.7	4.0.0 - 4.2.0	1.4.3
0.8	4.2.0	1.4.5
0.9	5.1.0 - 5.7.0	1.4.2 - 1.4.11	Using both deprecated and new annotations (io.cucumber.junit.Cucumber and io.cucumber.junit.CucumberOptions)
0.10	5.1.0 - 5.7.0	1.5.0 - 1.5.1	Using both deprecated and new annotations (io.cucumber.junit.Cucumber and io.cucumber.junit.CucumberOptions)
0.11.1	7.2.x	1.7.x

Troubleshooting

Before raising an issue on github or in the PIT's users mailing-list, please try to run the analysis in verbose mode. You just need to add a verbose flag in the configuration section of the maven plugin:

<configuration>
    ...
    <verbose>true</verbose>
</configuration>

If you are updating a project that was using pitest 1.1, be aware of the "testPlugin" config key in the maven configuration block:

<testPlugin>Cucumber</testPlugin>

If you forget this one, the pitest cucumber plugin will not be used and no test will be run...

alexvictoor / pitest-cucumber-plugin

readme