The 1.10 release notes say:

The go test command now automatically runs go vet on the package being tested, to identify significant problems before running the test. Any such problems are treated like build errors and prevent execution of the test. Only a high-confidence subset of the available go vet checks are enabled for this automatic check. To disable the running of go vet, use go test -vet=off.

That kind of buries the lede: the fact that it only runs a subset by default is important, especially since some of the checks that are not currently enabled detect significant errors (see #24112).

I'm not sure whether it's too late to revise the release notes, but it might be clearer to move that information up front:

The go test command now automatically runs a high-confidence subset of go vet checks on the package being tested, to identify significant problems before running the test. Any such problems are treated like build errors and prevent execution of the test. To disable the running of go vet, use go test -vet off.

It would also be helpful to document how to add more flags to the default set, or whether that's even possible. (If I run go test -vet all, is that expected to do the right thing?)

Change https://golang.org/cl/107077 mentions this issue: cmd/go: document which vet tests are enabled during go test