In this mode, go test compiles the package sources and tests found in the current directory and then, runs the resulting test binary. The first, called local directory mode, occurs when go test is invoked with no package arguments. Go’s standard error is reserved for printing errors while building the tests. To disable the running of go vet, use the -vet=off flag.Īll test output and summary lines are printed to Go’s standard output. You can view the documentation for these and other vet tests by issuing the go doc cmd/vet command. The subset of checks are: atomic, bool, buildtags, errorsas, ifaceassert, nilfunc, printf, and stringintconv. Only a high-confidence subset of the default go vet checks are used. If go vet finds any problems, go test reports those and does not run the test binary. Go’s built-in test runner ignores a directory named testdata, making it available to store ancillary data needed by the tests.Īs part of building a test binary, go test runs go vet on the package and its test source files to identify significant problems. They are then linked and run with the main test binary.
Test files that declare a package with the suffix _test are compiled as a separate package.
Files whose names begin with and underscore ( _) (including _test.go) or a dot (. Each listed package causes the execution of a separate test binary. These additional files can contain test functions, benchmark functions, and example functions. Go test recompiles each package and any files with names matching the file pattern *_test.go. Running your tests prints a summary of the test results as shown below: ok archive/tar 0.011sĪ detailed output is provided for any check that fails. The syntax used to run Go tests is as follows: go test The go test command automates testing packages named by import paths. This guide provides an introduction to unit testing in Go.
Unit and benchmark tests unit test a code#
In the Go language, go test is the built-in command that runs unit tests, example functions, and benchmarks does code profiling, and performs code coverage analysis.
Unit testing verifies the functionality of a specific section of code in isolation.
0 kommentar(er)
