On 30 Aug 2011, at 14:45, Nikolay Sturm wrote:
> * Ash Moran [2011-08-30]:
>> I never thought of that! Yes, that could also work, probably better in
>> fact. It just involves running multiple Guard processes, although
>> there's Terminitor[1] for that!
>
> A single guard process is enough, it wi
On 30 Aug 2011, at 14:45, Nikolay Sturm wrote:
> * Ash Moran [2011-08-30]:
>> I never thought of that! Yes, that could also work, probably better in
>> fact. It just involves running multiple Guard processes, although
>> there's Terminitor[1] for that!
>
> A single guard process is enough, it wil
On 30 Aug 2011, at 14:45, Nikolay Sturm wrote:
> A single guard process is enough, it will start all guards defined in
> your Guardfile.
I did not know that! I'm still new to Guard, a recent convert from Autotest.
Thanks for the tip.
Cheers
Ash
--
http://www.patchspace.co.uk/
http://www.link
* Ash Moran [2011-08-30]:
> I never thought of that! Yes, that could also work, probably better in
> fact. It just involves running multiple Guard processes, although
> there's Terminitor[1] for that!
A single guard process is enough, it will start all guards defined in
your Guardfile.
cheers,
N
On 30 Aug 2011, at 07:01, Nikolay Sturm wrote:
> I have a similar situation with the slow specs being integration specs
> in a special directory. I tagged all those example groups and setup two
> guards. The first is for unit tests and ignores all examples tagged
> 'integration' and doesn't watch
* Ash Moran [2011-08-30]:
> I'm trying to optimise my spec run time. I have 123 examples so far,
> which run in ~4.2 seconds on average. But 116 of those will run in
> ~0.18 seconds. So, obviously, I only want to run the slow ones when I
> change that code.
I have a similar situation with the slow
