go-junit-report is a tool that converts go test output to a JUnit compatible XML report, suitable for use with applications such as Jenkins.

The test output parser and JUnit XML report generator are also available as Go packages. This can be helpful if you want to create your own custom JUnit reports for example. See the package documentation on pkg.go.dev for more information:

• go-junit-report/v2/pkg/parser/gotest
• go-junit-report/v2/pkg/junit

Pre-built packages for Windows, macOS and Linux are found on the Releases page.

Download and install the latest stable version from source by running:

go install github.com/jstemmer/go-junit-report@latest

By default, go-junit-report reads go test -v output generated by the standard library testing package from stdin and writes a JUnit XML report to stdout.

Go build and runtime errors are also supported, but this requires that stderr is redirected to go-junit-report as well.

Typical use looks like this:

go test -v 2>&1 ./... | go-junit-report -set-exit-code > report.xml

JSON produced by go test -json is supported by the gojson parser. Note that stderr still needs to be redirected to go-junit-report in order for build errors to be detected. For example:

go test -json 2>&1 | go-junit-report -parser gojson > report.xml

Go benchmark output is also supported. The following example runs benchmarks for the package in the current directory and uses the -out flag to write the output to a file called report.xml.

go test -v -bench . -count 5 2>&1 | go-junit-report -out report.xml

The -iocopy flag copies stdin directly to stdout, which is helpful if you want to see what was sent to go-junit-report. The following example reads test input from a file called tests.txt, copies the input to stdout and writes the output to a file called report.xml.

go-junit-report -in tests.txt -iocopy -out report.xml

Run go-junit-report -help for a list of all supported flags.

See CONTRIBUTING.md.