Skip to content
Cucumber for the JVM
Java Scala Cucumber HTML Ruby Clojure Other
Find file
Latest commit 131f810 Apr 13, 2016 @brasmusson brasmusson Merge #986 'Use Integer.compare() in HookComparator'
Also Update History.md.
Failed to load latest commit information.
android Upgrade to JUnit 4.12 ref #889 Jul 27, 2015
clojure [maven-release-plugin] prepare for next development iteration Jul 23, 2015
core Use Integer.compare() in HookComparator in order to guard against pos… Apr 6, 2016
doc Fix JavaDoc stylesheet so it works with Java 7. Closes #457 Mar 11, 2013
examples Add alwaysRun=true to the TestNG example's AfterClass method Jan 26, 2016
gosu Adding examples modules back so their versions get bumped on release Jul 24, 2015
groovy [maven-release-plugin] prepare for next development iteration Jul 23, 2015
guice Correct the properties file name in the Guice Package.html. Fixes #913. Sep 25, 2015
java Replace \n with %n so that tests work on Windows. Apr 1, 2016
java8 Remove accidental temp dependency Oct 13, 2015
jruby [maven-release-plugin] prepare for next development iteration Jul 23, 2015
junit Let JUnitReporter treat Pending results in hooks correctly. Feb 18, 2016
jython [maven-release-plugin] prepare for next development iteration Jul 23, 2015
needle [maven-release-plugin] prepare for next development iteration Jul 23, 2015
openejb [maven-release-plugin] prepare for next development iteration Jul 23, 2015
osgi [maven-release-plugin] prepare for next development iteration Jul 23, 2015
picocontainer [maven-release-plugin] prepare for next development iteration Jul 23, 2015
rhino Fix global variable leak in Rhino Oct 27, 2015
scala [maven-release-plugin] prepare for next development iteration Jul 23, 2015
spring [maven-release-plugin] prepare for next development iteration Jul 23, 2015
testng Merge #956 'Always tear down TestNG cucumber tests'. Jan 26, 2016
weld [maven-release-plugin] prepare for next development iteration Jul 23, 2015
.gitignore added idea generated directories to .gitignore Sep 21, 2013
.travis-settings.xml Add travis config to deploy snapshots to sonatype. May 22, 2013
.travis.yml Stop IRC noise Oct 16, 2015
CONTRIBUTING.md Modify the release-sign-artifacts. Update Contributing.md Jul 8, 2015
History.md Merge #986 'Use Integer.compare() in HookComparator' Apr 13, 2016
LICENCE Update license May 15, 2014
README.md Update README.md Nov 12, 2015
cobertura.sh Added cobertura code coverage and started to clean up some cruftiness… May 1, 2012
cobertura.xml Added cobertura code coverage and started to clean up some cruftiness… May 1, 2012
pom.xml remove reference to decommissioned repository.codehaus.org repository Mar 1, 2016

README.md

Build Status Join the chat at https://gitter.im/cucumber/cucumber-jvm

Cucumber-JVM is a pure Java implementation of Cucumber that supports the most popular programming languages for the JVM.

You can run it with the tool of your choice.

Cucumber-JVM also integrates with all the popular Dependency Injection containers.

Documentation

Start Here.

Hello World

Check out the simple cucumber-java-skeleton starter project.

Downloading / Installation

Install

Bugs and Feature requests

You can register bugs and feature requests in the Github Issue Tracker.

You're most likely going to paste code and output, so familiarise yourself with Github Flavored Markdown to make sure it remains readable.

At the very least - use triple backticks:

```java
// Why doesn't this work?
@Given("I have (\\d+) cukes in my (.*)")
public void some_cukes(int howMany, String what) {
    // HALP!
}
```

Please consider including the following information if you register a ticket:

  • What cucumber-jvm version you're using
  • What modules you're using (cucumber-java, cucumber-spring, cucumber-groovy etc)
  • What command you ran
  • What output you saw
  • How it can be reproduced

How soon will my ticket be fixed?

The best way to have a bug fixed or feature request implemented is to fork the cucumber-jvm repo and send a pull request. If the pull request has good tests and follows the coding conventions (see below) it has a good chance of making it into the next release.

If you don't fix the bug yourself (or pay someone to do it for you), the bug might never get fixed. If it is a serious bug, other people than you might care enough to provide a fix.

In other words, there is no guarantee that a bug or feature request gets fixed. Tickets that are more than 6 months old are likely to be closed to keep the backlog manageable.

Contributing fixes

See CONTRIBUTING.md

Something went wrong with that request. Please try again.