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

[Peter Leonard]

I also want to follow up on this because I'm dealing with an additional 
problem:

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.

Anyone?


Peter Leonard wrote:
> Michael,
>
> To be clear - the code sample I posted doesn't work by design?  I'm 
> confused on this point because the POD in TAP::Harness and associated 
> modules leads me to believe that what I'm trying to do should simply 
> work.
>
> Thanks,
>
> Peter
>
>
> Michael Peters wrote:
>> Peter Leonard wrote:
>>
>>   
>>> I *have* gotten this to work by enabling 
>>> $ENV{PERL_TEST_HARNESS_DUMP_TAP}, and then manually loading the files 
>>> into new TAP::Parser objects, but it's really roundabout, clunky, and a 
>>> PITA.
>>>     
>>
>> You could use TAP::Harness::Archive that will do basically the same thing, but 
>> in a nicer interface. It will create a .tar.gz file that you can then point it 
>> at and get a TAP::Parser::Aggregator which will have different parsers you can 
>> use to analyze the TAP line by line.
>>
>>   
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> tapx-dev mailing list
> tapx-dev at hexten.net
> http://www.hexten.net/mailman/listinfo/tapx-dev
> cpan: http://search.cpan.org/dist/TAP-Parser/
> bugs: http://rt.cpan.org/Public/Dist/Display.html?Name=TAP-Parser
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.hexten.net/pipermail/tapx-dev/attachments/20090407/c7021640/attachment.htm