TEST-INFRA: [ci-pipeline-design] Use matrix builds for tests #1875

New issue

Open

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

freemo commented

2026-04-03 00:03:55 +00:00

Owner

Metadata

Branch: task/ci-pipeline-design-matrix-builds-for-tests
Commit Message: ci(pipeline): use matrix builds for unit_tests and integration_tests jobs
Milestone: v3.7.0
Parent Epic: #1678

Background and Context

The unit_tests and integration_tests jobs in .forgejo/workflows/ci.yml currently run against a single Python version only. Running these jobs in a matrix build across all supported Python versions (e.g., 3.11, 3.12, 3.13) is a standard best practice that ensures compatibility and catches version-specific regressions early in the development cycle.

Expected Behavior

The unit_tests and integration_tests jobs in ci.yml should use a strategy.matrix block to run against all supported Python versions, ensuring the codebase is compatible with each.

Acceptance Criteria

The unit_tests job in .forgejo/workflows/ci.yml uses a strategy.matrix block covering all supported Python versions.
The integration_tests job in .forgejo/workflows/ci.yml uses a strategy.matrix block covering all supported Python versions.
The matrix includes all currently supported Python versions (e.g., 3.11, 3.12, 3.13).
The CI pipeline passes successfully for all Python versions in the matrix.

Subtasks

Identify all supported Python versions for the project.
Update the unit_tests job in .forgejo/workflows/ci.yml to use a strategy.matrix for python-version.
Update the integration_tests job in .forgejo/workflows/ci.yml to use a strategy.matrix for python-version.
Ensure all matrix job runs complete successfully.
Update features/ci_workflow_validation.feature to assert the matrix strategy is present on both jobs.
Tests (Behave): Add/update scenarios for CI workflow matrix validation.
Verify coverage >= 97% via nox -s coverage_report.
Run nox (all default sessions), fix any errors.

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
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**: `task/ci-pipeline-design-matrix-builds-for-tests` - **Commit Message**: `ci(pipeline): use matrix builds for unit_tests and integration_tests jobs` - **Milestone**: v3.7.0 - **Parent Epic**: #1678 ## Background and Context The `unit_tests` and `integration_tests` jobs in `.forgejo/workflows/ci.yml` currently run against a single Python version only. Running these jobs in a matrix build across all supported Python versions (e.g., 3.11, 3.12, 3.13) is a standard best practice that ensures compatibility and catches version-specific regressions early in the development cycle. ## Expected Behavior The `unit_tests` and `integration_tests` jobs in `ci.yml` should use a `strategy.matrix` block to run against all supported Python versions, ensuring the codebase is compatible with each. ## Acceptance Criteria - The `unit_tests` job in `.forgejo/workflows/ci.yml` uses a `strategy.matrix` block covering all supported Python versions. - The `integration_tests` job in `.forgejo/workflows/ci.yml` uses a `strategy.matrix` block covering all supported Python versions. - The matrix includes all currently supported Python versions (e.g., 3.11, 3.12, 3.13). - The CI pipeline passes successfully for all Python versions in the matrix. ## Subtasks - [ ] Identify all supported Python versions for the project. - [ ] Update the `unit_tests` job in `.forgejo/workflows/ci.yml` to use a `strategy.matrix` for `python-version`. - [ ] Update the `integration_tests` job in `.forgejo/workflows/ci.yml` to use a `strategy.matrix` for `python-version`. - [ ] Ensure all matrix job runs complete successfully. - [ ] Update `features/ci_workflow_validation.feature` to assert the matrix strategy is present on both jobs. - [ ] Tests (Behave): Add/update scenarios for CI workflow matrix validation. - [ ] Verify coverage >= 97% via `nox -s coverage_report`. - [ ] Run `nox` (all default sessions), fix any errors. ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - 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.7.0 milestone

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

freemo added a new dependency

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

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

freemo commented

2026-04-03 00:12:53 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
MoSCoW: MoSCoW/Could Have — CI/test infrastructure improvement.

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

Issue triaged by project owner: - **State**: Verified - **MoSCoW**: MoSCoW/Could Have — CI/test infrastructure improvement. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner

freemo added the

MoSCoW

Could have

label

2026-04-03 00:12:53 +00:00