Steffen Schwigon wrote: > *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.
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. For my larger projects that I care about I write a custom test harness that uses the new Test::Harness 3 tools. > - Or would I write/subclass a complete own harness for my purposes? For my larger projects that I care about I write a custom test harness that uses the new Test::Harness 3 tools. -- Michael Peters Plus Three, LP
