Organize Robot Framework test files into feature-based subdirectories #2028

Open
opened 2026-04-03 02:42:52 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: task/robot-test-subdirectory-organization
  • Commit Message: refactor(robot): organize Robot Framework test files into feature-based subdirectories
  • Milestone: v3.8.0
  • Parent Epic: #1678

Overview

The robot/ directory currently contains all Robot Framework integration test files (.robot), helper Python modules, and resource files in a single flat structure. As the test suite grows, this makes it increasingly difficult to navigate, understand test scope, and maintain related files together.

Currently the flat robot/ directory holds files spanning multiple distinct domains:

  • Plan lifecycle: plan_lifecycle_v3.robot, plan_phase_migration.robot
  • Providers: google_provider.robot, openai_provider.robot, provider_registry.robot
  • Tools: tool_runtime.robot, tool_lifecycle.robot, tool_builtins.robot
  • Domain models: domain_models.robot, db_lifecycle_models.robot
  • CLI / Actions: commands.robot, action_cli_spec.robot, action_schema.robot
  • Security: security_eval_removal.robot
  • Helpers / resources: helper_*.py, *.resource, filter_output.py, indentation_library.py

Grouping these into subdirectories by feature area will improve discoverability, reduce cognitive load when onboarding contributors, and align the integration test layout with the modular architecture described in the specification.

Subtasks

  • Audit all files in robot/ and assign each to a logical subdirectory (e.g., robot/plan/, robot/providers/, robot/tools/, robot/domain/, robot/cli/, robot/security/, robot/resources/)
  • Move .robot test files into their respective subdirectories
  • Move helper Python modules (helper_*.py, filter_output.py, indentation_library.py, json_helper.py) into a shared robot/resources/ or robot/helpers/ subdirectory
  • Move .resource files into robot/resources/
  • Update all Resource, Library, and Variables import paths within .robot and .resource files to reflect the new locations
  • Update noxfile.py (or equivalent) Robot Framework invocation paths if they reference specific files or directories
  • Verify nox -e integration_tests passes with the new layout
  • Update CONTRIBUTING.md or any developer documentation that references the robot/ directory structure

Definition of Done

  • All Robot Framework test files are organized into logical feature-based subdirectories under robot/
  • All intra-suite import paths (Resource, Library) are updated and resolve correctly
  • nox -e integration_tests passes with zero failures
  • All nox stages pass
  • Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: Unknown | Agent: ca-new-issue-creator

## Metadata - **Branch**: `task/robot-test-subdirectory-organization` - **Commit Message**: `refactor(robot): organize Robot Framework test files into feature-based subdirectories` - **Milestone**: v3.8.0 - **Parent Epic**: #1678 ## Overview The `robot/` directory currently contains all Robot Framework integration test files (`.robot`), helper Python modules, and resource files in a single flat structure. As the test suite grows, this makes it increasingly difficult to navigate, understand test scope, and maintain related files together. Currently the flat `robot/` directory holds files spanning multiple distinct domains: - **Plan lifecycle**: `plan_lifecycle_v3.robot`, `plan_phase_migration.robot` - **Providers**: `google_provider.robot`, `openai_provider.robot`, `provider_registry.robot` - **Tools**: `tool_runtime.robot`, `tool_lifecycle.robot`, `tool_builtins.robot` - **Domain models**: `domain_models.robot`, `db_lifecycle_models.robot` - **CLI / Actions**: `commands.robot`, `action_cli_spec.robot`, `action_schema.robot` - **Security**: `security_eval_removal.robot` - **Helpers / resources**: `helper_*.py`, `*.resource`, `filter_output.py`, `indentation_library.py` Grouping these into subdirectories by feature area will improve discoverability, reduce cognitive load when onboarding contributors, and align the integration test layout with the modular architecture described in the specification. ## Subtasks - [ ] Audit all files in `robot/` and assign each to a logical subdirectory (e.g., `robot/plan/`, `robot/providers/`, `robot/tools/`, `robot/domain/`, `robot/cli/`, `robot/security/`, `robot/resources/`) - [ ] Move `.robot` test files into their respective subdirectories - [ ] Move helper Python modules (`helper_*.py`, `filter_output.py`, `indentation_library.py`, `json_helper.py`) into a shared `robot/resources/` or `robot/helpers/` subdirectory - [ ] Move `.resource` files into `robot/resources/` - [ ] Update all `Resource`, `Library`, and `Variables` import paths within `.robot` and `.resource` files to reflect the new locations - [ ] Update `noxfile.py` (or equivalent) Robot Framework invocation paths if they reference specific files or directories - [ ] Verify `nox -e integration_tests` passes with the new layout - [ ] Update `CONTRIBUTING.md` or any developer documentation that references the `robot/` directory structure ## Definition of Done - [ ] All Robot Framework test files are organized into logical feature-based subdirectories under `robot/` - [ ] All intra-suite import paths (`Resource`, `Library`) are updated and resolve correctly - [ ] `nox -e integration_tests` passes with zero failures - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Unknown | Agent: ca-new-issue-creator
freemo added this to the v3.8.0 milestone 2026-04-03 02:42:56 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Backlog (confirmed)
  • Milestone: v3.8.0 (confirmed — test infrastructure)
  • MoSCoW: Could Have — Reorganizing Robot Framework test files into subdirectories is a pure refactoring task with no behavioral change. Improves maintainability but is not urgent.
  • Parent Epic: #1678 (confirmed correct)

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Backlog (confirmed) - **Milestone**: v3.8.0 (confirmed — test infrastructure) - **MoSCoW**: Could Have — Reorganizing Robot Framework test files into subdirectories is a pure refactoring task with no behavioral change. Improves maintainability but is not urgent. - **Parent Epic**: #1678 (confirmed correct) --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-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#2028
No description provided.