You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in the comments in devfile/registry-support#199 the Code Coverage report is being severely impacted by any changes that require generated code files to grow in content. These generated code files should be excluded as they are not testable by us. As part of the above PR there was an addition to add files ending in .gen.go to be excluded from the coverage report, however, the reports are still failing because it is not changing the previous reports. This is causing the report to be expecting those files to be covered, even if we are now ignoring them.
Investigation will need to be done into Code Coverage to see if there is a way to either remove those generated files from previous reports, or force it to ignore them moving forward.
Which area/kind this issue is related to?
/area registry
Issue Description
As discussed in the comments in devfile/registry-support#199 the Code Coverage report is being severely impacted by any changes that require generated code files to grow in content. These generated code files should be excluded as they are not testable by us. As part of the above PR there was an addition to add files ending in
.gen.go
to be excluded from the coverage report, however, the reports are still failing because it is not changing the previous reports. This is causing the report to be expecting those files to be covered, even if we are now ignoring them.Investigation will need to be done into Code Coverage to see if there is a way to either remove those generated files from previous reports, or force it to ignore them moving forward.
Code Coverage Report
Change For Exclusion
Acceptance Criteria
The text was updated successfully, but these errors were encountered: