TEST-INFRA: [missing-test-levels] Add Robot integration tests for the infrastructure module #3767

Open
opened 2026-04-05 22:34:27 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: test/missing-test-levels-infrastructure-robot-integration-tests
  • Commit Message: test(infrastructure): add Robot Framework integration tests for the infrastructure module
  • Milestone: (none — backlog)
  • Parent Epic: #1678

Backlog note: This issue was discovered during autonomous operation
on milestone Test Infrastructure. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.

Background and Context

The infrastructure module in src/cleveragents/infrastructure is missing Robot Framework integration tests. Per the project testing strategy, every module must have integration tests written using the Robot Framework, located under the robot/ directory. Integration tests must exercise the module against real services and dependencies — mocks are not permitted in Robot tests.

The infrastructure module provides the foundational runtime layer of the CleverAgents platform, including the LSP Runtime (which manages language server lifecycles, workspace mapping, and file synchronisation) and other infrastructure-level concerns. Without integration test coverage at the Robot Framework level, regressions in LSP server startup, workspace management, and infrastructure lifecycle handling may go undetected.

This issue tracks the work to bring the infrastructure module into compliance with the integration test requirement.

Subtasks

  • Audit the infrastructure module's public API and integration points to identify all behaviours requiring Robot Framework integration test coverage
  • Create a new Robot Framework test suite in robot/infrastructure/ for the infrastructure module
  • Add integration test cases covering the core functionality of the infrastructure module (e.g., LSP runtime lifecycle, workspace mapping, file synchronisation)
  • Implement the corresponding Robot keywords and resource libraries as needed
  • Run nox -e integration_tests and confirm all new Robot tests pass
  • Run nox -e coverage_report and confirm coverage remains ≥ 97%
  • Run nox (all sessions) and confirm no regressions

Definition of Done

  • All subtasks above are checked
  • Robot Framework integration tests for the infrastructure module exist in robot/infrastructure/ and pass under nox -e integration_tests
  • The new tests provide adequate coverage for the module's integration points
  • nox -e coverage_report reports coverage ≥ 97%
  • All nox stages pass
  • Coverage >= 97%
  • Commit created with message: test(infrastructure): add Robot Framework integration tests for the infrastructure module
  • PR merged and issue closed

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

## Metadata - **Branch**: `test/missing-test-levels-infrastructure-robot-integration-tests` - **Commit Message**: `test(infrastructure): add Robot Framework integration tests for the infrastructure module` - **Milestone**: *(none — backlog)* - **Parent Epic**: #1678 > **Backlog note:** This issue was discovered during autonomous operation > on milestone Test Infrastructure. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. ## Background and Context The `infrastructure` module in `src/cleveragents/infrastructure` is missing Robot Framework integration tests. Per the project testing strategy, every module must have integration tests written using the Robot Framework, located under the `robot/` directory. Integration tests must exercise the module against real services and dependencies — mocks are not permitted in Robot tests. The `infrastructure` module provides the foundational runtime layer of the CleverAgents platform, including the LSP Runtime (which manages language server lifecycles, workspace mapping, and file synchronisation) and other infrastructure-level concerns. Without integration test coverage at the Robot Framework level, regressions in LSP server startup, workspace management, and infrastructure lifecycle handling may go undetected. This issue tracks the work to bring the `infrastructure` module into compliance with the integration test requirement. ## Subtasks - [ ] Audit the `infrastructure` module's public API and integration points to identify all behaviours requiring Robot Framework integration test coverage - [ ] Create a new Robot Framework test suite in `robot/infrastructure/` for the `infrastructure` module - [ ] Add integration test cases covering the core functionality of the `infrastructure` module (e.g., LSP runtime lifecycle, workspace mapping, file synchronisation) - [ ] Implement the corresponding Robot keywords and resource libraries as needed - [ ] Run `nox -e integration_tests` and confirm all new Robot tests pass - [ ] Run `nox -e coverage_report` and confirm coverage remains ≥ 97% - [ ] Run `nox` (all sessions) and confirm no regressions ## Definition of Done - [ ] All subtasks above are checked - [ ] Robot Framework integration tests for the `infrastructure` module exist in `robot/infrastructure/` and pass under `nox -e integration_tests` - [ ] The new tests provide adequate coverage for the module's integration points - [ ] `nox -e coverage_report` reports coverage ≥ 97% - [ ] All nox stages pass - [ ] Coverage >= 97% - [ ] Commit created with message: `test(infrastructure): add Robot Framework integration tests for the infrastructure module` - [ ] PR merged and issue closed --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Backlog (confirmed)
  • Story Points: 5 — L — Requires auditing infrastructure module integration points, creating Robot test suite, and implementing integration tests against real services.
  • MoSCoW: Could Have — Integration test coverage is important for quality but does not block any milestone. The infrastructure module's core functionality is already covered by unit tests.
  • Parent Epic: #1678

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Backlog (confirmed) - **Story Points**: 5 — L — Requires auditing infrastructure module integration points, creating Robot test suite, and implementing integration tests against real services. - **MoSCoW**: Could Have — Integration test coverage is important for quality but does not block any milestone. The infrastructure module's core functionality is already covered by unit tests. - **Parent Epic**: #1678 --- **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#3767
No description provided.