run: automatically turn on verbose mode if run with "go test -v" #126
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If I'm working on a project that doesn't use go-check, I can run
go test
to see only failures, orgo test -v
to see status messages as each test is run. If the project is using go-check though, I'd need to rungo test -v -check.v
for the latter.This is a pain if I've got a set of packages with some using go-check and others not, and want to run tests on all of them. If I run
go test -v ./...
, I miss out on status messages for the go-check modules. If I rungo test -v ./... -check.v
, the packages that don't use go-check fail because they don't understand the flag.I can't think of many cases where you'd want to enable stdlib verbose mode but not go-check verbose mode, so this PR automatically turns on go-check verbose mode by checking
testing.Verbose()
. Looking at the docs on pkg.go.dev, this was added in Go 1.1, so shouldn't introduce a compatibility problem.