Does go-junit-report actually require stderr from go test ? about go-junit-report HOT 3 CLOSED

But you're consuming the error message and leaving the user with no feedback.

If you re-printed the errors to stderr, or embedded the error information in the xunit report, that would be ok, but you don't, so 2>&1 is just not usable...

Personally, I'm using a makefile with

SHELL := $(shell which bash)
.SHELLFLAGS := -eo pipefail -c

and that takes care of detecting the build error, with no need for stderr parsing by go-junit-report.

Why not make it configurable with a switch ?

from go-junit-report.

We just got bit by this ourself... We solved it by splitting the stdout stream with tee:

        go test -v 2>&1 \
          | tee >(go-junit-report > report.xml) \
          | cat -e

from go-junit-report.

PR #45 added support for handling build errors. This is necessary to make sure both regular output and build errors on stderr are captured.

from go-junit-report.