Test Architecture: Verify Robot Framework Tests Use Real Services #10086

Open
opened 2026-04-16 22:20:59 +00:00 by HAL9000 · 0 comments
Owner

Summary

Robot Framework integration tests should use real services (no mocks) per CONTRIBUTING.md. Need to verify this requirement is met across all tests.

Current State

  • Robot tests: Extensive tests in robot/ directory
  • Mocks location: features/mocks/ (Behave only)
  • Robot fixtures: robot/fixtures/ directory exists
  • Verification needed: Ensure no mocks are used in Robot tests

Impact

  • Integration tests may not be testing real service interactions
  • Potential false positives in test results
  • Deviation from CONTRIBUTING.md requirements

Proposed Solution

  1. Audit all Robot Framework tests for mock usage
  2. Verify all tests use real services or proper test fixtures
  3. Document any exceptions or special cases
  4. Implement checks to prevent mock usage in Robot tests

Acceptance Criteria

  • All Robot Framework tests audited
  • No unauthorized mocks found in robot/ directory
  • Test fixtures properly organized
  • Documentation updated if needed

Duplicate Check

Searched for existing issues with keywords: "Robot Framework", "integration tests", "mocks"
No duplicate issues found in open or closed issues.


Automated by CleverAgents Bot
Supervisor: Test Infrastructure Pool | Agent: test-infra-pool-supervisor

## Summary Robot Framework integration tests should use real services (no mocks) per CONTRIBUTING.md. Need to verify this requirement is met across all tests. ## Current State - **Robot tests**: Extensive tests in `robot/` directory - **Mocks location**: `features/mocks/` (Behave only) - **Robot fixtures**: `robot/fixtures/` directory exists - **Verification needed**: Ensure no mocks are used in Robot tests ## Impact - Integration tests may not be testing real service interactions - Potential false positives in test results - Deviation from CONTRIBUTING.md requirements ## Proposed Solution 1. Audit all Robot Framework tests for mock usage 2. Verify all tests use real services or proper test fixtures 3. Document any exceptions or special cases 4. Implement checks to prevent mock usage in Robot tests ## Acceptance Criteria - [ ] All Robot Framework tests audited - [ ] No unauthorized mocks found in robot/ directory - [ ] Test fixtures properly organized - [ ] Documentation updated if needed ### Duplicate Check Searched for existing issues with keywords: "Robot Framework", "integration tests", "mocks" No duplicate issues found in open or closed issues. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure Pool | Agent: test-infra-pool-supervisor
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#10086
No description provided.