0.01
No commit activity in last 3 years
No release in over 3 years
Detect order dependencies in rspec test suites. Also print the minimal set of tests to reproduce the failure(s).
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

= 0.6.1
~> 1.6
= 1.3.17
~> 10.0

Runtime

= 0.7.3
> 2.12
 Project Readme

DEPRECATED

RSpec has a command that will perform the same features as this project. Prefer to use that instead.

$ rspec --seed 1234 --bisect

See their documentation for more details.

Rspec::Bisect

Detect order dependencies in rspec test suites and print a minimal list of tests required to reproduce it.

Installation

Add this line to your application's Gemfile:

gem 'rspec-bisect'

And then execute:

$ bundle

Or install it yourself as:

$ gem install rspec-bisect

Usage

So you think you have order dependencies? This tool will tell you exactly which tests are causing that dependency. It won't try to figure out if one exists or tell you why it's happening.

Have your rspec config set so that rspec --seed 1234 runs your test suite with the specified seed.

Run rspec-bisect --seed 1234 and rspec-bisect will tell you which tests are from an order dependency and the minimum tests required to reproduce it.

Contributing

  1. Fork it ( https://github.com/[my-github-username]/rspec-bisect/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