TEST-INFRA: [coverage-gaps] Configure CI to publish coverage reports #2226

New issue

Open

opened 2026-04-03 09:39:16 +00:00 by freemo · 1 comment

freemo commented

2026-04-03 09:39:16 +00:00

Owner

Metadata

Branch: chore/ci-coverage-report-publishing
Commit Message: chore(ci): configure CI to publish coverage reports to public service
Milestone: v3.7.0
Parent Epic: #1678

Description

There is currently no way to access code coverage reports for this repository. The nox -s coverage_report session generates a build/coverage.xml file, but this artifact is not stored in the repository and is not published to a public-facing service.

This lack of visibility makes it impossible for developers and automated agents to identify untested code paths and address coverage gaps.

Proposed Solution

Integrate a code coverage service (such as Codecov or Coveralls) into the Forgejo CI pipeline.

Subtasks

Configure the CI workflow to run the nox -s coverage_report session after tests complete.
Add a step to the CI workflow to upload the generated build/coverage.xml report to the chosen coverage service.
Add a coverage badge to the README.md file.
Ensure that the service posts a summary comment on pull requests detailing the impact on code coverage.

Definition of Done

A code coverage report is publicly accessible via a URL.
Pull requests are automatically updated with coverage statistics.
The README.md displays a real-time coverage badge.
All nox stages pass.
Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

## Metadata - **Branch**: `chore/ci-coverage-report-publishing` - **Commit Message**: `chore(ci): configure CI to publish coverage reports to public service` - **Milestone**: v3.7.0 - **Parent Epic**: #1678 ## Description There is currently no way to access code coverage reports for this repository. The `nox -s coverage_report` session generates a `build/coverage.xml` file, but this artifact is not stored in the repository and is not published to a public-facing service. This lack of visibility makes it impossible for developers and automated agents to identify untested code paths and address coverage gaps. ## Proposed Solution Integrate a code coverage service (such as Codecov or Coveralls) into the Forgejo CI pipeline. ## Subtasks - [ ] Configure the CI workflow to run the `nox -s coverage_report` session after tests complete. - [ ] Add a step to the CI workflow to upload the generated `build/coverage.xml` report to the chosen coverage service. - [ ] Add a coverage badge to the `README.md` file. - [ ] Ensure that the service posts a summary comment on pull requests detailing the impact on code coverage. ## Definition of Done - [ ] A code coverage report is publicly accessible via a URL. - [ ] Pull requests are automatically updated with coverage statistics. - [ ] The `README.md` displays a real-time coverage badge. - [ ] All nox stages pass. - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

freemo added this to the v3.7.0 milestone

2026-04-03 09:39:25 +00:00

freemo added a new dependency

2026-04-03 09:39:57 +00:00

#1678 Epic: CI Execution Time Optimization — Timeouts, Concurrency, and Coverage Artifact Sharing

freemo self-assigned this

2026-04-03 16:57:58 +00:00

freemo added the

MoSCoW

Must have

label

2026-04-03 18:27:18 +00:00

freemo commented

2026-04-03 18:27:30 +00:00

Author

Owner

MoSCoW classification: Must Have

Rationale: Test coverage must be maintained at or above 97% (CONTRIBUTING.md). Zero-coverage modules and missing test levels directly violate this requirement.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

MoSCoW classification: **Must Have** Rationale: Test coverage must be maintained at or above 97% (CONTRIBUTING.md). Zero-coverage modules and missing test levels directly violate this requirement. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner

freemo referenced this issue

2026-04-03 19:45:40 +00:00

Task: Autonomous build progress report — v3.7.0 Production Push — 2026-04-03 #2436