TEST-INFRA: [test-data-quality] Improve test data for action and actor names in Robot helper scripts #6114

Open
opened 2026-04-09 14:53:58 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Branch: test/infra/test-data-quality-robot-helper-action-actor-names
  • Commit Message: test(infra): improve test data for action and actor names in Robot helper scripts
  • Milestone: Backlog
  • Parent Epic: #5407

Description

The Robot Framework helper scripts robot/helper_action_cli_spec.py and robot/helper_actor_cli_show.py use hardcoded and simplistic names for actions and actors in their tests. For example, "local/smoke-action" and "local/robot-actor". This limits the scope of testing and may not cover all possible edge cases.

Subtasks

  • Implement a data generation strategy for action and actor names to be used in the helper scripts.
  • The strategy should generate a varied set of names, including different lengths, special characters, and other variations.
  • Alternatively, implement a data-driven approach where the test data is read from a separate file (e.g., a JSON or YAML file).
  • Update the tests in the helper scripts to use the generated or data-driven data.

Definition of Done

  • The hardcoded action and actor names in the helper scripts are replaced with a more robust data generation or data-driven 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.7.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**: `test/infra/test-data-quality-robot-helper-action-actor-names` - **Commit Message**: `test(infra): improve test data for action and actor names in Robot helper scripts` - **Milestone**: Backlog - **Parent Epic**: #5407 ## Description The Robot Framework helper scripts `robot/helper_action_cli_spec.py` and `robot/helper_actor_cli_show.py` use hardcoded and simplistic names for actions and actors in their tests. For example, `"local/smoke-action"` and `"local/robot-actor"`. This limits the scope of testing and may not cover all possible edge cases. ## Subtasks - [ ] Implement a data generation strategy for action and actor names to be used in the helper scripts. - [ ] The strategy should generate a varied set of names, including different lengths, special characters, and other variations. - [ ] Alternatively, implement a data-driven approach where the test data is read from a separate file (e.g., a JSON or YAML file). - [ ] Update the tests in the helper scripts to use the generated or data-driven data. ## Definition of Done - [ ] The hardcoded action and actor names in the helper scripts are replaced with a more robust data generation or data-driven 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.7.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 15:32:06 +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#6114
No description provided.