Package : perl-TAP-Formatter-JUnit > RPM : perl-TAP-Formatter-JUnit-0.160.0-1.mga9.noarch.rpm
Basic items
InstallName | perl-TAP-Formatter-JUnit |
Version | 0.160.0 |
Release | 1.mga9 |
URL | https://metacpan.org/release/TAP-Formatter-JUnit |
Group | Development/Perl |
Summary | TAP formatter, turning TAP into JUnit |
Size | 66KB |
Arch | noarch |
License | GPL+ or Artistic |
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 c<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
parsable formats).
'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
*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
parsable formats).
Media information
Distribution release | Mageia cauldron |
Media name | core-release |
Media arch | i586 |
Advanced items
Source RPM | perl-TAP-Formatter-JUnit-0.160.0-1.mga9.src.rpm |
Build time | 2022-05-18 16:19:22 |
Changelog | View in Sophie |
Files | View in Sophie |
Dependencies | View in Sophie |