TEST-INFRA: [ci-execution-time] Parallelize Behave unit test suite #5749

New issue

Open

opened 2026-04-09 09:03:59 +00:00 by HAL9000 · 0 comments

HAL9000 commented

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

Owner

Metadata

Branch: test-infra/parallelize-behave-unit-tests
Commit Message: perf(ci): parallelize Behave unit test suite to eliminate nox unit_tests timeout
Milestone: (backlog — see note below)
Parent Epic: #5407

Summary

The nox -e unit_tests session is consistently timing out after 30 minutes in CI. This is a major bottleneck in the development workflow and needs to be addressed.

Problem

The Behave test suite is running sequentially, which is not scalable as the number of tests grows. The current execution time exceeds the CI timeout, preventing PRs from being merged.

Proposed Solution

Implement parallel execution for the Behave test suite. This can be achieved by using tools like behave-parallel or by sharding the feature files and running them on multiple runners.

Subtasks

Research and choose a parallel execution strategy for Behave (e.g., behave-parallel, feature file sharding, or multiple CI runners).
Implement the chosen strategy in the noxfile.py.
Update the CI workflow to use the new parallel execution.
Monitor the execution time of the unit_tests session to ensure it is within acceptable limits.

Definition of Done

The unit_tests session completes successfully in CI without timing out.
The execution time of the unit_tests session is significantly reduced.
All nox stages pass (nox -e lint, nox -e typecheck, nox -e unit_tests, nox -e integration_tests).
Coverage >= 97% (nox -e coverage_report).
PR is merged and linked issue is closed.

Duplicate Check

Search queries: behave parallel, parallelize unit tests, unit_tests timeout, ci-execution-time
Related issue: #5662 covers Robot Framework parallel execution — this issue is distinct, covering the Behave unit test suite.
No existing issues found that address the parallelization of the Behave unit test suite.

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

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

## Metadata - **Branch**: `test-infra/parallelize-behave-unit-tests` - **Commit Message**: `perf(ci): parallelize Behave unit test suite to eliminate nox unit_tests timeout` - **Milestone**: *(backlog — see note below)* - **Parent Epic**: #5407 ## Summary The `nox -e unit_tests` session is consistently timing out after 30 minutes in CI. This is a major bottleneck in the development workflow and needs to be addressed. ## Problem The Behave test suite is running sequentially, which is not scalable as the number of tests grows. The current execution time exceeds the CI timeout, preventing PRs from being merged. ## Proposed Solution Implement parallel execution for the Behave test suite. This can be achieved by using tools like `behave-parallel` or by sharding the feature files and running them on multiple runners. ## Subtasks - [ ] Research and choose a parallel execution strategy for Behave (e.g., `behave-parallel`, feature file sharding, or multiple CI runners). - [ ] Implement the chosen strategy in the `noxfile.py`. - [ ] Update the CI workflow to use the new parallel execution. - [ ] Monitor the execution time of the `unit_tests` session to ensure it is within acceptable limits. ## Definition of Done - [ ] The `unit_tests` session completes successfully in CI without timing out. - [ ] The execution time of the `unit_tests` session is significantly reduced. - [ ] All nox stages pass (`nox -e lint`, `nox -e typecheck`, `nox -e unit_tests`, `nox -e integration_tests`). - [ ] Coverage >= 97% (`nox -e coverage_report`). - [ ] PR is merged and linked issue is closed. ## Duplicate Check - Search queries: `behave parallel`, `parallelize unit tests`, `unit_tests timeout`, `ci-execution-time` - Related issue: #5662 covers Robot Framework parallel execution — this issue is distinct, covering the Behave unit test suite. - No existing issues found that address the parallelization of the Behave unit test suite. > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.7.0. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: new-issue-creator

Rows
Columns