Write one Test::SMTP test for every type of SMTP transaction you want to
simulate. Then try to wrap your tests with
http://search.cpan.org/~dlux/Parallel-ForkManager-0.7.5/ForkManager.pm.
You will know if the individual tests went OK via their exit code.
I was about to take this approach for testing load on our servers, and
releasing it as a module. Test::Parallel (or something like that). That
module would act capturing all it's childs test outputs, summing the
number of tests, and returning valid TAP output. I don't have a schedule
for it, though, so, maybe you can have a go at it.
Even better... someone else had a go at it!!!
Test::Harness "prove" command lets you fork off the children tests you
like in parallel... just create a .t file, and a bunch of symlinks to
it... Then prove -jNUM_CHILDREN -f testdir/
Jose Luis Martinez
[EMAIL PROTECTED]
