TEST-INFRA: [test-architecture] Organize ASV benchmark files into subdirectories #6909

New issue

Open

opened 2026-04-10 05:03:24 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-10 05:03:24 +00:00

Owner

Metadata

Branch: refactor/test-infra/organize-asv-benchmark-subdirectories
Commit Message: refactor(benchmarks): organize ASV benchmark files into logical subdirectories
Milestone: Backlog (no milestone — see backlog note below)
Parent Epic: #5407

Summary

The benchmarks/ directory contains a large number of ASV benchmark files (_bench.py) in a flat structure. This makes it difficult to navigate, maintain, and understand the performance testing suite.

Duplicate Check

Search queries: "organize asv", "asv subdirectories", "structure benchmark files"
Results: 0 relevant issues found.

Proposal

Create subdirectories within benchmarks/ to group related benchmark files by the component they are testing.

Example Structure:

benchmarks/
├── cli/
│   ├── cli_benchmark.py
│   ├── cli_core_bench.py
│   └── ...
├── core/
│   ├── component_resolver_bench.py
│   ├── concurrency_lock_bench.py
│   └── ...
├── plans/
│   ├── plan_actor_integration_bench.py
│   ├── plan_cli_bench.py
│   └── ...
└── skills/
    ├── skill_add_persist_bench.py
    ├── skill_cli_bench.py
    └── ...

Subtasks

Identify logical groupings for existing benchmark files.
Create new subdirectories in benchmarks/ based on these groupings.
Move the benchmark files into their respective subdirectories.
Update any necessary paths in the ASV configuration (asv.conf.json).

Definition of Done

All benchmark files in benchmarks/ are organized into logical subdirectories.
The ASV benchmark suite runs successfully after the reorganization (nox -s benchmark).
The project's testing documentation is updated to reflect the new structure.
All nox stages pass.
Coverage >= 97%.

Backlog note: This issue was discovered during autonomous operation
on milestone v3.2.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**: `refactor/test-infra/organize-asv-benchmark-subdirectories` - **Commit Message**: `refactor(benchmarks): organize ASV benchmark files into logical subdirectories` - **Milestone**: Backlog (no milestone — see backlog note below) - **Parent Epic**: #5407 ## Summary The `benchmarks/` directory contains a large number of ASV benchmark files (`_bench.py`) in a flat structure. This makes it difficult to navigate, maintain, and understand the performance testing suite. ### Duplicate Check - Search queries: "organize asv", "asv subdirectories", "structure benchmark files" - Results: 0 relevant issues found. ## Proposal Create subdirectories within `benchmarks/` to group related benchmark files by the component they are testing. **Example Structure:** ``` benchmarks/ ├── cli/ │ ├── cli_benchmark.py │ ├── cli_core_bench.py │ └── ... ├── core/ │ ├── component_resolver_bench.py │ ├── concurrency_lock_bench.py │ └── ... ├── plans/ │ ├── plan_actor_integration_bench.py │ ├── plan_cli_bench.py │ └── ... └── skills/ ├── skill_add_persist_bench.py ├── skill_cli_bench.py └── ... ``` ## Subtasks - [ ] Identify logical groupings for existing benchmark files. - [ ] Create new subdirectories in `benchmarks/` based on these groupings. - [ ] Move the benchmark files into their respective subdirectories. - [ ] Update any necessary paths in the ASV configuration (`asv.conf.json`). ## Definition of Done - [ ] All benchmark files in `benchmarks/` are organized into logical subdirectories. - [ ] The ASV benchmark suite runs successfully after the reorganization (`nox -s benchmark`). - [ ] The project's testing documentation is updated to reflect the new structure. - [ ] All nox stages pass. - [ ] Coverage >= 97%. > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.2.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