Forum: RSpec rspec2: autotest keeps rerunning failing tests

Since my update to beta.20 i have this weird thing.
Normally i develop with autotest on, and when i get an error: i can
check the errors, and they are rerun when i save the files.

If all my tests pass this is still the current behaviour, but if i
have failing tests, autotest will keep running those tests.
I am afraid i find that kind of annoying :)

I am not sure what could cause this.

In my autotest/discover.rb i have the following lines:

Autotest.add_discovery { "rails" }
Autotest.add_discovery { "rspec2" }


Is there a way to get the old behaviour back? (tests are only rerun
when files have changed)

I can't explain why it suddenly did not work anymore, but i read
http://gist.github.com/365816
and the only thing i needed to do to make it work was adding the
following dependencies to my gemfile:

gem "autotest"
gem "autotest-rails"

The gem autotest-rails was already installed on my system. So can't
explain why, but now it works.
There, i fixed it :)

hmmmm.... adding autotest-rails did not fix it for me.

On Aug 30, 2010, at 9:56 AM, Justin Ko wrote:

>> There, i fixed it :)
>>> have failing tests, autotest will keep running those tests.
>>> when files have changed)
> hmmmm.... adding autotest-rails did not fix it for me.

Justin - are you experiencing the same problem?

Please take a look at the Autotest section in the README on 
http://github.com/rspec/rspec-rails. That explains what's been working 
for me. Let me know whether or not it works for you as well.

Cheers,
David

Following the instructions in the README, I still have this problem.
Downgrading to RSpec beta 19 fixes it.

On Aug 30, 11:08 am, David Chelimsky <dchelim...@gmail.com> wrote:
>
> >>> Normally i develop with autotest on, and when i get an error: i can
> >>> Autotest.add_discovery { "rails" }
> Cheers,
> David
> _______________________________________________
> rspec-users mailing list
> rspec-us...@rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

Woops, sorry about not posting at the bottom.

Hi,

I tried many variations of gems in Gemfile, modifying options in
autotest/discover.rb, running with and without bundle exec but in the
end only backing off to 2.0.0.beta.19 stopped failing tests being
immediately re-run.

Allan

Same here!

Allan

I spoke too soon. Adding "autotest-rails" did not solve my problems
either.
Trying "bundle exec autotest" also did not help.

I have been trying to use watchr, which seems faster, but when i save
multiple files at once, only one file is tested again.
But maybe i have to write a better wachtr script for that :)

I will try to investigate the autotest-problem further if i can make
some time today.

On Sep 1, 2010, at 4:13 AM, nathanvda wrote:

> I spoke too soon. Adding "autotest-rails" did not solve my problems
> either.
> Trying "bundle exec autotest" also did not help.
> 
> I have been trying to use watchr, which seems faster, but when i save
> multiple files at once, only one file is tested again.
> But maybe i have to write a better wachtr script for that :)
> 
> I will try to investigate the autotest-problem further if i can make
> some time today.

Looks like someone else discovered, reported, and is in the process of 
trying to fix this: 
http://github.com/rspec/rspec-rails/issues/#issue/191