[rspec-users] autotest with a non-rspec project
dchelimsky at gmail.com
Wed Oct 15 23:34:28 EDT 2008
On Wed, Oct 15, 2008 at 8:24 PM, Jon Dahl <lists at ruby-forum.com> wrote:
> I'm getting the same error - I'm using Test::Unit with Shoulda for this
> particular project, and can't autotest because it is trying to load
> David Chelimsky wrote:
>> The only reason that I know of that this would be happening would be
>> that there are both a spec directory in your app and the rspec gem
>> somewhere on your path.
> I don't have a spec directory in the app, except perhaps in a plugin;
> and I tried uninstalling the RSpec gem. But it is still trying to load
> autotest/rails_rspec, and failing.
>> We've introduced an autospec command since the last release just to
>> avoid this conflict. So one thing you might try doing is cloning the
>> git repo, building and installing the gem from source (see
> Are you talking about autospec as a replacement for autotest (which
> wouldn't seem to help the Test::Unit autotest problem), or a rewrite of
> autotest/Zentest that includes separate commands for autospec
> (RSpec-only) and autotest (Test::Unit only)?
I introduced autospec in 1.1.5 in response to this ticket:
Basically, we set it up so when you run autotest, rspec won't announce
itself to autotest's discovery system unless an env variable is set.
autospec sets this variable and then calls autotest. That's it.
So, unless there's a bug that I'm not seeing, the only way this could
be happening is if you have either an rspec gem older than 1.1.5 or
you have an older version of the rspec plugin.
> Posted via http://www.ruby-forum.com/.
> rspec-users mailing list
> rspec-users at rubyforge.org
More information about the rspec-users