GO-JUNIT-REPORT(1)

✨ NAME ✨

go-junit-report — the little icon that turns your Go test output into JUnit XML 💅

---

🦋 SYNOPSIS 🦋

go-junit-report [-in file] [-out file] [options...]

go-junit-report -version

go-junit-report -help

---

🌸 DESCRIPTION 🌸

okay so bestie, listen. go-junit-report is the tool that converts go test output into a JUnit-compatible XML report, which is perfect for feeding into stuff like Jenkins or GitLab CI. it's giving pipeline-ready. it's giving CI royalty. 👑

By default, go-junit-report reads go test -v output — the kind generated by the standard library testing package — from stdin, and writes a JUnit XML report to stdout. that's the no-cap default behavior, periodt.

Go build and runtime errors are also supported, but heads up: for that you need stderr redirected into go-junit-report too. can't skip that step, she needs both streams.

Typical use looks like this:

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

Alternatively, go-junit-report can consume JSON output of go test. in this case, stderr still needs to be redirected for build errors to be detected — yes, same rule, no exceptions:

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

The -iocopy flag copies stdin directly to stdout, which is useful if you still want to actually see the go test output. like, bestie, you don't have to give it up entirely:

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

---

💜 OPTIONS 💜

• -in file — read the log from file. if you don't specify it, stdin is used. 💖
• -out file — write the XML report to file. if you don't specify it, stdout is used. ✨
• -iocopy — copy input to stdout. can only be used in conjunction with -out. this is useful if you want to see what was sent to go-junit-report. 👀
• -no-xml-header — do not print the XML header. that's it, that's the whole vibe. 🙈
• -p key=value — add a key=value property to the generated report. repeat this flag to add multiple properties. stack 'em up, queen 🎀
• -package-name name — specify a default package name to use if the test log doesn't contain a package name. a lil fallback for when the log is being mysterious 💅
• -parser string — set the input parser type: gotest or gojson (default: gotest).
• -set-exit-code — set exit code to 1 if tests failed. that's the dramatic exit, and honestly? valid. 💀
• -subtest-mode mode — set subtest mode: ignore-parent-results (subtest parents always pass), exclude-parents (subtest parents are excluded from the report).
• -help — print a summary of command-line options. help a girl out 🫶
• -version — print the go-junit-report version. humble brag, as she should 🌈
• -debug.print-events — print events generated by the go test parser. nyoom, look at the little events go 🦋
• -go-version string — (deprecated, use -prop) the value to use for the go.version property in the generated XML. ⚠️ bestie it is literally deprecated, go use -prop instead, i'm begging

---

🌟 EXIT STATUS 🌟

• If go-junit-report encounters an error during its operation, or doesn't understand its command-line options, 2 is returned. 😭
• If the input logs indicate the tests failed, and -set-exit-code is specified, 1 is returned. 💀
• Otherwise, 0 is returned. slay, no notes ✨

---

👑 COPYRIGHT 👑

Copyright (C) 2025 Andrej Shadura.

---

and that's the whole page, bestie 🫶 this one's from the GO-JUNIT-REPORT(1) manual, dated 2026-02-03. go forth and make your CI pretty 💖🌈✨