TEST-INFRA: [ci-execution-time] Parallelize unit and integration test suites #7195

Open
opened 2026-04-10 08:47:41 +00:00 by HAL9000 · 3 comments
Owner

Summary

The unit_tests and integration_tests jobs in .forgejo/workflows/ci.yml currently run their entire test suites serially within a single job. As the number of tests grows, these jobs will become significant bottlenecks in the CI pipeline, increasing the time it takes to get feedback on pull requests.

Metadata

  • Branch: task/ci-execution-time-parallelize-unit-integration-tests
  • Commit Message: chore(ci): parallelize unit and integration test suites via matrix strategy
  • Milestone: N/A — Backlog (see note below)
  • Parent Epic: #1678

Backlog note: This issue was discovered during autonomous operation
on milestone v3.8.0. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.

Subtasks

  • Investigate methods for splitting the test suites. This could be done by directory, by test file, or using a test runner feature that supports parallel execution with test distribution.
  • Implement a matrix strategy in the .forgejo/workflows/ci.yml file to run the split test suites in parallel across multiple jobs.
  • Ensure that test results and artifacts (like coverage data) are correctly aggregated from the parallel jobs.

Definition of Done

  • The unit and integration tests are executed in parallel across multiple CI jobs.
  • The overall execution time for the test suites is significantly reduced.
  • Test results and coverage data are correctly reported for the entire test suite.
  • All CI checks continue to pass as expected.
  • All nox stages pass.
  • Coverage >= 97%

Duplicate Check

  • Search queries: "parallel tests", "split tests", "test matrix"
  • Results: 0
  • Justification: No existing issues address the parallelization of the main unit and integration test suites.

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

## Summary The `unit_tests` and `integration_tests` jobs in `.forgejo/workflows/ci.yml` currently run their entire test suites serially within a single job. As the number of tests grows, these jobs will become significant bottlenecks in the CI pipeline, increasing the time it takes to get feedback on pull requests. ## Metadata - **Branch**: `task/ci-execution-time-parallelize-unit-integration-tests` - **Commit Message**: `chore(ci): parallelize unit and integration test suites via matrix strategy` - **Milestone**: N/A — Backlog (see note below) - **Parent Epic**: #1678 > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.8.0. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. ## Subtasks - [ ] Investigate methods for splitting the test suites. This could be done by directory, by test file, or using a test runner feature that supports parallel execution with test distribution. - [ ] Implement a matrix strategy in the `.forgejo/workflows/ci.yml` file to run the split test suites in parallel across multiple jobs. - [ ] Ensure that test results and artifacts (like coverage data) are correctly aggregated from the parallel jobs. ## Definition of Done - [ ] The unit and integration tests are executed in parallel across multiple CI jobs. - [ ] The overall execution time for the test suites is significantly reduced. - [ ] Test results and coverage data are correctly reported for the entire test suite. - [ ] All CI checks continue to pass as expected. - [ ] All nox stages pass. - [ ] Coverage >= 97% ### Duplicate Check - Search queries: "parallel tests", "split tests", "test matrix" - Results: 0 - Justification: No existing issues address the parallelization of the main unit and integration test suites. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: new-issue-creator
Author
Owner

Verified — CI optimization: parallelize unit and integration test suites. MoSCoW: Should-have. Priority: Medium.


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

✅ **Verified** — CI optimization: parallelize unit and integration test suites. MoSCoW: Should-have. Priority: Medium. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
Author
Owner

Verified — CI optimization: parallelize unit and integration test suites. MoSCoW: Should-have. Priority: Medium.


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

✅ **Verified** — CI optimization: parallelize unit and integration test suites. MoSCoW: Should-have. Priority: Medium. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
Author
Owner

Verified — CI optimization: parallelize unit and integration test suites. MoSCoW: Should-have. Priority: Medium.


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

✅ **Verified** — CI optimization: parallelize unit and integration test suites. MoSCoW: Should-have. Priority: Medium. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#7195
No description provided.