diff options
Diffstat (limited to 'src/cmd/go/testdata/script/test_flag.txt')
-rw-r--r-- | src/cmd/go/testdata/script/test_flag.txt | 38 |
1 files changed, 38 insertions, 0 deletions
diff --git a/src/cmd/go/testdata/script/test_flag.txt b/src/cmd/go/testdata/script/test_flag.txt new file mode 100644 index 0000000..6ef4529 --- /dev/null +++ b/src/cmd/go/testdata/script/test_flag.txt @@ -0,0 +1,38 @@ +[short] skip + +go test flag_test.go -v -args -v=7 # Two distinct -v flags +go test -v flag_test.go -args -v=7 # Two distinct -v flags + +# Using a custom flag mixed with regular 'go test' flags should be OK. +go test -count=1 -custom -args -v=7 + +# However, it should be an error to use custom flags when -c is used, +# since we know for sure that no test binary will run at all. +! go test -c -custom +stderr '^go: unknown flag -custom cannot be used with -c$' + +# The same should apply even if -c comes after a custom flag. +! go test -custom -c +stderr '^go: unknown flag -custom cannot be used with -c$' + +-- go.mod -- +module m +-- flag_test.go -- +package flag_test + +import ( + "flag" + "log" + "testing" +) + +var v = flag.Int("v", 0, "v flag") + +var custom = flag.Bool("custom", false, "") + +// Run this as go test pkg -v=7 +func TestVFlagIsSet(t *testing.T) { + if *v != 7 { + log.Fatal("v flag not set") + } +} |