Skip to content
This repository

Cucumber for the JVM

Update the android-sdk used on Travis

The android-sdk r21.1 does not recognize android-8 anymore, not even
with the --all flag. When using the latest version, r22.6.2, then the
update sdk command needs to explicitly specify build-tools (with a
specific version), and answer y to a question about license.
latest commit 08e6b87a0a
Björn Rasmusson brasmusson authored
Octocat-spinner-32 android Set version 1.1.7-SNAPSHOT in AndroidManifest and example pom's
Octocat-spinner-32 clojure [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 core [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 doc Fix JavaDoc stylesheet so it works with Java 7. Closes #457
Octocat-spinner-32 examples Set version 1.1.7-SNAPSHOT in AndroidManifest and example pom's
Octocat-spinner-32 gosu [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 groovy [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 guice [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 ioke [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 java [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 jruby [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 junit [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 jython [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 needle [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 openejb [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 picocontainer [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 rhino [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 scala [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 spring [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 testng [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 weld [maven-release-plugin] prepare for next development iteration
Octocat-spinner-32 .gitignore added idea generated directories to .gitignore
Octocat-spinner-32 .travis-settings.xml Add travis config to deploy snapshots to sonatype.
Octocat-spinner-32 .travis.yml Update the android-sdk used on Travis
Octocat-spinner-32 CONTRIBUTING.md post-release updates
Octocat-spinner-32 History.md post-release updates
Octocat-spinner-32 LICENCE Add years
Octocat-spinner-32 README.md add waffle.io badge
Octocat-spinner-32 cobertura.sh Added cobertura code coverage and started to clean up some cruftiness…
Octocat-spinner-32 cobertura.xml Added cobertura code coverage and started to clean up some cruftiness…
Octocat-spinner-32 pom.xml [maven-release-plugin] prepare for next development iteration
README.md

Stories in Ready
Build Status

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. This page also links to examples. Look here for API docs.

Hello World

Check out the simple Hello World example.

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 3 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 as well as CONTRIBUTING.md

Coming from Cuke4Duke?

See Migration from Cuke4Duke

Something went wrong with that request. Please try again.