Cucumber for the JVM
Java Scala Cucumber HTML Ruby Clojure Other
Permalink
Failed to load latest commit information.
android Fixing squid:S1118 - Utility classes should not have public constructors Dec 25, 2015
clojure [maven-release-plugin] prepare for next development iteration Jul 23, 2015
core Merge #978 'Double-check for directory exists in ...'. Jul 31, 2016
doc Fix JavaDoc stylesheet so it works with Java 7. Closes #457 Mar 11, 2013
examples Merge branch 'master' of https://github.com/holtzermann17/cucumber-jvm May 11, 2016
gosu Adding examples modules back so their versions get bumped on release Jul 24, 2015
groovy Test added: Fixed NPE in List parameter conversion Mar 31, 2016
guice Merge branch 'staging/Utility-classes-should-not-have-public-construc… May 11, 2016
java Bring back the Java8StepDefinitionTest in the java module. Jul 31, 2016
java8 Working on closing over local variables Jul 31, 2016
jruby [maven-release-plugin] prepare for next development iteration Jul 23, 2015
junit fixed copy&paste error with junit args Jul 25, 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 The package org.ops4j.pax.exam.util is optional for cucumber-osgi Apr 30, 2016
picocontainer #993 tests for Picocontainer lifecycle management May 18, 2016
rhino Fix global variable leak in Rhino Oct 27, 2015
scala [maven-release-plugin] prepare for next development iteration Jul 23, 2015
spring cucumber-spring test fix Jan 20, 2016
testng Merge branch 'staging/Collection.isEmpty-should-be-used-to-test-for-e… May 11, 2016
weld [maven-release-plugin] prepare for next development iteration Jul 23, 2015
.gitignore Git should ignore the TestNG output directory Apr 15, 2016
.travis-settings.xml Add travis config to deploy snapshots to sonatype. May 22, 2013
.travis.yml Fix the snapshot deployment on Travis. Aug 2, 2016
CONTRIBUTING.md Modify the release-sign-artifacts. Update Contributing.md Jul 8, 2015
History.md Attribution. Closes #916, closes #924, closes #929. Jul 31, 2016
LICENCE Remove year from Copyright May 26, 2016
README.md Add version badge May 2, 2016
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

Maven Central 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