On Sep 3, 2010, at 10:56 PM, ericindc wrote: > > > On Sep 3, 9:37 pm, David Chelimsky <dchelim...@gmail.com> wrote: >> On Sep 3, 2010, at 8:12 PM, ericindc wrote: >> >> >> >> >> >> >> >>> On Sep 3, 8:34 pm, David Chelimsky <dchelim...@gmail.com> wrote: >>>> On Sep 3, 2010, at 6:42 PM, ericindc wrote: >> >>>>> On Sep 3, 7:33 pm, ericindc <ericmilf...@gmail.com> wrote: >>>>>> On Sep 3, 7:09 pm, David Chelimsky <dchelim...@gmail.com> wrote: >> >>>>>>> On Sep 3, 2010, at 6:07 PM, ericindc wrote: >> >>>>>>>> On Sep 3, 7:04 pm, David Chelimsky <dchelim...@gmail.com> wrote: >>>>>>>>> On Sep 3, 2010, at 6:02 PM, ericindc wrote: >> >>>>>>>>>> Any idea why autotest would miss some of my tests? I run autotest >>>>>>>>>> and >>>>>>>>>> everything passes, but rake spec results in 2 failures. The 2 >>>>>>>>>> failures are from the model spec that is not being included when run >>>>>>>>>> in autotest. >> >>>>>>>>> Are you sure that the model spec is excluded from autotest rather >>>>>>>>> than it's just passing? >> >>>>>>>>> Also - versions? rspec, rails, ruby, os? >> >>>>>>>> I also verified in the autotest output that the model spec is not >>>>>>>> included. Not sure if there are others. >> >>>>>>> Versions? >> >>>>>> I purposefully broke the test and everything passes. Running rake >>>>>> spec, however, caught the error. I am running a Rails 3 app on OS X >>>>>> and RVM 1.8.7-p302 and the the following: >> >>>>>> rspec (2.0.0.beta.20) >>>>>> rspec-core (2.0.0.beta.20) >>>>>> rspec-expectations (2.0.0.beta.20) >>>>>> rspec-mocks (2.0.0.beta.20) >>>>>> rspec-rails (2.0.0.beta.20) >>>>>> autotest (4.3.2) >>>>>> autotest-fsevent (0.2.3) >>>>>> autotest-growl (0.2.5) >>>>>> autotest-rails (4.1.0)> _______________________________________________ >>>>>>> rspec-users mailing list >>>>>>> rspec-us...@rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users >> >>>>> I also just noticed that renaming the file to something random causes >>>>> autotest to pick it up. It blows up because the corresponding model >>>>> does not exist. Naming it back to it's original causes it to miss >>>>> again. >> >>>> Are the names perfectly aligned with the specs? i.e. app/models/thing.rb >>>> and spec/models/thing_spec.rb? By default, autotest requires this mapping, >>>> though it can be customized if you have a need. >> >>> Yes, and I don't see any mention of the model in the "No tests >>> match...." output from autotest. >> >> Just noticed your post a few back with the versions - try removing >> autotest-rails from your Gemfile and make sure you're running autotest with >> bundle exec. > > Hrm...I'm not sure what's going on. I already removed autotest-rails, > etc. so that I only have: > > $ gem list | grep -i test > autotest (4.3.2) > autotest-growl (0.2.5) > rack-test (0.5.4) > ZenTest (4.4.0) > > > I did notice that it does not appear to be running through bundle > exec: > > /Users/Eric/.rvm/rubies/ruby-1.8.7-p302/bin/ruby -rrubygems > > Is something misconfigured on my end?
Nope - wasn't handling bundler. Is now: http://github.com/rspec/rspec-core/commit/976b935bde657aebf6f5f7dbb26d6d4e29cc1ac1 Try setting up your gemfile per Living on edge on http://github.com/rspec/rspec-rails. Don't know if it'll help, but it's probably worth trying. _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
