TEST-INFRA: [ci-execution-time] Optimize integration test setup and execution #2303

New issue

Closed

opened 2026-04-03 13:26:10 +00:00 by freemo · 2 comments

freemo commented

2026-04-03 13:26:10 +00:00

Owner

Metadata

Branch: test/m3-optimize-integration-test-setup
Commit Message: test(ci): optimize integration test setup and execution for faster CI
Milestone: v3.8.0
Parent Epic: #1678

Background and Context

The integration test suite may be contributing to slow CI times due to inefficient setup of external services or a lack of parallelization. Identifying and addressing these bottlenecks will improve developer feedback loops and overall pipeline throughput.

Expected Behavior

Integration tests should set up external service dependencies efficiently (leveraging caching where possible), execute in parallel where feasible, and be organized into smaller, independently runnable suites — resulting in a measurably faster integration_tests CI job.

Acceptance Criteria

The setup time for integration tests is reduced by eliminating redundant or slow initialization steps.
External service dependencies (e.g., database images, microservices) are cached between CI runs where possible.
Integration tests run in parallel (or are split into independent sub-suites) where the test design permits.
The overall execution time of the integration_tests job is measurably improved.
The CI pipeline remains stable and reliable with no flaky test failures introduced by the changes.

Subtasks

Analyze the setup process for the integration tests to identify bottlenecks (e.g., slow service startup, redundant initialization).
Investigate and implement caching for external service dependencies (e.g., database images, other microservices).
Evaluate feasibility of parallel execution or test splitting for the integration test suite.
Update .forgejo/workflows/ci.yml to run integration tests in parallel or across split suites, if applicable.
Monitor and measure the performance impact of the optimizations against the baseline.
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.
A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly (test(ci): optimize integration test setup and execution for faster CI), 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 (test/m3-optimize-integration-test-setup).
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/m3-optimize-integration-test-setup` - **Commit Message**: `test(ci): optimize integration test setup and execution for faster CI` - **Milestone**: v3.8.0 - **Parent Epic**: #1678 ## Background and Context The integration test suite may be contributing to slow CI times due to inefficient setup of external services or a lack of parallelization. Identifying and addressing these bottlenecks will improve developer feedback loops and overall pipeline throughput. ## Expected Behavior Integration tests should set up external service dependencies efficiently (leveraging caching where possible), execute in parallel where feasible, and be organized into smaller, independently runnable suites — resulting in a measurably faster `integration_tests` CI job. ## Acceptance Criteria - The setup time for integration tests is reduced by eliminating redundant or slow initialization steps. - External service dependencies (e.g., database images, microservices) are cached between CI runs where possible. - Integration tests run in parallel (or are split into independent sub-suites) where the test design permits. - The overall execution time of the `integration_tests` job is measurably improved. - The CI pipeline remains stable and reliable with no flaky test failures introduced by the changes. ## Subtasks - [ ] Analyze the setup process for the integration tests to identify bottlenecks (e.g., slow service startup, redundant initialization). - [ ] Investigate and implement caching for external service dependencies (e.g., database images, other microservices). - [ ] Evaluate feasibility of parallel execution or test splitting for the integration test suite. - [ ] Update `.forgejo/workflows/ci.yml` to run integration tests in parallel or across split suites, if applicable. - [ ] Monitor and measure the performance impact of the optimizations against the baseline. - [ ] 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. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly (`test(ci): optimize integration test setup and execution for faster CI`), 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 (`test/m3-optimize-integration-test-setup`). - 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 13:26:25 +00:00

freemo commented

2026-04-03 13:27:45 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Medium (confirmed)
Milestone: v3.8.0 (confirmed — CI infrastructure)
MoSCoW: Could Have — Integration test optimization is a CI performance improvement. Not blocking any deliverables.
Parent Epic: #1678 (confirmed correct)

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Medium (confirmed) - **Milestone**: v3.8.0 (confirmed — CI infrastructure) - **MoSCoW**: Could Have — Integration test optimization is a CI performance improvement. Not blocking any deliverables. - **Parent Epic**: #1678 (confirmed correct) --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner

freemo added the

MoSCoW

Could have

label

2026-04-03 13:27:47 +00:00

freemo added a new dependency

2026-04-03 13:42:25 +00:00

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

freemo commented

2026-04-03 17:23:35 +00:00

Author

Owner

Closing as duplicate of #2315.

This issue ("Optimize integration test setup and execution") covers the same scope as #2315 ("Investigate and optimize slow integration_tests suite (22m+ runtime)"). Consolidating to avoid duplicate work.

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

Closing as duplicate of #2315. This issue ("Optimize integration test setup and execution") covers the same scope as #2315 ("Investigate and optimize slow integration_tests suite (22m+ runtime)"). Consolidating to avoid duplicate work. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner

freemo closed this issue

2026-04-03 17:23:58 +00:00

freemo referenced this issue

2026-04-03 17:24:36 +00:00

TEST-INFRA: [ci-execution-time] Investigate and optimize slow integration_tests suite (22m+ runtime) #2315