On Sat, Sep 29, 2001 at 01:25:20PM -0500, Dave Rolsky wrote:
> > Thinking about it, you could probably move the module loads into the
> > test scripts and have them just run the basic test, which would, in
> > turn, probably mean you could get away with just using Test::More/Simple
>
> But I like Test::More! Its just the numbering issue that's the problem.
Have you tried the Test::Builder thing yet? I think you should be
able to solve your forking problem like so:
use Test::More tests => 10; # or whatever.
ok(1, 'normal test');
ok(1, 'another normal test');
$builder = Test::Builder->new; # get the underlying T::B object for
# fine control.
$builder->use_numbers(0);
...fork into three tests (I forget how to that, so *handwave*)...
ok(1, "forked test 1 (PID $$)");
ok(1, "forked test 2 (PID $$)");
...forked code done...
$builder->use_numbers(1);
ok(1, 'last two');
ok(1, 'normal tests');
So the output should look something like:
1..10
ok 1 - normal test
ok 2 - another normal test
ok - forked test 1 (PID 3245)
ok - forked test 2 (PID 3245)
ok - forked test 1 (PID 3246)
ok - forked test 2 (PID 3246)
ok - forked test 1 (PID 3247)
ok - forked test 2 (PID 3247)
ok 9 - last two
ok 10 - normal tests
--
Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
List context isn't dangerous. Misquoting Gibson is dangerous.
-- Ziggy
