Having problems with TAP::Harness / TAP::Parser output

[Michael Peters]

Peter Leonard wrote:

> Sometimes test scripts fail due to missing dependencies (e.g. developers 
> forget to check in dependent CPAN modules).  When test scripts blow up 
> due to this, an empty TAP file is left behind - which means I have no 
> output to parse to give appropriate feedback as to what actually 
> failed.  Furthermore, when the responsible developer re-tests their 
> code, it works on their end, as the un-checked-in module is happily 
> present in their environment.

TAP::Harness::Archive only stores the TAP that it gets back from the processes 
that are run. If the process never runs there is no TAP. How are you running 
your tests? Are you using the merge option of TAP::Harness? It will merge stderr 
and stdout together, but I'm not sure what TAP::Harness does with subprocesses 
that die prematurely like that.

-- 
Michael Peters
Plus Three, LP