This is an application/library heavily inspired by dart-junitreport and dart-testreport. It takes what was done in those two packages and brings them under a single umbrella, updates to null-safety, and makes various code style improvements.
The purpose of this package is three-fold:
- Firstly, it provides models by which output from the test json reporter can be decoded.
- Secondly, it provides a processor that will take a full json report from the test json reporter and generate a more developer-friendly report model structure that is agnostic to the protocol version of the test json reporter.
- Thirdly, it is a command-line application(
report_to_junit) that can be used to take in a full json report from the test json reporter and generate a junit XML report(usable by many CI tools)
This package is still experimental as we continue to build out more functionality. It's current state is barebones as we investigate ways to make the junit output more useful and ways to produce better testing reports for use outside of just junit.
In order to start using the
report_to_junit command, install the latest
better_test_reporter as a global package via pub.dev.
pub global activate better_test_reporter
Details on all options for
report_to_junit can be found by running
> report_to_junit --help
-i, --input the path to the 'json' file containing the output of 'pub run test'.
if missing, <stdin> will be used
-o, --output the path of the to be generated junit xml file.
if missing, <stdout> will be used
-b, --base the part to strip from the 'path' elements in the source
(defaults to the current working directory)
-p, --package the part to prepend to the 'path' elements in the source
(defaults to "")
-t, --timestamp the timestamp to be used in the report
- 'now' will use the current date/time
- 'none' will suppress timestamps altogether
- a date formatted 'yyyy-MM-ddThh:mm:ss' will be used as UTC date/time
- if no value is provided
- if '--input' is specified the file modification date/time is used
- otherwise the current date/time is used
-h, --help display this help text
Differences from original implementation in
- When generating the XML for a problem during a test,
dart-junitreporthad a special case for only one problem occurred. The multiple problem case also handled the case for a single problem. We found the special case for a single problem unneeded and a little buggy, so it was removed in
- When parsing the test reporter json into a report,
dart-testreportset tests as not hidden if they encountered any problems while running. In
better_test_reporter, the hidden attribute on a test will be purely based on whether the test was explicitly hidden based on the
TestDoneEventjson. That said, we maintained the hidden behavior for the output junit xml by shifting that decision out of the report and up to whatever consumes the report.
- When generating the XML for a test case,
better_test_reporterdefaults to stripping the current working directory out of the classname.