Implemented Robot Framework E2E test suite validating Specification
Workflow Example 7 (CI/CD Integration). Tests exercise the real
CleverAgents CLI with zero mocking, covering:
- ci-profile configuration with JSON output format and WARN log level
(spec Step 1)
- Idempotent resource and project registration with resource linking,
verified via strict occurrence-count assertions
- Three-validation registration (lint, typecheck, tests) with project
attachment and tool-list verification
- CI plan launch with action args (pr_branch, base_branch), explicit
plan execute for lifecycle progression, and terminal-state assertion
- JSON output verification via json.loads() with raw_decode fallback
for mixed log/JSON CLI output
- Graceful degradation via Skip If No LLM Keys when API keys are
unavailable
Resource/project naming follows spec convention (local/ci-workspace
project, local/ci-main resource). Entity creation commands tolerate
"already exists" for CI re-runnability. Config assertions use
stdout-only matching and exact equality. Validation naming aligned
with spec (local/ci-lint per §Example 7, line 39130).
Added robot/common_vars.py module placeholder for shared Robot
Framework variables.
ISSUES CLOSED: #753