Re: How might we mark a test suite isn't parallalizable?

On a side note, this is one of the reasons I want to add tags to Test::Class::Moose (http://blogs.perl.org/users/ovid/2013/04/adding-tags-to-testclassmoose.html). With that, marking a test as "parallelizable" becomes a trivial problem. This is, in part, because Test::Class::Moose is evolving into a testing platform for those who need more reporting and fine-grained control over their test suite, something which I think has currently been lacking in the Perl toolchain.

Currently, marking things as "parallelizable" could already be done using the include and exclude features, but that's based on the method names and isn't really scalable.
 
Cheers,
Ovid
--
Twitter - http://twitter.com/OvidPerl/
Buy my book - http://bit.ly/beginning_perl
Buy my other book - http://www.oreilly.com/catalog/perlhks/
Live and work overseas - http://www.overseas-exile.com/


>________________________________
> From: brian d foy <[email protected]>
>To: [email protected] 
>Sent: Thursday, 2 May 2013, 21:39
>Subject: How might we mark a test suite isn't parallalizable?
> 
>
>In HARNESS_OPTIONS we can set -jN to note we want parallel tests
>running, but how can a particular module, which might be buried in the
>dependency chain, tell the harness it can't do that?
>
>It seems to me that by the time the tests are running, it's too late
>because they are already in parallel and the best we can do is issue a
>warning or decide to fail.
>
>
>