TEST-INFRA: [ci-execution-time] Investigate and optimize long-running E2E tests #2273

Closed
opened 2026-04-03 12:31:03 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: task/ci-execution-time-optimize-e2e-tests
  • Commit Message: perf(ci): investigate and optimize long-running E2E tests to reduce pipeline feedback time
  • Milestone: v3.8.0
  • Parent Epic: #1678

Description

The e2e_tests job in the CI pipeline has a timeout of 45 minutes, which indicates a significant performance bottleneck. This long execution time increases the feedback loop for developers and consumes a large amount of CI resources.

Analysis

The CI configuration file (.forgejo/workflows/ci.yml) defines the e2e_tests job with a timeout-minutes: 45. This suggests that the end-to-end test suite is either very large, contains inefficient tests, or has other performance issues.

Subtasks

  • Profile the E2E test suite to identify the slowest tests.
  • Investigate the cause of the long execution time for the identified tests.
  • Explore options for optimizing the E2E tests, such as:
    • Splitting the test suite into smaller, parallelizable chunks.
    • Improving test data setup and teardown.
    • Optimizing test logic and assertions.
    • Identifying and removing redundant or unnecessary tests.

Definition of Done

  • The execution time of the e2e_tests job is significantly reduced (e.g., under 15 minutes).
  • The E2E test suite is optimized for performance without compromising test coverage.
  • The changes are documented and communicated to the team.
  • All nox stages pass
  • Coverage >= 97%

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

## Metadata - **Branch**: `task/ci-execution-time-optimize-e2e-tests` - **Commit Message**: `perf(ci): investigate and optimize long-running E2E tests to reduce pipeline feedback time` - **Milestone**: v3.8.0 - **Parent Epic**: #1678 ## Description The `e2e_tests` job in the CI pipeline has a timeout of 45 minutes, which indicates a significant performance bottleneck. This long execution time increases the feedback loop for developers and consumes a large amount of CI resources. ## Analysis The CI configuration file (`.forgejo/workflows/ci.yml`) defines the `e2e_tests` job with a `timeout-minutes: 45`. This suggests that the end-to-end test suite is either very large, contains inefficient tests, or has other performance issues. ## Subtasks - [ ] Profile the E2E test suite to identify the slowest tests. - [ ] Investigate the cause of the long execution time for the identified tests. - [ ] Explore options for optimizing the E2E tests, such as: - Splitting the test suite into smaller, parallelizable chunks. - Improving test data setup and teardown. - Optimizing test logic and assertions. - Identifying and removing redundant or unnecessary tests. ## Definition of Done - [ ] The execution time of the `e2e_tests` job is significantly reduced (e.g., under 15 minutes). - [ ] The E2E test suite is optimized for performance without compromising test coverage. - [ ] The changes are documented and communicated to the team. - [ ] 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 12:32:40 +00:00
Author
Owner

Closing as duplicate of #2336.

This issue ("Investigate and optimize long-running E2E tests") covers the same scope as #2336 ("Parallelize E2E tests using pabot"). Consolidating to avoid duplicate work.


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

Closing as duplicate of #2336. This issue ("Investigate and optimize long-running E2E tests") covers the same scope as #2336 ("Parallelize E2E tests using pabot"). Consolidating to avoid duplicate work. --- **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.

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