[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl-qa
Subject:    Re: Reuse TAP from "prove -v" for later use
From:       Steffen Schwigon <ss5 () renormalist ! net>
Date:       2008-06-11 20:48:40
Message-ID: 87r6b3vgt3.fsf () shirts ! quite-simply ! de
[Download RAW message or body]

Michael Peters <mpeters@plusthree.com> writes:
> Steffen Schwigon wrote:
>
>> I'm not sure what's the best way to dual-use "prove/Build test/make
>> test" on one hand and sending the raw TAP at the same time to the
>> receiver.
>
> That's what TAP::Harness::Archive was meant to address. If you run prove with
> the -a flag it will create an archive of the test run (basically a tarball of
> the resulting TAP streams and some meta data about the run).
>
>> "prove -v" seems to slighty change my TAP, eg., adds extra single
>> intermediate summary "ok" lines, lowercases "SKIP", etc.; at least it
>> is still basically the same TAP.
>> 
>> - Is using and later re-parsing the slightly changed "prove -v" output
>>   a legitimate way at all, eg., by stripping away the added lines?
>
> No, use -a :)
>
>> - Would I write an own TAP::Formatter that preserves the raw TAP?
>>
>> - If so, how can I use an own formatter from "./Build test"?
>
> I'm not sure there is an easy way to have Module::Build use
> TAP::Harness::Archive, but prove can.

Ah, I kind of misinterpreted the -a option in the manual in a way that
"store the resulting TAP" would mean the slightly different TAP that I
described above, not the original TAP from my tests.

The -a option perfectly fits to my needs.

Thanks.

Kind regards,
Steffen
-- 
Steffen Schwigon <ss5@renormalist.net>
Dresden Perl Mongers <http://dresden-pm.org/>
Deutscher Perl-Workshop <http://www.perl-workshop.de/>
[prev in list] [next in list] [prev in thread] [next in thread]