TEST-INFRA: [test-architecture] Organize Behave feature files into subdirectories #5400

Open
opened 2026-04-09 06:24:05 +00:00 by HAL9000 · 2 comments
Owner

Metadata

  • Branch: refactor/organize-behave-feature-files-into-subdirectories
  • Commit Message: refactor(tests): organize Behave feature files into component subdirectories
  • Milestone: (none — backlog)
  • Parent Epic: (orphan — see note below)

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

Summary

The features/ directory currently has a flat structure, containing a large number of .feature files. This makes it difficult to navigate and understand the test suite's organization.

Proposed Solution

Organize the Behave feature files into subdirectories based on the component or feature they test. For example:

  • features/a2a/ — all features related to the a2a component
  • features/acms/ — all features related to the acms component
  • features/plan/ — all features related to plan lifecycle
  • features/projects/ — all features related to projects and resources
  • etc.

This change will make the test suite more modular, easier to navigate, and simpler to maintain.

Subtasks

  • Audit the current features/ directory and catalogue all .feature files by component
  • Define the target subdirectory structure based on the component/module layout in src/
  • Move .feature files into the appropriate subdirectories
  • Update any Behave environment.py or steps/ imports that reference specific feature file paths
  • Verify nox -e unit_tests passes after the reorganization
  • Verify nox -e coverage_report still meets the >=97% threshold

Definition of Done

  • All .feature files are organized into component-based subdirectories under features/
  • No .feature files remain at the top level of features/ (except any intentional top-level ones)
  • All nox stages pass (nox -e lint, nox -e typecheck, nox -e unit_tests, nox -e coverage_report)
  • Coverage >= 97%
  • The features/ directory structure mirrors the component layout in src/

⚠️ Orphan Issue: No parent Epic was found for test infrastructure improvements. This issue needs to be manually linked to an appropriate parent Epic. Please link it to a test infrastructure or testing quality Epic.


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

## Metadata - **Branch**: `refactor/organize-behave-feature-files-into-subdirectories` - **Commit Message**: `refactor(tests): organize Behave feature files into component subdirectories` - **Milestone**: *(none — backlog)* - **Parent Epic**: *(orphan — see note below)* > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.5.0. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. ## Summary The `features/` directory currently has a flat structure, containing a large number of `.feature` files. This makes it difficult to navigate and understand the test suite's organization. ## Proposed Solution Organize the Behave feature files into subdirectories based on the component or feature they test. For example: - `features/a2a/` — all features related to the `a2a` component - `features/acms/` — all features related to the `acms` component - `features/plan/` — all features related to plan lifecycle - `features/projects/` — all features related to projects and resources - etc. This change will make the test suite more modular, easier to navigate, and simpler to maintain. ## Subtasks - [ ] Audit the current `features/` directory and catalogue all `.feature` files by component - [ ] Define the target subdirectory structure based on the component/module layout in `src/` - [ ] Move `.feature` files into the appropriate subdirectories - [ ] Update any Behave `environment.py` or `steps/` imports that reference specific feature file paths - [ ] Verify `nox -e unit_tests` passes after the reorganization - [ ] Verify `nox -e coverage_report` still meets the >=97% threshold ## Definition of Done - [ ] All `.feature` files are organized into component-based subdirectories under `features/` - [ ] No `.feature` files remain at the top level of `features/` (except any intentional top-level ones) - [ ] All nox stages pass (`nox -e lint`, `nox -e typecheck`, `nox -e unit_tests`, `nox -e coverage_report`) - [ ] Coverage >= 97% - [ ] The `features/` directory structure mirrors the component layout in `src/` --- > ⚠️ **Orphan Issue:** No parent Epic was found for test infrastructure improvements. This issue needs to be manually linked to an appropriate parent Epic. Please link it to a test infrastructure or testing quality Epic. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: new-issue-creator
Author
Owner

Label compliance fix applied:

  • Added missing labels to bring issue into compliance with CONTRIBUTING.md

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Backlog — Organizing Behave feature files into subdirectories is a structural improvement that doesn't affect functionality. Low urgency.
  • Milestone: None (backlog)
  • Story Points: 2 — S — Reorganizing files and updating imports, 1-4 hours.
  • MoSCoW: MoSCoW/Could have — This is a nice-to-have organizational improvement. It improves navigability but doesn't affect test correctness or coverage.
  • Parent Epic: #5406 (Testing Infrastructure & Quality Hardening Legendary)

Valid test architecture improvement. Low priority but worth tracking.


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

Issue triaged by project owner: - **State**: Verified - **Priority**: Backlog — Organizing Behave feature files into subdirectories is a structural improvement that doesn't affect functionality. Low urgency. - **Milestone**: None (backlog) - **Story Points**: 2 — S — Reorganizing files and updating imports, 1-4 hours. - **MoSCoW**: MoSCoW/Could have — This is a nice-to-have organizational improvement. It improves navigability but doesn't affect test correctness or coverage. - **Parent Epic**: #5406 (Testing Infrastructure & Quality Hardening Legendary) Valid test architecture improvement. Low priority but worth tracking. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: 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#5400
No description provided.