-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Open
Description
Description
There is no unified or automated way to generate and view test coverage reports across all test suites. This makes it difficult to assess overall test coverage and identify untested code paths.
Environment
- Chainlink repo: develop branch
- Go 1.22+
- OS: Linux 6.11.0-29-generic
Examples
- No top-level script or Makefile target for generating a combined coverage report.
- Individual packages may generate coverage, but not aggregated.
Steps to Reproduce
- Attempt to generate a unified coverage report (e.g.,
go test -coverprofile=coverage.out ./...
). - Observe that results are fragmented or missing for some packages.
Additional Info
- Consider adding a Makefile target or script for unified coverage.
- Use tools like
go tool cover
to visualize combined coverage.
Metadata
Metadata
Assignees
Labels
No labels