tested on v.2.9.0
ginkgo -coverpkg=./... -coverprofile=ginko.out --output-dir build/ ./...
go test -coverpkg=./... -coverprofile=build/gotest.out ./...
number of lines in the ginkgo.out 85
number of lines in the gotest.out 773
I tried in specific folders within my project like ./cli where my cobra commands are in place
and same behaviour but at folder level, less lines of test are covered in ginkgo.
After comparing 2 files, I have the feeling that ginkgo only take into account coverage of code of the instructed folder, but this folder is possible is calling to functions in other packages.
tested on
v.2.9.0ginkgo -coverpkg=./... -coverprofile=ginko.out --output-dir build/ ./...go test -coverpkg=./... -coverprofile=build/gotest.out ./...number of lines in the ginkgo.out 85
number of lines in the gotest.out 773
I tried in specific folders within my project like
./cliwhere my cobra commands are in placeand same behaviour but at folder level, less lines of test are covered in ginkgo.
After comparing 2 files, I have the feeling that ginkgo only take into account coverage of code of the instructed folder, but this folder is possible is calling to functions in other packages.