On 12 Nov 2007, at 17:43, Eric Wilhelm wrote:
[snip]
Perhaps a solution which involves a pre-fork model of
Test::Class would be a little neater. The "test scripts"
would then be sub-sub-processes and the harness just needs
filehandles from each of those.
[snip]
Yeah - that would be neat and help with runtimes. One of the reasons
I'm keeping an eye on things like TAP::Harness::Parallel :-)
When the free time fairy next visits what I'd like to do is have T::C
use some of the newer features and push information on the class/
name/
tags of the running method out into TAP.
Well, whatever tagging and formatting is fine and dandy.
I was suggesting that rethinking the run layer would solve more
issues,
and it inherently 'tags' the output as coming from different
processes.
Yup. Although the _real_ reason I want tagging is do do things like
"run all the database test" or "run all the tests that aren't slow".
Cheers,
Adrian
