Ruby on Rails Wednesday, September 29, 2010

Heinz Strunk wrote:
> I normally used autotest to when writing test which worked just fine
> until I switched to Rails 3. Now, when I run autotest it tests all tests
> and gets stuck somewhere:
> Loaded suite -e
> Started
> ...EE..EEE.....................E.................................E.EE..EE..................................E.EE..EE.....................FEE....E
>
> Even after an hour or so it doesn't continue.
>
> I'm using these versions:
> autotest (4.4.0)
> autotest-growl (0.2.6)
> autotest-rails (4.1.0)
> ZenTest (4.4.0)

I don't know for sure what's happening to you, but I've been using
autotest just fine with Rails 3 (so far).

However, I your list of gems are somewhat in conflict. ZenTest includes
autotest, but you're showing both gems above. If you only need the
autotest part of ZenTest then don't install ZenTest. Also, if you
install autotest-rails then that will install ZenTest (as a dependency)
so don't install autotest-rails either.

Here's the list of autotest gems I've been using successfully with Rails
3 and RSpec on Mac OS X 10.6:
autotest
autotest-fsevent
autotest-growl

If you're on a Mac I highly recommend autotest-fsevent as it's much less
burdensome on the system because it eliminates the file system polling.
Instead it uses the Finder notification system to detect changes.
--
Posted via http://www.ruby-forum.com/.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

No comments:

Post a Comment