ci: send test results to Codecov Test Analytics - #769
Conversation
The Codecov Test Analytics page for this repo has no data: go-check uploads coverage.out and nothing else, so there is no flaky-test detection, no per-test durations and no failure history. netresearch/.github#333 added enable-test-results to the shared workflow, which runs the unit tests through gotestsum and uploads the JUnit report. Turning it on here is the whole change. The template.yaml drift reason is updated to name the new input, and corrects the e2e count it records: 11 tests now, one of them browser-driven. Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Automated approval for maintainer PR
All automated quality gates passed. See SECURITY_CONTROLS.md for compensating controls.
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s CI configuration to start publishing JUnit-style unit test results to Codecov Test Analytics (in addition to the existing coverage upload), so Codecov can show per-test timing/history and flaky-test signals for this repo.
Changes:
- Enable
enable-test-results: truefor the sharedgo-checkreusable workflow invocation. - Update
.github/template.yaml’s intentional drift note to document the new input and correct the recorded e2e test count to 11.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/workflows/ci.yml |
Enables test-results publishing in the shared go-check workflow via enable-test-results: true. |
.github/template.yaml |
Updates the intentional drift reason to include the new CI input and adjusted e2e test count documentation. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #769 +/- ##
==========================================
+ Coverage 87.70% 87.72% +0.01%
==========================================
Files 90 90
Lines 12057 12057
==========================================
+ Hits 10575 10577 +2
+ Misses 1193 1191 -2
Partials 289 289
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
Follow-up to netresearch/.github#333, which is merged.
Why
Codecov's Test Analytics page for this repo is empty —
go-checkuploadscoverage.outand nothing else, so there is no flaky-test detection, no per-test durations, and no failure history. That is whatapp.codecov.io/gh/netresearch/ofelia/tests/newshows as unconfigured.What changes
One input. With
enable-test-results: truethe shared workflow runs the unit tests through gotestsum — which drivesgo test -jsonand writes a JUnit report next to the coverage profile — and uploads it viacodecov/codecov-actionwithreport_type: test_results.Nothing about which tests run changes: the flags, packages and coverage threshold are the same, and the coverage upload is untouched.
template.yaml's drift reason is updated to name the new input, and the e2e count it records is corrected to 11 (one of them browser-driven, added in #767).Verification
The input exists on the shared workflow's
main(go-check.yml:88), so the call resolves. Locally, the invocation the shared workflow now uses produces both artifacts from a single run — a valid JUnit report and the coverage profile the threshold step and the Codecov upload consume.The proof that matters is on this PR's own CI: the Build & Test job should report the upload, and the Test Analytics page should stop being empty once it lands.