I have not used RSpec since December, when our app was still Rails 3. Since, we've upgraded to Rails 4 and updated the necessary gems. I have not changed anything in the Guardfile, .rspec, or spec/spec_helper.rb files yet.
When I run bundle exec guard like I used to, I receive no error (except for Rails-specific deprecation warnings). When I switch to another tab in my terminal, I run bundle exec rspec spec/features/admin/login_spec.rb. As noted in the title, I receive the following error/backtrace:
If I need to add gists of additional files, let me know. I think this issue relates to the fact we upgraded to Rails 4. I am not sure where (maybe Spork), but a README listed that it covered <= 4.0.0, not Rails 4.2.0
Do let me know, if necessary, the correct Github repo I should post this issue in.
GEM VERSIONS Rails 4.2.0 ruby 1.9.3p547 (2014-05-14) [x86_64-linux] rspec-core (3.1.7) guard (2.11.1) guard-compat (1.2.0) guard-spork (2.1.0) spork (1.0.0rc4) spork-rails (4.0.0) spork-testunit (0.0.8)
I have not used RSpec since December, when our app was still Rails 3. Since, we've upgraded to Rails 4 and updated the necessary gems. I have not changed anything in the
Guardfile
,.rspec
, orspec/spec_helper.rb
files yet.When I run
bundle exec guard
like I used to, I receive no error (except for Rails-specific deprecation warnings). When I switch to another tab in my terminal, I runbundle exec rspec spec/features/admin/login_spec.rb
. As noted in the title, I receive the following error/backtrace:If I need to add gists of additional files, let me know. I think this issue relates to the fact we upgraded to Rails 4. I am not sure where (maybe Spork), but a README listed that it covered <= 4.0.0, not Rails 4.2.0