[rspec-users] Autotest quits when code has errors

[Anthony Broad-Crawford]

Try rspactor.  I have been using since the author pinged this list  
several months ago.  No complaints thus far.  To your point, it  
doesn't bomb when there is an error.

Anthony Broad-Crawford

On Jul 28, 2008, at 7:19 PM, Mark Wilden wrote:

> On Mon, Jul 28, 2008 at 3:10 PM, Evan Dorn <lists at ruby-forum.com>  
> wrote:
> Sorry, I'd put this in a ZenTest forum (as opposed to RSpec), except
> that I can't find one.
>
> I find it frustrating that autotest keeps running when it finds  
> failing
> tests - but it quits back to the command line whenever a test or code
> contains *errors*.
>
> This means I have to constantly (like every 5 minutes) restart  
> autotest
> by hand, which kind of defeats the purpose of autotest, and I find it
> hard to believe this is the default behavior.
>
> If I want to do TDD/BDD and call methods before they exist, this  
> causes
> autotest to quit, which REALLY defeats the purpose.
>
> Am I doing something wrong, or is there a fix?   I'm using ZenTest  
> 3.10
> with RSpec 1.1.5.
>
> It sounds like it might be an RSpec 1.1.5 thing. I've used 1.1.4  
> with autotest without seeing the problem you describe.
>
> ///ark
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20080728/21b0fe68/attachment-0001.html>