TEST-INFRA: [ci-execution-time] Investigate and Parallelize E2E Test Suite #2344

Closed
opened 2026-04-03 15:06:23 +00:00 by freemo · 2 comments
Owner

Metadata

  • Branch: test/ci-parallelize-e2e-test-suite
  • Commit Message: test(ci): investigate and parallelize e2e test suite
  • Milestone: v3.2.0
  • Parent Epic: (to be linked — see dependency)

Summary

The e2e_tests job in the CI pipeline has a 45-minute timeout, which is a strong indicator that it is a major bottleneck in the CI execution time. The current implementation runs the entire E2E test suite as a single command (nox -s e2e_tests), which does not take advantage of potential parallelization.

Background and Context

Long-running CI jobs reduce developer feedback speed and increase the cost of every pipeline run. The E2E test suite is the most likely candidate for parallelization because it is the slowest stage and is composed of independent test scenarios that do not share state.

Expected Behavior

The E2E test suite should be split into independent chunks and executed in parallel, significantly reducing the wall-clock time of the e2e_tests CI job.

Acceptance Criteria

  • The E2E test suite is analyzed and long-running tests are identified.
  • The suite is split into independent, parallelizable chunks.
  • The .forgejo/workflows/ci.yml file is updated to run chunks in parallel (matrix strategy or parallel steps).
  • The e2e_tests job execution time is measurably and significantly reduced.

Subtasks

  • Analyze the E2E test suite to identify long-running tests.
  • Split the E2E test suite into smaller, independent chunks that can be run in parallel.
  • Update the .forgejo/workflows/ci.yml file to run the E2E test chunks in parallel using a matrix strategy or multiple parallel steps.
  • Verify all nox stages pass after the change.
  • 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 E2E test suite is parallelized and the e2e_tests job execution time is significantly reduced.
  • 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 details.
  • 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**: `test/ci-parallelize-e2e-test-suite` - **Commit Message**: `test(ci): investigate and parallelize e2e test suite` - **Milestone**: v3.2.0 - **Parent Epic**: *(to be linked — see dependency)* ## Summary The `e2e_tests` job in the CI pipeline has a 45-minute timeout, which is a strong indicator that it is a major bottleneck in the CI execution time. The current implementation runs the entire E2E test suite as a single command (`nox -s e2e_tests`), which does not take advantage of potential parallelization. ## Background and Context Long-running CI jobs reduce developer feedback speed and increase the cost of every pipeline run. The E2E test suite is the most likely candidate for parallelization because it is the slowest stage and is composed of independent test scenarios that do not share state. ## Expected Behavior The E2E test suite should be split into independent chunks and executed in parallel, significantly reducing the wall-clock time of the `e2e_tests` CI job. ## Acceptance Criteria - The E2E test suite is analyzed and long-running tests are identified. - The suite is split into independent, parallelizable chunks. - The `.forgejo/workflows/ci.yml` file is updated to run chunks in parallel (matrix strategy or parallel steps). - The `e2e_tests` job execution time is measurably and significantly reduced. ## Subtasks - [ ] Analyze the E2E test suite to identify long-running tests. - [ ] Split the E2E test suite into smaller, independent chunks that can be run in parallel. - [ ] Update the `.forgejo/workflows/ci.yml` file to run the E2E test chunks in parallel using a matrix strategy or multiple parallel steps. - [ ] Verify all nox stages pass after the change. - [ ] 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 E2E test suite is parallelized and the `e2e_tests` job execution time is significantly reduced. - [ ] 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 details. - [ ] 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.2.0 milestone 2026-04-03 15:06:27 +00:00
Author
Owner

⚠️ Orphan Issue — Manual Linking Required

This issue was created without a known parent Epic. Per CONTRIBUTING.md, all non-Epic/non-Legendary issues must be linked to a parent Epic using Forgejo's dependency system (child blocks parent).

A maintainer must:

  1. Identify or create the appropriate parent Epic for CI/test infrastructure work.
  2. Open this issue and add the parent Epic under "blocks" (so this issue blocks the parent Epic).

This issue should not be moved beyond State/Unverified until the parent Epic link is established.


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

⚠️ **Orphan Issue — Manual Linking Required** This issue was created without a known parent Epic. Per `CONTRIBUTING.md`, all non-Epic/non-Legendary issues must be linked to a parent Epic using Forgejo's dependency system (child **blocks** parent). A maintainer must: 1. Identify or create the appropriate parent Epic for CI/test infrastructure work. 2. Open this issue and add the parent Epic under **"blocks"** (so this issue blocks the parent Epic). This issue should not be moved beyond `State/Unverified` until the parent Epic link is established. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
Author
Owner

Duplicate of #1961, #2278, #2322, and #2336.

This is the fifth issue requesting E2E test parallelization. All previous duplicates have been closed:

  • #1961 ("Parallelize E2E test execution in CI", v3.8.0) — the canonical issue
  • #2278 ("Parallelize E2E tests for faster execution", v3.8.0) — triaged
  • #2322 — closed as duplicate
  • #2336 — closed as duplicate

Closing as a duplicate.


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

**Duplicate of #1961, #2278, #2322, and #2336.** This is the fifth issue requesting E2E test parallelization. All previous duplicates have been closed: - #1961 ("Parallelize E2E test execution in CI", v3.8.0) — the canonical issue - #2278 ("Parallelize E2E tests for faster execution", v3.8.0) — triaged - #2322 — closed as duplicate - #2336 — closed as duplicate Closing as a duplicate. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
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.

Dependencies

No dependencies set.

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