Closed cburgmer closed 8 years ago
so rspec is not installed ? ... how can rspec-core be there and rspec is not ?
bundle exec rspec spec/ --fail-fast
or
# spec/spec_helper.rb
RSpec.configure do |c|
c.fail_fast = true
end
basically this gem is obsolete and should not be used ...
--fail-fast
will not run all other tests after a failure, while this gem does, a benefit to me.
I might be doing this wrong (and I don't have any clue about Ruby gem resolution), but my project references some rspec dependencies (though not directly rspec). I have instafail installed globally.
If I run bundle exec rspec
things seem to work fine, whereas just rspec
will produce above error.
I am running JRuby on Windows.
Happy to have bundle exec
as a solution for me, but also wouldn't mind understanding why an upgrade to rspec stopped working. Feel free to close this.
I'd think you should add rspec to the Gemfile ... not sure why it works without ... but I guess changing to rspec-core is fine too ...
Sorry, actually I can't run bundle exec
together with a user install of instafail. I am assuming that bundle doesn't cover this. I could add the gem to the project's Gemspec, but not everybody is using it and it feels like polluting the team deps.
Given that I skip bundle exec
, if I do a puts Gem.loaded_specs
I only receive a hash with rspec-support
, rspec-core
and rspec-instafail
, although I also have rspec-3.4.0 installed alongside instafail.
so I guess it works because you are not using bundler ... funky ...
0.5.0 ... this might bite a few people stuck on rspec1 ... but let's see :D
Thanks, works like a charm
When upgrading rspec from 3.1.0 to 3.4.0 I receive the following stacktrace running rspec:
The proposed change fixes that issue for me.