gocov should accept the path globs that go test does. ie

gocov test ./... gocov test std

The goal is to be able to produce test coverage for an entire project, ie

gocov test launchpad.net/juju-core/... | gocov report

Internally gocov will execute an independent instrumentAndTest() for each package.

Discovered this nice tool a few days ago. Thank you for making it available. What I would like is an option to annotate to only show routines that have less than 100% coverage (= have at least one 'miss' mark). That could be of help to quickly find out where exactly testing could be improved. Johan

I'm not quite sure what's happening here, but I'm trying to run tests in github.com/couchbaselabs/cbgb/cbgb and I get the following:

/var/folders/nt/_3y11_t12szbmgshvz6zgbhh0000gn/T/gocov343768907/src/pkg/github.com/couchbaselabs/cbgb/cbgb/main.go:11:2: no Go source files in /var/folders/nt/_3y11_t12szbmgshvz6zgbhh0000gn/T/gocov343768907/src/pkg/github.com/couchbaselabs/cbgb
go test failed: exit status 1
failed to parse gocov output: stat /var/folders/nt/_3y11_t12szbmgshvz6zgbhh0000gn/T/gocov343768907/gocov.out: no such file or directory

As described in the issue title.

Ideally, when I run gocov test ./... under a certain project folder, I want to see the reported total line numbers be the total lines to be covered in the project, no matter whether there is test file existing for a certain package or not.

However, this is not what gocov does for now, in my experiments. It seems that if there is no test file existing for a certain package, the line numbers in that package are not added to the total line number count. (please let me know if you are not able to replicate this result. :)

Also, in some circumstances, we don't want to add tests for some packages, for example, some packages are solely for testing purposes like mocks, testdata etc. If we do want to count lines no matter whether there is test file existing, we should also add an option to ignore packages. That would make the tool report the total line numbers correctly as I expect.

Thanks!

P.S. gocov is really an awesome and handy tool! It enables and empowers me to do my testing job! :)

Hello,

I may be mistaking something, but for some reason gocov will annotate and report coverage on transitive dependencies. Am I missing something, or is this a bug ?

% go get github.com/davecheney/a/... % gocov test github.com/davecheney/a/b | gocov report warning: building out-of-date packages: github.com/axw/gocov github.com/davecheney/a time os fmt flag runtime/pprof testing installing these packages with 'go test -i github.com/davecheney/a/b' will speed future tests.

ok github.com/davecheney/a/b 0.008s

github.com/davecheney/a/a.go A 100.00% (1/1) github.com/davecheney/a - 100.00% (1/1)

github.com/davecheney/a/b/b.go B 66.67% (2/3) github.com/davecheney/a/b - 66.67% (2/3)

Why is the coverage of package a being reported ?

In some cases, the 'gocov test' is generating a json file which contains duplicate package name records. This is happening despite the fact that there is not a duplicate package name. Due to this incorrect behavior the generated json is unusable by the 'gocov report' as the condition on line 88 in report.go is met and panic("package already exists: result merging not implemented yet") is executed.

go test -cover refuses to run tests from multiple package at once. I wrote a function to work around this in TestCoverage.run(), see https://github.com/maruel/pre-commit-go/blob/master/checks/checks.go#L532.

It runs each package test independently and concurrently, each with their own coverage file, then merges all the coverage files into one. It's ~130 lines of code in practice.

This feature request is to handle this automatically and transparently inside gocov so that the following command would work:

gocov test ./... | gocov report

It would be nice to have an output in Cobertura format for integration with Jenkins/Hudson and other CIs. Example is there: https://raw.github.com/jenkinsci/cobertura-plugin/master/src/test/resources/hudson/plugins/cobertura/coverage-with-data.xml

As the title indicates, this will not compile with Go 1.0.3 on Windows as of commit cacb452347903453c8483c92e2ce1842c1ceef8a.

The error message is: $GOPATH\src\github.com\axw\gocov\io.go:35: cannot use int(w) (type int) as type syscall.Handle in function argument.

In my testing code, I use relative paths to pull in fixtures (non-go files). This however doesn't work because there is a new, temporary path being generated such as:

/var/folders/qy/zmrxj1t14mnbxsxrz9gtknxc0000gn/T/gocov672324733/src/pkg/github.com/imosquera/uploadthis/conf

for gocov to work. Whats the best way to get the original file path?

Sorry if I'm just blind to see it(1), but it seems to me that there's no way to pass-through parameters to the "underlying" 'go test'.

Specifically, my problem is that I need to add -timeout (or -test.timeout) as the package I want to run gocov against is taking about 4 minutes to test w/o the coverage tooling and it timeouts after 600 secs with it.

However, the need to pass any other parameters is a general problem, which should be addressed (if not solved already[1]).

I have got the kubernetes coverprofile with make test, I want to convert the profile to html with gocov-html, but when I run gocov to convert the combined-coverage.out to json format under the dir of /opt/zz/kubernetes which is the source root of my code, it raise the following error messages: error: open /opt/zz/kubernetes/vendor/k8s.io/kubernetes/vendor/k8s.io/api/core/v1/generated.pb.go: no such file or directory unmarshal coverage data: unexpected end of JSON input

I found that the file exist, but the path with duplicate parts, the exist file path is /opt/zz/kubernetes/vendor/k8s.io/api/core/v1/generated.pb.go, I guess that there must be some misconfiguration, can anyone help me?

I would like to exclude some deprecated methods from the code coverage calculation. Is it currently possible to add a comment above the method which tells gocov to not count this method against the final result?

Running the command: gocov test /go/src/github.com/xxx/fff/xx-controller/... | gocov-xml > /reports/coverage.xml it fails with: # github.com/xxx/fff/xx-controller/router #11 12.45 xx-controller/router/router.go:168: Info call has possible formatting directive %#v #11 12.48 error: exit status 2 #11 12.48 panic: EOF

The code is log.Info("NoRoute claims: %#v\n", claims)

Is it possible to generate output in the same format as standard go test does? Some tools require output to be in standard go test format, not json. I wonder if there is any limitation to do this. In theory it could be directly generated from json... however I'm not sure if there are any known limitations?

The instrumentation code has become increasingly complex. As bugs are fixed, new ones are getting introduced; automated tests would be useful to mitigate this.