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
You can't use any of custom flags (-check.*) outside the tests directory (all flags handled by the test suite itself), so you can't use syntax like ./... with custom flags.
You can use custom flags only when you are running tests in the current directory.
The -check.* flags are interpreted by the test executable that is built. So they can't be interpreted before selecting which packages to test.
Instead, you can run:
go test -v ./test/... -check.f TestSuite
This will cause go test to pass the arguments after the package name through to the test executable(s) as is. Note that if some of the selected packages aren't using go-check, then they will likely fail due to the unknown command line argument.
Folder structure:
run_test.go
abc_test.go
Running
go test -v ./test/...
works.Output:
Running
go test -v -check.f TestSuite ./test/...
does not work: I get a[no test files]
outputThe text was updated successfully, but these errors were encountered: