Proposal Details

Running go test ./... on a project with many packages and having all of the ok ... (cached) [no tests to run] lines repeatedly flickering over the screen is

1. probably not a good thing for eyes/people with epilepsy.
2. making identifying failing tests harder than it should be (having to scroll up looking for that FAILED statement)

Tests should ideally be fast enough that these status messages should not be needed.

I have searched for this, and the closest I have found is a go nuts thread that suggests something ala:

go test ./... |  grep -Ev "^(\?|ok)\s+"

Which works, but this should be a flag or something on the go test command.