Task Summary
Codecov already receives coverage from four flags (frontend, amber, python, agent-service) plus five per-service platform flags. Codecov also offers Test Analytics — JUnit-XML-based reporting that surfaces failing tests with stack traces in PR comments, detects flaky tests against main, and tracks per-test run-time / failure-rate over time. The data is independent of coverage and uploads through the same codecov/codecov-action@v5 with report_type: test_results.
Enable it for every CI test job:
- pytest (
python) — add --junit-xml=junit.xml
- Vitest (
frontend, unit + browser) — configure JUnit reporter in vitest.config.ts / vitest.browser.config.ts
bun test (agent-service) — add --reporter=junit --reporter-outfile=junit.xml- ScalaTest (
amber, amber-integration, five platform matrix entries) — ThisBuild / Test / testOptions gets -u target/test-reports
Then add one codecov/codecov-action@v5 upload step per test job with report_type: test_results, reusing the existing flag name and CODECOV_TOKEN.
Task Type
Task Summary
Codecov already receives coverage from four flags (frontend, amber, python, agent-service) plus five per-service
platformflags. Codecov also offers Test Analytics — JUnit-XML-based reporting that surfaces failing tests with stack traces in PR comments, detects flaky tests againstmain, and tracks per-test run-time / failure-rate over time. The data is independent of coverage and uploads through the samecodecov/codecov-action@v5withreport_type: test_results.Enable it for every CI test job:
python) — add--junit-xml=junit.xmlfrontend, unit + browser) — configure JUnit reporter invitest.config.ts/vitest.browser.config.tsbun test(agent-service) — add--reporter=junit --reporter-outfile=junit.xmlamber,amber-integration, fiveplatformmatrix entries) —ThisBuild / Test / testOptionsgets-u target/test-reportsThen add one
codecov/codecov-action@v5upload step per test job withreport_type: test_results, reusing the existing flag name andCODECOV_TOKEN.Task Type