How to `go test` all tests in my project?

Question

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 under the dir ./.

What's the command to do this?

score 545 · Accepted Answer · edited Apr 07 '20 at 14:47

545

This should run all tests in current directory and all of its subdirectories:

$ go test ./...

This should run all tests for given specific directories:

$ go test ./tests/... ./unit-tests/... ./my-packages/...

This should run all tests with import path prefixed with foo/:

$ go test foo/...

This should run all tests import path prefixed with foo:

$ go test foo...

This should run all tests in your $GOPATH:

$ go test ...

edited Apr 07 '20 at 14:47

omurbek

742
1
7
23

answered May 03 '13 at 07:05

zzzz

87,403
16
175
139

7

FYI in zsh, the bare `...` in the last example must be escaped, IE `go test \...` – Gabe Kopley Jun 21 '16 at 20:42
When I am trying to run all the tests in subdir I am getting `go: warning: "subdir/..." matched no packages` – Ivan Aracki May 17 '19 at 08:58
@zzzz how to run tests for specific folders? say "go test foo... bar...? – omurbek Apr 06 '20 at 13:52
`go test ./...` is really a great command!. Thanks for helping :) – bumblebee Jun 13 '20 at 10:03
1

Don't forget `-v` parameter if you want to see outputs of successful tests too. – ufukty Aug 12 '21 at 09:56
Where is "./..." documented? It's hard to search on Google – Eric Burel Nov 08 '22 at 14:44

user7610 · Answer 2 · 2017-10-26T16:15:04.410

81

From Go 1.9 onwards, use

go test ./...

In Go 1.6 through 1.8, the ./... matched also the vendor directory. To skip vendored packages, you'd use

go test $(go list ./... | grep -v /vendor/)

Sources: https://github.com/golang/go/issues/11659, https://github.com/golang/go/issues/14417, https://github.com/go-lang-plugin-org/go-lang-idea-plugin/issues/2366, @nickgrim's comment.

edited Oct 26 '17 at 16:15

answered Mar 07 '16 at 20:01

user7610

25,267
15
124
150

1

As easy as this solution looks, it makes it much more complicated for people on Windows (I'm not but some of my team mates are) to run this. The beauty of Go running native on each platform without the need for a Makefile is great. – Konrad Kleine Sep 14 '16 at 08:47
6

Worth pointing out that [as of Go 1.9](https://golang.org/doc/go1.9#vendor-dotdotdot) `./...` no longer matches the `./vendor/` directory, so you can run all of your tests and none of the vendor-tests with `go test ./...` – nickgrim Oct 26 '17 at 15:32

score 16 · Answer 3 · answered May 21 '18 at 11:38

Folder Structure

ProjectName/folderName1/file_test.go
ProjectName/folderName2/file1_test.go
ProjectName/folderName3/file2_test.go

go test command Command

   ProjectName$ go test -v ./...
    ProjectName$ go test  ./...
    ProjectName$ go test -cover ./...

Coverage Report for the Entire Project

ok      ProjectName/folderName1 10%
ok      ProjectName/folerName2  90%
ok      ProjectName/folerName2  85%

How to `go test` all tests in my project?

3 Answers3

Linked

Related