Running `gocov test` doesn't appear to test subdirectories about gocov HOT 3 CLOSED

Directory structure does not necessarily imply a relationship between packages, even if that's usually the case. So you're right, running "gocov test" will not test subdirectories; it only tests the specified package. If you don't specify a package on the command line, it tests the package in the working directory.

It's not entirely clear to me what you want to see. You want to see coverage for your package and all packages in subdirectories? What I suggest you do is test each package using go test -coverprofile=..., and then combine the results using gocov convert. That can then be fed into gocov report or gocov annotate.

from gocov.

That's right. I want to see coverage for the package and all packages in subdirectories. It's true directory structure may not necessarily imply relationship, but to elaborate my use case: I have a package main for foo.go. In here, it may use packages from subdirectories. The intuition here is to organize the code in a modular fashion. The entire codebase in the example represents one service/component of a large system.

I thought it would be nice to run the test on the codebase as a whole. One thing I could do is to just make all subdirectory packages be the same package name as whatever my service/component is named.

Right now, my goal is two things: (1) to see an overall coverage percentage and (2) to page through the output of gocov annotate for the codebase.

I'll try your suggestion and circle back here tomorrow. Thanks!

from gocov.

Using standard go cover works from the above suggested solution. Moreover, plain simple go test ./... -cover works as well. Closing.

from gocov.