TEST-INFRA: [test-architecture] Organize Robot Framework test files into subdirectories #5415

Open
opened 2026-04-09 06:36:57 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Branch: refactor/test-infra/organize-robot-subdirectories
  • Commit Message: refactor(tests): organize robot framework test files into component subdirectories
  • Milestone: Backlog (no milestone — see backlog note below)
  • Parent Epic: #5407

Summary

The robot/ directory currently has a flat structure, containing a large number of .robot files. This makes it difficult to navigate and understand the integration test suite's organization.

Proposed Solution

Organize the Robot Framework test files into subdirectories based on the component or API they test. For example, all tests related to the a2a API could be moved to a robot/a2a/ subdirectory.

This change will make the integration test suite more modular, easier to navigate, and simpler to maintain.

Subtasks

  • Audit the existing robot/ directory and catalogue all .robot files by component
  • Define the target subdirectory structure (e.g., robot/a2a/, robot/acms/, robot/lsp/, etc.)
  • Move .robot files into their respective subdirectories
  • Update any robot.toml, pyproject.toml, or CI configuration that references specific robot file paths
  • Verify nox -e integration_tests still passes after reorganization
  • Update documentation or README references to the robot/ directory structure if applicable

Definition of Done

  • All .robot files are organized into component-based subdirectories under robot/
  • No .robot files remain at the top level of robot/ (except any intentional top-level suites)
  • nox -e integration_tests passes without modification to test logic
  • CI pipeline passes all stages
  • All nox stages pass
  • Coverage >= 97%

Backlog note: This issue was discovered during autonomous operation
on milestone Cross-cutting (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**: `refactor/test-infra/organize-robot-subdirectories` - **Commit Message**: `refactor(tests): organize robot framework test files into component subdirectories` - **Milestone**: Backlog (no milestone — see backlog note below) - **Parent Epic**: #5407 ## Summary The `robot/` directory currently has a flat structure, containing a large number of `.robot` files. This makes it difficult to navigate and understand the integration test suite's organization. ## Proposed Solution Organize the Robot Framework test files into subdirectories based on the component or API they test. For example, all tests related to the `a2a` API could be moved to a `robot/a2a/` subdirectory. This change will make the integration test suite more modular, easier to navigate, and simpler to maintain. ## Subtasks - [ ] Audit the existing `robot/` directory and catalogue all `.robot` files by component - [ ] Define the target subdirectory structure (e.g., `robot/a2a/`, `robot/acms/`, `robot/lsp/`, etc.) - [ ] Move `.robot` files into their respective subdirectories - [ ] Update any `robot.toml`, `pyproject.toml`, or CI configuration that references specific robot file paths - [ ] Verify `nox -e integration_tests` still passes after reorganization - [ ] Update documentation or README references to the `robot/` directory structure if applicable ## Definition of Done - [ ] All `.robot` files are organized into component-based subdirectories under `robot/` - [ ] No `.robot` files remain at the top level of `robot/` (except any intentional top-level suites) - [ ] `nox -e integration_tests` passes without modification to test logic - [ ] CI pipeline passes all stages - [ ] All nox stages pass - [ ] Coverage >= 97% > **Backlog note:** This issue was discovered during autonomous operation > on milestone Cross-cutting (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
Author
Owner

Label compliance fix applied:

  • Added missing labels: Type/Testing, Priority/Medium, State/Unverified
  • Reason: Issue had no labels at all. Type inferred from TEST-INFRA prefix. Priority/Medium is default. State/Unverified as this is a new issue.

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels: `Type/Testing`, `Priority/Medium`, `State/Unverified` - Reason: Issue had no labels at all. Type inferred from TEST-INFRA prefix. Priority/Medium is default. State/Unverified as this is a new issue. --- **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#5415
No description provided.