Add Robot Framework integration test for the infrastructure module #2794

Open
opened 2026-04-04 19:44:25 +00:00 by freemo · 2 comments
Owner

Metadata

  • Branch: test/robot-infrastructure-module-integration
  • Commit Message: test(infrastructure): add Robot Framework integration test for infrastructure module
  • Milestone: v3.5.0
  • Parent Epic: #397

Background

The infrastructure module (server transport stubs, ACP facade, LSP stub wiring, autonomy guards) currently has no Robot Framework integration test coverage under robot/. Per project conventions, all integration tests must use Robot Framework and reside in robot/; mocking is strictly prohibited in integration tests. This gap means the module's real-world behaviour is unverified at the integration level.

Subtasks

  • Identify all public entry-points and flows in the infrastructure module that require integration-level verification (transport stubs, ACP facade, LSP wiring, autonomy guards)
  • Create robot/infrastructure/ directory and add a __init__.robot or suite file following existing Robot suite conventions
  • Write Robot test cases covering the happy-path flows for each identified entry-point
  • Write Robot test cases covering key error/edge-case flows (e.g., guard enforcement, budget cap breach)
  • Ensure no mocks are used — all dependencies must be real or stubbed at the infrastructure boundary
  • Run nox -e integration_tests locally and confirm all new tests pass
  • Run nox -e coverage_report and confirm overall coverage remains >= 97%
  • Run full nox suite and confirm all stages pass

Definition of Done

  • A Robot Framework test suite exists under robot/infrastructure/ covering the infrastructure module's public flows
  • All new Robot tests pass under nox -e integration_tests
  • No mocking libraries or test doubles are used in the Robot suite
  • nox -e typecheck passes with no new type errors
  • nox -e lint passes with no new lint violations
  • All nox stages pass
  • Coverage >= 97%

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

## Metadata - **Branch**: `test/robot-infrastructure-module-integration` - **Commit Message**: `test(infrastructure): add Robot Framework integration test for infrastructure module` - **Milestone**: v3.5.0 - **Parent Epic**: #397 ## Background The `infrastructure` module (server transport stubs, ACP facade, LSP stub wiring, autonomy guards) currently has no Robot Framework integration test coverage under `robot/`. Per project conventions, all integration tests must use Robot Framework and reside in `robot/`; mocking is strictly prohibited in integration tests. This gap means the module's real-world behaviour is unverified at the integration level. ## Subtasks - [ ] Identify all public entry-points and flows in the infrastructure module that require integration-level verification (transport stubs, ACP facade, LSP wiring, autonomy guards) - [ ] Create `robot/infrastructure/` directory and add a `__init__.robot` or suite file following existing Robot suite conventions - [ ] Write Robot test cases covering the happy-path flows for each identified entry-point - [ ] Write Robot test cases covering key error/edge-case flows (e.g., guard enforcement, budget cap breach) - [ ] Ensure no mocks are used — all dependencies must be real or stubbed at the infrastructure boundary - [ ] Run `nox -e integration_tests` locally and confirm all new tests pass - [ ] Run `nox -e coverage_report` and confirm overall coverage remains >= 97% - [ ] Run full `nox` suite and confirm all stages pass ## Definition of Done - [ ] A Robot Framework test suite exists under `robot/infrastructure/` covering the infrastructure module's public flows - [ ] All new Robot tests pass under `nox -e integration_tests` - [ ] No mocking libraries or test doubles are used in the Robot suite - [ ] `nox -e typecheck` passes with no new type errors - [ ] `nox -e lint` passes with no new lint violations - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Unknown | Agent: ca-new-issue-creator
freemo added this to the v3.5.0 milestone 2026-04-04 19:44:34 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified | MoSCoW: Should Have — Missing Robot Framework integration test for the infrastructure module. Integration test coverage is important for system reliability.

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

Issue triaged by project owner: - **State**: Verified | **MoSCoW**: Should Have — Missing Robot Framework integration test for the infrastructure module. Integration test coverage is important for system reliability. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
Author
Owner

This issue has been moved to the backlog as part of an aggressive grooming of the v3.5.0 milestone. It has been deemed non-critical for the minimal viability of the milestone and will be addressed in a future release.

This issue has been moved to the backlog as part of an aggressive grooming of the v3.5.0 milestone. It has been deemed non-critical for the minimal viability of the milestone and will be addressed in a future release.
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.

Blocks
#397 Epic: Server & Autonomy Infrastructure
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core#2794
No description provided.