On 10 Jun 2008, at 17:48, 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.
"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?
TAP::Parser accepts a 'spool' option which should be a filehandle to
which raw TAP can be spooled. Does that help?
--
Andy Armstrong, Hexten
