TEST-INFRA: [ci-pipeline-design] Upload artifacts from test and coverage jobs #1980

New issue

Open

opened 2026-04-03 00:29:45 +00:00 by freemo · 1 comment

freemo commented

2026-04-03 00:29:45 +00:00

Owner

Metadata

Branch: chore/ci-upload-test-coverage-artifacts
Commit Message: chore(ci): upload test and coverage reports as artifacts from unit, integration, and coverage jobs
Milestone: v3.8.0
Parent Epic: #1678

Background and Context

The benchmark-regression and benchmark-publish jobs in ci.yml already upload artifacts, but the unit_tests, integration_tests, and coverage jobs do not. When these jobs fail or produce unexpected results, there is no easy way to inspect the generated reports without re-running the pipeline locally. Uploading reports as artifacts would make debugging significantly easier by allowing developers to download and inspect them directly from the Forgejo UI.

Expected Behavior

The unit_tests, integration_tests, and coverage jobs should each upload their respective reports as CI artifacts, making them available for download from the Forgejo UI after each pipeline run.

Acceptance Criteria

The unit_tests job uploads the Behave test report as an artifact.
The integration_tests job uploads the Robot Framework test report as an artifact.
The coverage job uploads the HTML coverage report as an artifact.
All artifacts are accessible and downloadable from the Forgejo UI.
The CI pipeline continues to pass after these changes.

Subtasks

Identify the output paths for the Behave test report in the unit_tests job
Add an artifact upload step to the unit_tests job in ci.yml for the Behave report
Identify the output paths for the Robot Framework test report in the integration_tests job
Add an artifact upload step to the integration_tests job in ci.yml for the Robot report
Identify the output path for the HTML coverage report in the coverage job
Add an artifact upload step to the coverage job in ci.yml for the HTML coverage report
Verify all artifacts appear in the Forgejo UI after a pipeline run
Run nox (all default sessions), fix any errors
Verify coverage >= 97% via nox -s coverage_report

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
The unit_tests, integration_tests, and coverage jobs each upload their respective reports as artifacts.
The artifacts are available for download from the Forgejo UI.
The CI pipeline still passes with all checks green.
A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
All nox stages pass.
Coverage >= 97%

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

## Metadata - **Branch**: `chore/ci-upload-test-coverage-artifacts` - **Commit Message**: `chore(ci): upload test and coverage reports as artifacts from unit, integration, and coverage jobs` - **Milestone**: v3.8.0 - **Parent Epic**: #1678 ## Background and Context The `benchmark-regression` and `benchmark-publish` jobs in `ci.yml` already upload artifacts, but the `unit_tests`, `integration_tests`, and `coverage` jobs do not. When these jobs fail or produce unexpected results, there is no easy way to inspect the generated reports without re-running the pipeline locally. Uploading reports as artifacts would make debugging significantly easier by allowing developers to download and inspect them directly from the Forgejo UI. ## Expected Behavior The `unit_tests`, `integration_tests`, and `coverage` jobs should each upload their respective reports as CI artifacts, making them available for download from the Forgejo UI after each pipeline run. ## Acceptance Criteria - The `unit_tests` job uploads the Behave test report as an artifact. - The `integration_tests` job uploads the Robot Framework test report as an artifact. - The `coverage` job uploads the HTML coverage report as an artifact. - All artifacts are accessible and downloadable from the Forgejo UI. - The CI pipeline continues to pass after these changes. ## Subtasks - [ ] Identify the output paths for the Behave test report in the `unit_tests` job - [ ] Add an artifact upload step to the `unit_tests` job in `ci.yml` for the Behave report - [ ] Identify the output paths for the Robot Framework test report in the `integration_tests` job - [ ] Add an artifact upload step to the `integration_tests` job in `ci.yml` for the Robot report - [ ] Identify the output path for the HTML coverage report in the `coverage` job - [ ] Add an artifact upload step to the `coverage` job in `ci.yml` for the HTML coverage report - [ ] Verify all artifacts appear in the Forgejo UI after a pipeline run - [ ] Run `nox` (all default sessions), fix any errors - [ ] Verify coverage >= 97% via `nox -s coverage_report` ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - The `unit_tests`, `integration_tests`, and `coverage` jobs each upload their respective reports as artifacts. - The artifacts are available for download from the Forgejo UI. - The CI pipeline still passes with all checks green. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. - All nox stages pass. - Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

freemo added this to the v3.8.0 milestone

2026-04-03 00:30:50 +00:00

freemo added a new dependency

2026-04-03 00:32:06 +00:00

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

freemo commented

2026-04-03 02:43:38 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Low (confirmed)
Milestone: v3.8.0 (already assigned — CI infrastructure)
MoSCoW: Could Have — Uploading test artifacts from CI is a nice-to-have for debugging failed CI runs but does not block any deliverables.

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Low (confirmed) - **Milestone**: v3.8.0 (already assigned — CI infrastructure) - **MoSCoW**: Could Have — Uploading test artifacts from CI is a nice-to-have for debugging failed CI runs but does not block any deliverables. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner

freemo added the

MoSCoW

Could have

label

2026-04-03 02:44:15 +00:00