Skip to content
A reporter for Spinach that writes in a file all failed scenarios in order to re-execute them.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
examples
lib
tasks
.editorconfig
.gitignore
.ruby-gemset
.ruby-version
Gemfile
LICENSE
README.md
spinach-rerun-reporter.gemspec

README.md

spinach-rerun-reporter

A reporter for Spinach that writes in a file all failed scenarios in order to re-execute them.

Status

Gem Depfu

Installation

Add this line to your application's Gemfile:

group :development, :test do
  gem 'spinach-rerun-reporter'
end

And then execute:

$ bundle install

Usage

$ bundle exec spinach -r rerun

When a scenario fails, the reporter writes the feature file and line in the file specified in SPINACH_RERUN_FILE environment variable which defaults to tmp/spinach-rerun.txt if not exists.

How to rerun

In order to rerun the failing scenarios you can use this script.

Rails

If Rails is present, this gem adds a Rake task to your project that automatize the rerun process.

$ rake spinach:rerun

You can use the following environment variables to configure it:

Variable Description Default
SPINACH_RERUN_TAGS Specify tags for Spinach nil
SPINACH_RERUN_FILE Specify the rerun file tmp/spinach-rerun.txt
SPINACH_RERUN_RETRY_COUNT Specify the number of retry attemps 3
SPINACH_RERUN_PREPEND_CMD Specify a prefix for run Spinach command nil

Contributing

  1. Fork it ( https://github.com/javierav/spinach-rerun-reporter/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request

Versioning

spinach-rerun-reporter uses Semantic Versioning 2.0.0

License

Copyright (c) 2018 Javier Aranda - Released under MIT license

You can’t perform that action at this time.