Permalink
..
Failed to load latest commit information.
src Use correct CucumberOptions Feb 23, 2015
.gitignore Words/tweaks Jan 13, 2013
README.md Words/tweaks Jan 13, 2013
build.gradle Prepare for release 2.0.1 Sep 17, 2017

README.md

Running Cucumber-JVM with step definitions in Java using Gradle's javaexec task

Credits

This work is based on dkowis/cucumber-jvm-groovy-example

Motivation

There exists a number of issues which prevent seamless integration of Cucumber-JVM and Gradle.

Solution

One possible solution is to use Cucumber's Main class to run your tests. You can do this by using the javaexec task in Gradle.

Running

In order to run your Cucumber tests execute:

gradle cucumber

Caveats

The Groovy example by David Kowis runs perfectly, but it uses Groovy step definitions.

If you're writing your step definitions in Java then the Gradle script needs to be changed slightly.

Here are some caveats:

  • The cucumber task has to depend on compileTestJava task in order to compile test sources
task cucumber() {
    dependsOn assemble, compileTestJava
    ...
}
  • The javaexec classpath should include main and test output directories. Otherwise Cucumber-JVM will not find your production classes/resources and step definitions respectively.
classpath = configurations.cucumberRuntime + sourceSets.main.output + sourceSets.test.output
  • Cucumber's --glue should be set to your package name (e.g. gradle.cucumber) and NOT to src/test/java
args = ['-f', 'pretty', '--glue', 'gradle.cucumber', 'src/test/resources']