I don't know about RSpactor, but autospec will keep track of failing specs and re-run them along with changed specs and specs for changed files. It won't run the entire suite until everything has passed. You could temporarily add a dummy example somewhere in your suite which always fails. That way autospec will never think it's ready to run the whole suite.
Other than that, I can't think of a way to do it short of writing your own autospec style and overriding the #run algorithm. Peeja On Fri, Feb 20, 2009 at 1:34 PM, Ben Mabey <[email protected]> wrote: > Hello all, > Is there a way to have autospec and/or RSpactor just run the specs for the > files that have changed and not run the entire spec suite afterwards? If > you start autospec with -f it will wait for a change but it will then run > the entire suite after the individual one passes. The project that I am > working on now has a spec suite that is too long for the normal autospec > cycle. However, I like having that tight feedback loop for the files I > touch. Any ideas? > > Thanks, > Ben > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
