-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove 'rspec-instafail' dependency from gemspec? #20
Comments
Hey Doug, I really want to get rid of that dependency, but --fail-fast stops the suite after the first failure (http://jeffkreeftmeijer.com/2010/making-rspec-stop-operation-immediately-after-failing/). Using instafail, the specs would continue running after the first fail, but print out their error immediately. I'll keep this open, since this is still something we need to do. Thanks for reporting! |
rspec-instafail changed things on v0.2.3. fuubar.rb:3:in `require': cannot load such file -- rspec/instafail |
…, #29, #20, #33 * feature/remove-rspec-instafail: Big refactoring to use the capabilities exposed by RSpec's formatters as well as replacing the specs with ones which are more representative Add .ruby-version file Use RSpec's helpers to output the failures at the proper time Remove all references to instafail Remove rspec-instafail from the project
…, #29, #20, #33 * feature/remove-rspec-instafail: Big refactoring to use the capabilities exposed by RSpec's formatters as well as replacing the specs with ones which are more representative Add .ruby-version file Use RSpec's helpers to output the failures at the proper time Remove all references to instafail Remove rspec-instafail from the project
This issue has been closed automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hey, I just noticed that RSpec core has a
--fail-fast
command line option now. Do you still need the'rspec-instafail'
dependency in the gemspec, or can it be removed?The text was updated successfully, but these errors were encountered: