A reporter for Spinach that writes in a file all failed scenarios in order to re-execute them.
Add this line to your application's Gemfile:
group :development, :test do
gem 'spinach-rerun-reporter'
end
And then execute:
$ bundle install
$ 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.
In order to rerun the failing scenarios you can use this script.
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 |
- Fork it ( https://github.com/javierav/spinach-rerun-reporter/fork )
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Create a new Pull Request
spinach-rerun-reporter uses Semantic Versioning 2.0.0
Copyright (c) 2018 Javier Aranda - Released under MIT license