On 21 Jan 2007, at 13:23, David Golden wrote:
This is a false assumption. You've got to consider that the
"canonical" way to run tests for a distribution is still "make test"
and thus Test::Harness is getting called from a command-line embedded
in a Makefile. The program calling "make test" (e.g. CPAN.pm) has no
way of getting structured data back from the function call -- it has
to have some sort of IPC. Thus my suggestion for dumping structured
output to text files.
OK, point taken. Adam's suggestion is that if an env variable, say,
TEST_HARNESS_DUMP is defined the harness will copy all TAP to the
file it names.
It'd be possible to turn that into structured results by feeding that
back into TAPx::Parser. So you'd do
export TEST_HARNESS_DUMP=/home/me/testdump
make test
<some code that uses TAPx::Parser to parse the dumped test results
into Perl objects>
Is that workable?
--
Andy Armstrong, hexten.net
