Cucumber PIT integration plugin

Out of the box mutation testing tool PIT does not take in account cucumber features and scenarios to kill mutants in your code.
The purpose of this plugin is to make PIT use your cucumber scenarios the same way it use already your regular junit tests.

Limitations

Today, PIT plugins require maven or Gradle. You cannot for the moment use this plugin 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.1.4</version>
			<configuration>
				<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.2</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.1.4'
       pitest 'com.github.alexvictoor:pitest-cucumber-plugin:0.2'
   }
}

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
0.1	1.1.8
0.2	1.2.2

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 verbise flag in the configuration section of the maven plugin:

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