TEST-INFRA: [test-architecture] Reorganize feature and robot test files into subdirectories #1671

New issue

Open

opened 2026-04-02 23:27:16 +00:00 by freemo · 1 comment

freemo commented

2026-04-02 23:27:16 +00:00

Owner

Metadata

Branch: test/reorganize-test-files-into-subdirectories
Commit Message: test(test-architecture): reorganize feature and robot test files into subdirectories
Milestone: v3.7.0
Parent Epic: (see orphan notice below — needs manual linking)

Description

The features/ and robot/ directories contain a large number of test files at the top level. This makes it difficult to navigate and maintain the test suite. To improve the organization, subdirectories should be created based on the prefixes of the file names.

For example, in the features/ directory, all files prefixed with acms_ could be moved to an acms/ subdirectory. Similarly, all files prefixed with action_ could be moved to an action/ subdirectory, and so on. The same logic applies to the robot/ directory.

This change will make it easier to find and maintain tests, and it will improve the overall organization of the test suite.

Subtasks

Audit all files in features/ and group them by prefix/module.
Create subdirectories in features/ for each major feature/module group.
Move existing feature files into the appropriate features/ subdirectories.
Audit all files in robot/ and group them by prefix/module.
Create subdirectories in robot/ for each major feature/module group.
Move existing robot files into the appropriate robot/ subdirectories.
Update noxfile.py and any test runner configuration to discover tests in the new subdirectory structure.
Verify all Behave step definitions resolve correctly after the move.
Verify all Robot Framework test suites execute correctly after the move.

Definition of Done

The features/ and robot/ directories are fully reorganized into subdirectories by module/feature prefix.
All Behave unit tests pass (nox -e unit_tests).
All Robot Framework integration tests pass (nox -e integration_tests).
Linting passes (nox -e lint).
Type checking passes (nox -e typecheck).
All nox stages pass.
Coverage >= 97%.
The commit is pushed to test/reorganize-test-files-into-subdirectories with the prescribed commit message.
The PR is merged.

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

## Metadata - **Branch**: `test/reorganize-test-files-into-subdirectories` - **Commit Message**: `test(test-architecture): reorganize feature and robot test files into subdirectories` - **Milestone**: v3.7.0 - **Parent Epic**: _(see orphan notice below — needs manual linking)_ ## Description The `features/` and `robot/` directories contain a large number of test files at the top level. This makes it difficult to navigate and maintain the test suite. To improve the organization, subdirectories should be created based on the prefixes of the file names. For example, in the `features/` directory, all files prefixed with `acms_` could be moved to an `acms/` subdirectory. Similarly, all files prefixed with `action_` could be moved to an `action/` subdirectory, and so on. The same logic applies to the `robot/` directory. This change will make it easier to find and maintain tests, and it will improve the overall organization of the test suite. ## Subtasks - [ ] Audit all files in `features/` and group them by prefix/module. - [ ] Create subdirectories in `features/` for each major feature/module group. - [ ] Move existing feature files into the appropriate `features/` subdirectories. - [ ] Audit all files in `robot/` and group them by prefix/module. - [ ] Create subdirectories in `robot/` for each major feature/module group. - [ ] Move existing robot files into the appropriate `robot/` subdirectories. - [ ] Update `noxfile.py` and any test runner configuration to discover tests in the new subdirectory structure. - [ ] Verify all Behave step definitions resolve correctly after the move. - [ ] Verify all Robot Framework test suites execute correctly after the move. ## Definition of Done - [ ] The `features/` and `robot/` directories are fully reorganized into subdirectories by module/feature prefix. - [ ] All Behave unit tests pass (`nox -e unit_tests`). - [ ] All Robot Framework integration tests pass (`nox -e integration_tests`). - [ ] Linting passes (`nox -e lint`). - [ ] Type checking passes (`nox -e typecheck`). - [ ] All nox stages pass. - [ ] Coverage >= 97%. - [ ] The commit is pushed to `test/reorganize-test-files-into-subdirectories` with the prescribed commit message. - [ ] The PR is merged. --- **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:28:55 +00:00

freemo commented

2026-04-02 23:29:37 +00:00

Author

Owner

⚠️ Orphan Issue — Manual Epic Linking Required

This issue was created without a parent Epic because no existing test-architecture Epic was found in the repository. Per CONTRIBUTING.md, orphan issues are not permitted — every issue must be linked to a parent Epic using Forgejo's dependency system (child blocks parent).

Action required: A project maintainer must either:

Identify or create a suitable parent Epic for test file reorganization / test architecture work, and then link this issue as a dependency (this issue blocks the parent Epic), or
Create a new TEST-INFRA: [test-architecture] Epic and link this issue to it.

Once the parent Epic is identified, run:

curl -s -X POST "https://git.cleverthis.com/api/v1/repos/cleveragents/cleveragents-core/issues/1671/blocks" \
  -H "Authorization: token <FORGEJO_PAT>" \
  -H "Content-Type: application/json" \
  -d '{"dependency_id": <PARENT_EPIC_NUMBER>}'

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 existing `test-architecture` Epic was found in the repository. Per `CONTRIBUTING.md`, orphan issues are **not permitted** — every issue must be linked to a parent Epic using Forgejo's dependency system (child **blocks** parent). **Action required:** A project maintainer must either: 1. Identify or create a suitable parent Epic for test file reorganization / test architecture work, and then link this issue as a dependency (this issue **blocks** the parent Epic), or 2. Create a new `TEST-INFRA: [test-architecture]` Epic and link this issue to it. Once the parent Epic is identified, run: ```bash curl -s -X POST "https://git.cleverthis.com/api/v1/repos/cleveragents/cleveragents-core/issues/1671/blocks" \ -H "Authorization: token <FORGEJO_PAT>" \ -H "Content-Type: application/json" \ -d '{"dependency_id": <PARENT_EPIC_NUMBER>}' ``` --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

freemo referenced this issue

2026-04-02 23:34:23 +00:00

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

freemo referenced this issue

2026-04-02 23:37:09 +00:00

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

freemo referenced this issue

2026-04-03 09:37:21 +00:00

TEST-INFRA: [test-architecture] Organize helper files in robot directory #2220