TEST-INFRA: [test-architecture] Missing step definition files for Behave features #5718

Open
opened 2026-04-09 08:48:08 +00:00 by HAL9000 · 0 comments
Owner

Metadata

  • Branch: feat/test-infra/test-architecture-step-definition-files
  • Commit Message: test(infra): add missing step definition files for Behave feature files
  • Milestone: Backlog
  • Parent Epic: #5407

Background and context

The CONTRIBUTING.md file states that 'Steps used only by a particular feature file should live in a correspondingly named step definition file.'

Current behavior

A large number of Behave feature files in the features/ directory do not have a corresponding step definition file. This makes it difficult to maintain the tests and violates the project's BDD guidelines.

Duplicate Check

  • Search queries: 'test architecture', 'BDD', 'step file'
  • Results: 0
  • None of the existing issues cover this specific finding.

Expected behavior

Every .feature file should have a corresponding _steps.py file that contains the step definitions for that feature.

Subtasks

  • Identify all .feature files that are missing a corresponding _steps.py file.
  • Create a new _steps.py file for each of these feature files.
  • Move the relevant step definitions from other files into the new step files.

Definition of Done

  • All subtasks above are completed and checked off.
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
  • All nox stages pass.
  • Coverage >= 97%.

Backlog note: This issue was discovered during autonomous operation
on milestone Test Infrastructure. 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**: `feat/test-infra/test-architecture-step-definition-files` - **Commit Message**: `test(infra): add missing step definition files for Behave feature files` - **Milestone**: Backlog - **Parent Epic**: #5407 ## Background and context The `CONTRIBUTING.md` file states that 'Steps used only by a particular feature file should live in a correspondingly named step definition file.' ## Current behavior A large number of Behave feature files in the `features/` directory do not have a corresponding step definition file. This makes it difficult to maintain the tests and violates the project's BDD guidelines. ### Duplicate Check - Search queries: 'test architecture', 'BDD', 'step file' - Results: 0 - None of the existing issues cover this specific finding. ## Expected behavior Every `.feature` file should have a corresponding `_steps.py` file that contains the step definitions for that feature. ## Subtasks - [ ] Identify all `.feature` files that are missing a corresponding `_steps.py` file. - [ ] Create a new `_steps.py` file for each of these feature files. - [ ] Move the relevant step definitions from other files into the new step files. ## Definition of Done - [ ] All subtasks above are completed and checked off. - [ ] A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - [ ] The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - [ ] The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. - [ ] All nox stages pass. - [ ] Coverage >= 97%. > **Backlog note:** This issue was discovered during autonomous operation > on milestone Test Infrastructure. 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
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#5718
No description provided.