You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Picking up from #86 (comment), @ti-mo has a nice suggestion to split tparse output and go test output when using -follow.
Briefly, the -follow flag parses the go test json event and prints the output just like running go test without tparse. This enables tparse to accumulate test data without a noticeable difference to the caller, as they can view (read "follow") the go test output.
The proposal is to pipe the go test output to stderr and the tparse output to stdout.
The text was updated successfully, but these errors were encountered:
Picking up from #86 (comment), @ti-mo has a nice suggestion to split tparse output and go test output when using
-follow
.Briefly, the
-follow
flag parses thego test
json event and prints the output just like runninggo test
without tparse. This enables tparse to accumulate test data without a noticeable difference to the caller, as they can view (read "follow") the go test output.The proposal is to pipe the go test output to
stderr
and the tparse output tostdout
.The text was updated successfully, but these errors were encountered: