tparse

README

tparse

A command line tool for analyzing and summarizing go test output.

Don't forget to run go test with -json flag.

Pass	Fail

By default, tparse will always return a summary box containing package-level details followed by errors, if any.

To get a summary table of passed tests run tparse with the -pass flag. Tests are grouped by package and sorted by elapsed time (longest to shortest).

See but why?! for more info.

Installation

go get github.com/mfridman/tparse

Usage

Once tparse is installed there are 2 ways to use it:

1. Run go test as you normally would, but add the -json flag and pipe the output to tparse.

go test fmt -json | tparse -all

1. Save the output of go test with the -json flag into a file and call tparse with filename as an argument.

go test fmt -json > fmt.out
tparse -all fmt.out

Tip: run tparse -h to get usage and options.

But why?!

go test is a great tool, but a bit verbose. Sometimes all one wants is failures; grouped by package, printed with a dash of color and bubbled to the top.

By default, tparse attempts to do just that, output a package-level summary followed by all failed tests (if any).

But we can take it a bit further. With -all (-pass and -skip combined) we can get additional info, such as which tests were skipped or elapsed time of each passed test.

tparse comes with a -dump flag to print back everything that would have otherwise been printed. Enables users to retrieve the original go test output.

Some displays are narrow. Some may find the -smallscreen flag useful. Which takes long test names and makes them vertical heavy:

TestSubtests/an_awesome_but_long/subtest_for_the/win

TestSubtests
 /an_awesome_but_long
 /subtest_for_the
 /win

tparse aims to provide a simply alternative to those one-liner bash functions.

p.s. tparse uses itself in travis pipeline:

Example here