Hi!

*Intro:*

I use TAP to collect reports of several kinds, not only Perl
libraries.

Normally I send the raw TAP from running a test suite to a test
receiver. That receiver collects the raw TAP into a database. I
evaluate the TAP later with TAP::Parser. (The receiver is basically
just a host+port to which apps can "netcat" their results. Meta info
is transported in diagnostics/comment lines.)

Now I want to use that same not-perl environment to collect the TAP of
my Perl libs, similar to what happens when CPAN.pm uses
CPAN::Reporter.


*The question:*

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.

"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?

- Would I write an own TAP::Formatter that preserves the raw TAP?

- If so, how can I use an own formatter from "./Build test"?

- Or would I write/subclass a complete own harness for my purposes?


Suggestions? Comments? Hints?

Thanks.

Kind regards,
Steffen
-- 
Steffen Schwigon <[EMAIL PROTECTED]>
Dresden Perl Mongers <http://dresden-pm.org/>
Deutscher Perl-Workshop <http://www.perl-workshop.de/>

Reply via email to