[tap-l] Parallel testing

[H.Merijn Brand]

In Oslo Andy and I came up with a way to define how Test::Harness should
deal with parallel tests, like this:

--8<--- psmoke.conf
# never run files in this group side by side, order doesn't matter
conflict:
    folder:	../ext/DB_File/t
    folder:	../ext/IO_Compress_Zlib/t
    folder:	../lib/CPANPLUS
    folder:	../lib/ExtUtils/t
#   folder:	../lib/Pod/t

# first file should be run before file 2, 3, 4, ...
depends:
    depend:	[ foo.t bar.t ]
-->8---

As Test::Harness `does' TAP, maybe "psmoke.conf" should better be
renamed to ".taprc", which brought me to the question

if that config file would be called .taprc (or tap.rc on windows/vms) and
it would be stackable (~/.taprc, /etc/tap.rc ...) would that be usefull?

and then it should be included in the yaml metadata we disdussed?

I bet the TAP parsers should know about the tests being run in parallel
and what the restrictions were. It maybe also should know what
$HARNESS_OPTIONS was set when the run ran.

-- 
H.Merijn Brand         Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using & porting perl 5.6.2, 5.8.x, 5.10.x  on HP-UX 10.20, 11.00, 11.11,
& 11.23, SuSE 10.1 & 10.2, AIX 5.2, and Cygwin.       http://qa.perl.org
http://mirrors.develooper.com/hpux/            http://www.test-smoke.org
                        http://www.goldmark.org/jeff/stupid-disclaimers/