The coverage report does not report on files that has no corresponding *_test.go files about test-infra HOT 6 CLOSED

cc @adrcunha
cc @jessiezcc
cc @evankanderson

from test-infra.

from test-infra.

For auto-generated files, we can flag the file with coverage-excluded so that code coverage will ignore it. see below for an example
/pkg//testing/ coverage-excluded=true

from test-infra.

Do we really want to include the data from source files without corresponding _test.go? I think our consensus was to ignore them
In terms of reporting, what do you think the report would look like if we are to include those files? @srinivashegde86

from test-infra.

the tool should be smart enough to include coverage report of files without test files. If we expect there to be test files for every file needing coverage, we should explicitly state that:

1. Files with no corresponding *_test.go will not be included in the coverage report.
2. Add a presumbmit check to make sure that all *.go files either have a *_test.go file or the coverage-ignore gitattribute. This check will be repo-specific and not at this tool's discretion though.

from test-infra.

fixed by the last two commits here: https://github.com/steuhs/test-infra/commits/re-org

from test-infra.