On Sat, Feb 21, 2009 at 12:33 AM, Ben Mabey wrote:
> Stephen Eley wrote:
>>
>> On Fri, Feb 20, 2009 at 2:33 PM, Peter Jaros
>> wrote:
>>
>>>
>>> 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.
>>>
>>
>> Which is almo
Stephen Eley wrote:
On Fri, Feb 20, 2009 at 2:33 PM, Peter Jaros wrote:
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.
Which is almost exactly what I was about to suggest. >8-> Only you
don't have to overr
On Fri, Feb 20, 2009 at 2:33 PM, Peter Jaros wrote:
>
> 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.
Which is almost exactly what I was about to suggest. >8-> Only you
don't have to override #run, you can just fak
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 wa
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
proje
