CI::Reporter::Cucumber

Connects Cucumber to CI::Reporter, and then to your CI system.

The latest release of Cucumber 1.3 is supported.

Add this line to your application's Gemfile:

gem 'ci_reporter_cucumber'

And then install it:

$ bundle

Require the reporter in your Rakefile, and ensure that ci:setup:cucumber is a dependency of your Cucumber task:

require 'ci/reporter/rake/cucumber'

# ...
# Rake code that creates a task called `:cucumber`
# ...

task :cucumber => 'ci:setup:cucumber'

If you want to treat undefined and pending steps as failures (instead of skipping them), set the CI_PENDING_IS_FAILURE environment variable to true.

Refer to the shared documentation for details on setting up CI::Reporter.

If you use both Cucumber and Spinach, you are likely to see strange errors due to gherkin and gherkin-ruby both being loaded. Choose only one of these frameworks.

1. Fork it ( https://github.com/ci-reporter/ci_reporter_cucumber/fork )
2. Create your feature branch (git checkout -b my-new-feature)
3. Add a failing test.
4. Commit your changes (git commit -am 'Add some feature')
5. Ensure tests pass.
6. Push to the branch (git push origin my-new-feature)
7. Create a new Pull Request