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.
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?
On Sep 3, 7:04 pm, David C. [email protected] 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.
On Sep 3, 2010, at 6:07 PM, ericindc wrote:
On Sep 3, 7:04 pm, David C. [email protected] 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?
On Sep 3, 7:09 pm, David C. [email protected] wrote:
On Sep 3, 2010, at 6:07 PM, ericindc wrote:
On Sep 3, 7:04 pm, David C. [email protected] 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)
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)
On Sep 3, 9:37 pm, David C. [email protected] wrote:
failures are from the model spec that is not being included when run
autotest-fsevent (0.2.3)
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?
On Sep 3, 2010, at 8:12 PM, ericindc wrote:
failures are from the model spec that is not being included when run
autotest-fsevent (0.2.3)
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.
On Sep 3, 8:34 pm, David C. [email protected] wrote:
Are you sure that the model spec is excluded from autotest rather than it’s just passing?
and RVM 1.8.7-p302 and the the following:
rspec-users mailing list
[email protected]://rubyforge.org/mailman/listinfo/rspec-usersI 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.
On Sep 3, 2010, at 10:56 PM, ericindc wrote:
included. Not sure if there are others.
rspec-mocks (2.0.0.beta.20)
does not exist. Naming it back to it’s original causes it to miss
etc. so that I only have:/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:
Try setting up your gemfile per Living on edge on
GitHub - rspec/rspec-rails: RSpec for Rails 5+. Don’t know if it’ll help, but it’s
probably worth trying.
On Sep 3, 2010, at 6:42 PM, ericindc wrote:
Also - versions? rspec, rails, ruby, os?
rspec (2.0.0.beta.20)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.
On Sep 4, 10:42 am, David C. [email protected] wrote:
included. Not sure if there are others.
rspec-mocks (2.0.0.beta.20)
does not exist. Naming it back to it’s original causes it to miss
etc. so that I only have:
/Users/Eric/.rvm/rubies/ruby-1.8.7-p302/bin/ruby -rrubygemsIs something misconfigured on my end?
Nope - wasn’t handling bundler. Is now:Run autotest with 'bundle exec' if there is a Gemfile present. · rspec/rspec-core@976b935 · GitHub…
Try setting up your gemfile per Living on edge onhttp://github.com/rspec/rspec-rails. Don’t know if it’ll help, but it’s probably worth trying.
No luck. Even with living on the edge, it’s still not running under
bundler (could it be something with RVM) and I get 144 tests with
autotest and 151 with rake spec.