| Name : perl-TAP-Formatter-JUnit
| |
| Version : 0.16
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : 1.18
| Date : 2024-02-14 20:10:47
|
| Group : Unspecified
| Source RPM : perl-TAP-Formatter-JUnit-0.16-1.18.src.rpm
|
| Size : 0.06 MB
| |
| Packager : (none)
| |
| Summary : Harness output delegate for JUnit output
|
Description :
*This code is currently in alpha state and is subject to change.*
\'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 \'PERL_TEST_HARNESS_DUMP_TAP\' to a
directory that you would like the JUnit XML dumped to. Note, that this will
*also* cause \'TAP::Harness\' to dump the original TAP output into that
directory as well (but IMHO that\'s ok as you\'ve now got the data in two
parseable formats).
Timing information is included in the JUnit XML, _if_ you specified
\'--timer\' when you ran _prove_.
In standard use, a \"passing TODO\" is treated as failure conditions (and is
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/). That\'s the build tool I\'m using at the
moment and needed to be able to generate JUnit output for.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl:/CPAN-T/openSUSE_Tumbleweed/noarch |
