817a23b10d
When running `go test` without the `-v` flag, the output may not contain everything that we expect. For example, no output is generated for passing tests. Even for a failing test the output does not contain a `=== RUN` line. Currently, this resulted in us ignoring the test result since we couldn't find an existing test to assign this result to. We should however handle this situation gracefully, and just assume a test exists when only encountering a test result line. References #109
go-junit-report
go-junit-report is a tool that converts go test output to an XML report,
suitable for applications that expect JUnit-style XML reports (e.g. Jenkins).
The test output parser and JUnit report formatter are also available as Go packages.
Install from package (recommended)
Pre-built packages for Windows, macOS and Linux are found on the Releases page.
Install from source
Download and install the latest stable version from source by running:
go install github.com/jstemmer/go-junit-report@latest
Usage
go-junit-report reads the full go test output from stdin and writes JUnit
compatible XML to stdout. In order to capture build errors as well as test
output, redirect both stdout and stderr to go-junit-report.
go test -v 2>&1 | go-junit-report > report.xml
Parsing benchmark output is also supported, for example:
go test -v -bench . -count 5 2>&1 | go-junit-report > report.xml
If you want go-junit-report to exit with a non-zero exit code when it encounters
build errors or test failures, set the -set-exit-code flag.
Run go-junit-report -help for a list of all supported flags.
Contributing
See CONTRIBUTING.md.