gotestfmt: go test output for humans

Have you ever been in a situation where the CI system gave you a test log of a few megabytes and you had to find a but in it? Even worse, the test run was in parallel, so the log had lines from various tests running in parallel in them?

Go somewhat mitigates this problem by providing the t.Log() and t.Logf() functions, which let you interweave the output like this:

=== RUN   TestParallel1
=== PAUSE TestParallel1
=== RUN   TestParallel2
=== PAUSE TestParallel2
=== CONT  TestParallel1
    parallel_test.go:10: Test message 1
=== CONT  TestParallel2
=== CONT  TestParallel1
    parallel_test.go:12: Test message 2
--- PASS: TestParallel1 (5.01s)
=== CONT  TestParallel2
    parallel_test.go:18: Test message 1
    parallel_test.go:20: Test message 2
--- PASS: TestParallel2 (10.02s)
PASS
ok      github.com/haveyoudebuggedit/example    10.048s

While this makes sense, it still doesn’t make it readable. To a human, at least. Development environments can pick these apart, so you’ll have a nicely formatted output, but in CI systems you’ll have to find a tool to take care of that.

There are a great many tools out there that transform the reports in, for example, the JUnit XML format. One such example is gotestsum. However, the resulting XML or JSON file still needs to be transformed to create beautiful, easy to use output in the CI system.

GitHub Actions, for example, lets you use workflow commands to create foldable sections or issue warnings for file lines.

So, we set out to solve this problem: create a simple utility that takes the go test output and transforms it into beautiful, colored, foldable logs with icons on GitHub actions or other CI systems.

The result is gotestfmt, a tool that you can install into your GitHub Actions pipeline in under 5 minutes, or integrate with other CI systems quickly by creating a custom rendering template.