TEST-INFRA: [test-architecture] Organize Robot Framework tests into subdirectories #1717

Open
opened 2026-04-02 23:34:23 +00:00 by freemo · 2 comments
Owner

Metadata

  • Branch: test/robot-framework-subdirectory-organization
  • Commit Message: test(test-architecture): organize robot framework tests into subdirectories
  • Milestone: v3.7.0
  • Parent Epic: (none identified — see orphan notice below)

Description

The Robot Framework tests in the robot/ directory are currently organized in a flat structure. This makes it difficult to find specific tests and to understand the overall structure of the test suite.

Per the project specification, integration tests must use Robot Framework and be located in the robot/ directory. The current flat layout does not reflect the modular architecture described in docs/specification.md, where each module under src/cleveragents/ should have a corresponding test subdirectory.

Note: This issue overlaps in scope with #1671 ("TEST-INFRA: [test-architecture] Reorganize feature and robot test files into subdirectories"), which also covers the robot/ directory. This issue focuses exclusively on the Robot Framework (robot/) side of that reorganization. If #1671 is already in progress, this issue may be resolved as a duplicate or absorbed into that work.

Subtasks

  • Audit all existing .robot files in robot/ and map each to its corresponding module in src/cleveragents/
  • Create subdirectories in robot/ for each major functional area / module (e.g., robot/acms/, robot/action/, robot/plan/, etc.)
  • Move existing Robot Framework test files into the appropriate subdirectories
  • Update noxfile.py (and any robot.cfg or equivalent runner configuration) to recursively discover tests in the new subdirectory structure
  • Verify all Robot Framework integration tests pass after the move: nox -e integration_tests
  • Verify linting passes: nox -e lint
  • Verify type checking passes: nox -e typecheck
  • Verify coverage remains ≥ 97%: nox -e coverage_report
  • Run nox (all default sessions) and fix any errors

Definition of Done

This issue is complete when:

  • The Robot Framework tests in robot/ are fully reorganized into subdirectories based on functional area / module, mirroring the structure of src/cleveragents/
  • The Robot Framework test runner (via nox -e integration_tests) recursively discovers and executes all tests in the new subdirectory structure without any tests being skipped or lost
  • All nox stages pass
  • Coverage ≥ 97%
  • 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

⚠️ Orphan Notice: No test-architecture Epic was found to serve as a parent for this issue. This issue must be manually linked to an appropriate parent Epic before work begins. Candidate parent: #1670 ("TEST-INFRA: [test-architecture] Reorganize test suite for modularity and clarity") — however that issue is labeled Type/Task, not Type/Epic. A new test-architecture Epic may need to be created, or this issue should be linked once one is available.


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

## Metadata - **Branch**: `test/robot-framework-subdirectory-organization` - **Commit Message**: `test(test-architecture): organize robot framework tests into subdirectories` - **Milestone**: v3.7.0 - **Parent Epic**: _(none identified — see orphan notice below)_ ## Description The Robot Framework tests in the `robot/` directory are currently organized in a flat structure. This makes it difficult to find specific tests and to understand the overall structure of the test suite. Per the project specification, integration tests must use Robot Framework and be located in the `robot/` directory. The current flat layout does not reflect the modular architecture described in `docs/specification.md`, where each module under `src/cleveragents/` should have a corresponding test subdirectory. > **Note:** This issue overlaps in scope with #1671 ("TEST-INFRA: [test-architecture] Reorganize feature and robot test files into subdirectories"), which also covers the `robot/` directory. This issue focuses exclusively on the Robot Framework (`robot/`) side of that reorganization. If #1671 is already in progress, this issue may be resolved as a duplicate or absorbed into that work. ## Subtasks - [ ] Audit all existing `.robot` files in `robot/` and map each to its corresponding module in `src/cleveragents/` - [ ] Create subdirectories in `robot/` for each major functional area / module (e.g., `robot/acms/`, `robot/action/`, `robot/plan/`, etc.) - [ ] Move existing Robot Framework test files into the appropriate subdirectories - [ ] Update `noxfile.py` (and any `robot.cfg` or equivalent runner configuration) to recursively discover tests in the new subdirectory structure - [ ] Verify all Robot Framework integration tests pass after the move: `nox -e integration_tests` - [ ] Verify linting passes: `nox -e lint` - [ ] Verify type checking passes: `nox -e typecheck` - [ ] Verify coverage remains ≥ 97%: `nox -e coverage_report` - [ ] Run `nox` (all default sessions) and fix any errors ## Definition of Done This issue is complete when: - [ ] The Robot Framework tests in `robot/` are fully reorganized into subdirectories based on functional area / module, mirroring the structure of `src/cleveragents/` - [ ] The Robot Framework test runner (via `nox -e integration_tests`) recursively discovers and executes all tests in the new subdirectory structure without any tests being skipped or lost - [ ] All nox stages pass - [ ] Coverage ≥ 97% - [ ] 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 --- > ⚠️ **Orphan Notice**: No test-architecture Epic was found to serve as a parent for this issue. This issue must be manually linked to an appropriate parent Epic before work begins. Candidate parent: #1670 ("TEST-INFRA: [test-architecture] Reorganize test suite for modularity and clarity") — however that issue is labeled `Type/Task`, not `Type/Epic`. A new test-architecture Epic may need to be created, or this issue should be linked once one is available. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
freemo added this to the v3.7.0 milestone 2026-04-02 23:34:52 +00:00
Author
Owner

⚠️ Orphan Issue — Manual Epic Linking Required

This issue was created without a parent Epic because no Type/Epic issue covering test architecture was found in the repository at the time of creation.

Recommended action: Link this issue to a parent Epic once one is available. Candidate options:

  • Create a new "Epic: Test Suite Architecture & Reorganization" Epic to serve as the parent for this and related issues (#1670, #1671).
  • Alternatively, if #1670 ("TEST-INFRA: [test-architecture] Reorganize test suite for modularity and clarity") is promoted to an Epic, link this issue to it.

Per CONTRIBUTING.md, orphan issues are not permitted. This must be resolved before work begins.


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

⚠️ **Orphan Issue — Manual Epic Linking Required** This issue was created without a parent Epic because no `Type/Epic` issue covering test architecture was found in the repository at the time of creation. **Recommended action:** Link this issue to a parent Epic once one is available. Candidate options: - Create a new **"Epic: Test Suite Architecture & Reorganization"** Epic to serve as the parent for this and related issues (#1670, #1671). - Alternatively, if #1670 ("TEST-INFRA: [test-architecture] Reorganize test suite for modularity and clarity") is promoted to an Epic, link this issue to it. Per `CONTRIBUTING.md`, orphan issues are not permitted. This must be resolved before work begins. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • MoSCoW: MoSCoW/Could Have — CI/test infrastructure improvement. Could Have.

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

Issue triaged by project owner: - **State**: Verified - **MoSCoW**: MoSCoW/Could Have — CI/test infrastructure improvement. Could Have. --- **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.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#1717
No description provided.