-
Notifications
You must be signed in to change notification settings - Fork 18.1k
cmd/go: go test should be more explicit about test failures #13106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
To be specific on the scope of this issue: For |
Is the |
On the one hand, it's true that a long list of tests might scroll a failure off the screen. On the other hand, it's relatively easy to use a bash Perhaps rather than For example, this output today:
might become:
|
Is this still an issue? You should be able to run a tool that invokes |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
In the best case, the output of
go test github.com/blevesearch/bleve/...
is 88 lines long. If one of the early test fails, the error message can easily be scrolled out and short of looking at$?
or scrolling back manually, the user has no way to know the test run failed.I propose
go test
prints something visible at the end of the run in that case like:Having a prefix like
TEST RESULT:
may make it easier for tools processing test output to ignore this line in the future, should its format change (by adding the number of tests run/successful, or time it took, etc.).A
TEST RESULT: OK
might be displayed on success to.Thoughts?
The text was updated successfully, but these errors were encountered: