To run a specific test of test suite in go, you need to use: -testify.m. go test -v <package> -run ^TestMyTestSuite$ -testify.m TestMethodA More simply, if the method name is unique to a package, you can always run this. go test -v <package> -testify.m TestMethodA

2014年5月19日 · Often, there's relatively fewer test functions, but each contains a table-driven set of test cases. See this article written by one of the Go team. With a table-driven test, you simply put any setup code before the loop that executes the individual test-cases specified in the table, and put any cleanup code afterwards.

As you see there are no test files in the root package, only the main.go file. You will get "no test files." The solution is to test all packages within the current working directory, recursively. go test -v ./... Or if you use govendor. govendor test +local Or you can specify which package (directory) to test. go test -v ./packagename Or test ...

2013年5月3日 · The go test command covers *_test.go files in only one dir. I want to go test the whole project, which means the test should cover all *_test.go files in the dir ./ and every children tree dir unde...

2019年2月10日 · TestMain was introduced in Go 1.4 to help with the setup/teardown of the test environment and is called instead of running the tests; quoting the release notes: If the test code contains a function func TestMain(m *testing.M)

In Go 1.14, go test -v will stream t.Log output as it happens, rather than hoarding it til the end of the test run. Under Go 1.14 the fmt.Println and t.Log lines are interleaved, rather than waiting for the test to complete, demonstrating that test output is streamed when go test -v is used. Advantage, according to Dave:

2017年5月22日 · If your test is running concurrently (for example, when testing an http Server or Client), you may encounter a race between writing to the buffer and reading from it. Instead of the buffer, we can redirect output to an os.Pipe and use a bufio.Scanner to block until output has been written by using the Scan() method.

The 'go test' command may run tests for different packages in parallel as well, according to the setting of the -p flag (see 'go help build'). For #1, you can observe this directly by having tests in multiple packages, and forcing them to be long running with a sleep.

2013年12月18日 · The go test command has support for the -c flag, described as follows:-c Compile the test binary to pkg.test but do not run it. (Where pkg is the last element of the package's import path.) As far as I understand, generating a binary like this is the way to run it interactively using GDB.

2013年6月5日 · $ go test foo_test.go But there's a catch. This works well if: foo.go is in package foo. foo_test.go is in package foo_test and imports 'foo'. If foo_test.go and foo.go are the same package (a common case) then you must name all other files required to build foo_test. In this example it would be: $ go test foo_test.go foo.go