TEST-INFRA: [ci-execution-time] Optimize the coverage_report session #4435

New issue

Open

opened 2026-04-08 12:35:33 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-08 12:35:33 +00:00

Owner

Metadata

Branch: task/ci-execution-time-optimize-coverage-report
Commit Message: perf(ci): optimize coverage_report nox session with parallel test execution
Milestone: v3.8.0
Parent Epic: #1678

Overview

The coverage_report nox session runs all the Behave tests sequentially to generate a coverage report. This is necessary to get an accurate report, but it is also one of the slowest parts of the CI pipeline.

This proposal suggests investigating ways to optimize the coverage_report session. One possible approach is to run the tests in parallel and then merge the coverage reports from the parallel runs. The slipcover tool is used for coverage, and it might have options to support this workflow.

Subtasks

Research how to generate a combined coverage report from parallel test runs using slipcover.
Update the coverage_report nox session to run the tests in parallel.
Ensure that the generated coverage report is accurate and that the coverage threshold is still enforced correctly.

Definition of Done

The coverage_report session runs the tests in parallel.
The total execution time of the coverage_report session is significantly reduced.
The generated coverage report is accurate and complete.
The coverage threshold is still enforced correctly.
All nox stages pass.
Coverage >= 97%.

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

## Metadata - **Branch**: `task/ci-execution-time-optimize-coverage-report` - **Commit Message**: `perf(ci): optimize coverage_report nox session with parallel test execution` - **Milestone**: v3.8.0 - **Parent Epic**: #1678 ## Overview The `coverage_report` nox session runs all the Behave tests sequentially to generate a coverage report. This is necessary to get an accurate report, but it is also one of the slowest parts of the CI pipeline. This proposal suggests investigating ways to optimize the `coverage_report` session. One possible approach is to run the tests in parallel and then merge the coverage reports from the parallel runs. The `slipcover` tool is used for coverage, and it might have options to support this workflow. ## Subtasks - [ ] Research how to generate a combined coverage report from parallel test runs using `slipcover`. - [ ] Update the `coverage_report` nox session to run the tests in parallel. - [ ] Ensure that the generated coverage report is accurate and that the coverage threshold is still enforced correctly. ## Definition of Done - [ ] The `coverage_report` session runs the tests in parallel. - [ ] The total execution time of the `coverage_report` session is significantly reduced. - [ ] The generated coverage report is accurate and complete. - [ ] The coverage threshold is still enforced correctly. - [ ] All nox stages pass. - [ ] Coverage >= 97%. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: new-issue-creator

Rows
Columns