<B>This code is currently in alpha state and is subject to change.B>
TAP::Formatter::JUnit provides JUnit output formatting for TAP::Harness.
By default (e.g. when run with prove), the entire test suite is gathered
together into a single JUnit XML document, which is then displayed on STDOUT.
You can, however, have individual JUnit XML files dumped for each individual
test, by setting c<PERL_TEST_HARNESS_DUMP_TAP> to a directory that you would
like the JUnit XML dumped to. Note, that this will <B>alsoB> cause
TAP::Harness to dump the original TAP output into that directory as well (but
IMHO thats ok as youve now got the data in two parsable formats).
Timing information is included in the JUnit XML, if you specified --timer
when you ran prove.
In standard use, passing TODOs are treated as failure conditions (and are
reported as such in the generated JUnit). If you wish to treat these as a
pass and not a fail condition, setting ALLOW_PASSING_TODOS in your
environment will turn these into pass conditions.
The JUnit output generated is partial to being grokked by Hudson
(<http://hudson.dev.java.net/>). Thats the build tool Im using at the
moment and needed to be able to generate JUnit output for.
Graham TerMarsch <email@example.com>
Many thanks to Andy Armstrong et al. for the <B>fabulousB> set of tests in
Test::Harness; they became the basis for the unit tests here.
Other thanks go out to those that have provided feedback, comments, or patches: