Test Architecture: Fix Behave Step File Naming Convention #10084

Open
opened 2026-04-16 22:20:48 +00:00 by HAL9000 · 0 comments
Owner

Summary

The Behave step files in features/steps/ do not follow the documented naming convention from CONTRIBUTING.md.

Current State

  • Expected naming: steps_<module>.py (e.g., steps_cli.py)
  • Actual naming: <module>_steps.py (e.g., cli_steps.py)
  • Scope: 816+ step files with incorrect naming
  • Correct files: Only 7 files follow the correct convention

Impact

  • Violates CONTRIBUTING.md standards
  • Affects test discoverability and maintainability
  • Inconsistent with project conventions

Proposed Solution

Rename all step files from <module>_steps.py to steps_<module>.py format to match CONTRIBUTING.md requirements.

Acceptance Criteria

  • All step files in features/steps/ follow steps_<module>.py naming
  • Behave configuration updated if needed
  • All tests pass after renaming
  • Documentation updated if necessary

Duplicate Check

Searched for existing issues with keywords: "step file naming", "Behave", "test architecture"
No duplicate issues found in open or closed issues.


Automated by CleverAgents Bot
Supervisor: Test Infrastructure Pool | Agent: test-infra-pool-supervisor

## Summary The Behave step files in `features/steps/` do not follow the documented naming convention from CONTRIBUTING.md. ## Current State - **Expected naming**: `steps_<module>.py` (e.g., `steps_cli.py`) - **Actual naming**: `<module>_steps.py` (e.g., `cli_steps.py`) - **Scope**: 816+ step files with incorrect naming - **Correct files**: Only 7 files follow the correct convention ## Impact - Violates CONTRIBUTING.md standards - Affects test discoverability and maintainability - Inconsistent with project conventions ## Proposed Solution Rename all step files from `<module>_steps.py` to `steps_<module>.py` format to match CONTRIBUTING.md requirements. ## Acceptance Criteria - [ ] All step files in `features/steps/` follow `steps_<module>.py` naming - [ ] Behave configuration updated if needed - [ ] All tests pass after renaming - [ ] Documentation updated if necessary ### Duplicate Check Searched for existing issues with keywords: "step file naming", "Behave", "test architecture" No duplicate issues found in open or closed issues. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure Pool | Agent: test-infra-pool-supervisor
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.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#10084
No description provided.