TEST-INFRA: [test-data-quality] Improve test data for action names in action_cli.feature #5931

Open
opened 2026-04-09 11:55:04 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Branch: feat/test-infra/test-data-quality-action-cli-action-names
  • Commit Message: test(infra): improve test data for action names in action_cli.feature
  • Milestone: Backlog
  • Parent Epic: #5407

Description

The feature file features/action_cli.feature uses hardcoded and simplistic names for actions in its scenarios, such as "local/test-action" and "local/my-action". This limits the scope of testing and may not cover all possible edge cases, such as actions with special characters, long names, or unusual formats.

Improving the test data strategy for action names will make the test suite more robust and increase confidence that the action CLI handles a wider variety of inputs correctly.

Subtasks

  • Implement a data generation strategy for action names to be used in the feature file.
  • The strategy should generate a varied set of action names, including different lengths, special characters, and other variations.
  • Update the scenarios in features/action_cli.feature to use the generated data.

Definition of Done

  • The hardcoded action names in features/action_cli.feature are replaced with a more robust data generation strategy.
  • The tests continue to pass after the changes.
  • The new test data covers a wider range of scenarios.
  • All nox stages pass
  • Coverage >= 97%

Backlog note: This issue was discovered during autonomous operation
on milestone v3.6.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**: `feat/test-infra/test-data-quality-action-cli-action-names` - **Commit Message**: `test(infra): improve test data for action names in action_cli.feature` - **Milestone**: Backlog - **Parent Epic**: #5407 ## Description The feature file `features/action_cli.feature` uses hardcoded and simplistic names for actions in its scenarios, such as `"local/test-action"` and `"local/my-action"`. This limits the scope of testing and may not cover all possible edge cases, such as actions with special characters, long names, or unusual formats. Improving the test data strategy for action names will make the test suite more robust and increase confidence that the action CLI handles a wider variety of inputs correctly. ## Subtasks - [ ] Implement a data generation strategy for action names to be used in the feature file. - [ ] The strategy should generate a varied set of action names, including different lengths, special characters, and other variations. - [ ] Update the scenarios in `features/action_cli.feature` to use the generated data. ## Definition of Done - [ ] The hardcoded action names in `features/action_cli.feature` are replaced with a more robust data generation strategy. - [ ] The tests continue to pass after the changes. - [ ] The new test data covers a wider range of scenarios. - [ ] All nox stages pass - [ ] Coverage >= 97% > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.6.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
HAL9000 added this to the v3.8.0 milestone 2026-04-09 12:21:09 +00:00
Author
Owner

Label compliance fix applied:

  • Added missing labels and/or milestone 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 and/or milestone to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer
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#5931
No description provided.