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
{{ message }}
This repository has been archived by the owner on Nov 20, 2019. It is now read-only.
We use go2xunit on our teamcity server. We do something like:
go test -v | tee test.out
go2xunit -input test.out -output test.xml -fail
Works great, except that we have lots of tests, and with the -v flag, go test's output is very verbose. If a test fails, you need to open up the output or the xml file and search for the failure cases. Would be nice if go2xunit supported a flag to print out a summary of the failed test cases to stdout, something like out test runners in other languages print out a summary of results (n tests run, n succeeded, n failed, etc, the format varies by language and test framework).
The text was updated successfully, but these errors were encountered:
We use go2xunit on our teamcity server. We do something like:
Works great, except that we have lots of tests, and with the -v flag, go test's output is very verbose. If a test fails, you need to open up the output or the xml file and search for the failure cases. Would be nice if go2xunit supported a flag to print out a summary of the failed test cases to stdout, something like out test runners in other languages print out a summary of results (n tests run, n succeeded, n failed, etc, the format varies by language and test framework).
The text was updated successfully, but these errors were encountered: