test(integration): implement workflow example integration test suites for specification examples 10–18 #8986

Open
opened 2026-04-14 04:35:19 +00:00 by HAL9000 · 1 comment
Owner

Background and Context

Epic #401 requires all 18 specification workflow examples to be translated into Robot Framework integration tests. This issue covers the second half — workflow examples 10–18. These later examples typically cover more advanced features such as decision correction, invariant enforcement, and multi-step plan workflows. Integration tests use mocked LLM providers, making them fast and CI-friendly. Without these tests, the full set of documented workflow examples lacks automated regression coverage and the Epic cannot be closed.

Expected Behavior

When this issue is complete:

  • Robot Framework integration test suites for workflow examples 10–18 exist under tests/integration/workflow_examples/
  • Each suite exercises the command sequence from the corresponding specification workflow example using mocked LLM providers
  • Output validation is flexible — checks major structural components without strict character-by-character comparison
  • All 9 suites run under nox -s integration_tests and pass
  • All 18 workflow example integration suites (examples 1–18) pass together under nox -s integration_tests

Acceptance Criteria

  • One .robot file per workflow example (examples 10–18) exists under tests/integration/workflow_examples/
  • Workflow example 10 integration test passes under nox -s integration_tests
  • Workflow example 11 integration test passes under nox -s integration_tests
  • Workflow example 12 integration test passes under nox -s integration_tests
  • Workflow example 13 integration test passes under nox -s integration_tests
  • Workflow example 14 integration test passes under nox -s integration_tests
  • Workflow example 15 integration test passes under nox -s integration_tests
  • Workflow example 16 integration test passes under nox -s integration_tests
  • Workflow example 17 integration test passes under nox -s integration_tests
  • Workflow example 18 integration test passes under nox -s integration_tests
  • All 18 workflow example integration suites pass together without cross-suite interference
  • Output validation uses flexible matching (structural checks, not exact character matching)
  • Suites are NOT tagged @E2E

Subtasks

  • Write workflow_example_10.robot through workflow_example_18.robot
  • Reuse shared integration keywords library from tests/integration/resources/integration_keywords.resource
  • Map each workflow example to its specification section and document the reference in the suite header
  • Run all 9 suites under nox -s integration_tests and verify they pass
  • Run the full 18-suite integration suite together and verify no cross-suite interference
  • Update integration test documentation to mark all 18 workflow example suites as complete
  • Verify coverage >= 97% via nox -s coverage_report

Definition of Done

  • All acceptance criteria met
  • Tests written and passing (coverage >= 97%)
  • Code reviewed and approved
  • Documentation updated if needed
  • No regressions introduced

Metadata

  • Commit message: test(integration): implement workflow example integration test suites for specification examples 10–18
  • Branch name: test/integration-workflow-examples-10-18

Automated by CleverAgents Bot
Supervisor: Epic Planning Pool | Agent: epic-planning-pool-supervisor

## Background and Context Epic #401 requires all 18 specification workflow examples to be translated into Robot Framework integration tests. This issue covers the second half — workflow examples 10–18. These later examples typically cover more advanced features such as decision correction, invariant enforcement, and multi-step plan workflows. Integration tests use mocked LLM providers, making them fast and CI-friendly. Without these tests, the full set of documented workflow examples lacks automated regression coverage and the Epic cannot be closed. ## Expected Behavior When this issue is complete: - Robot Framework integration test suites for workflow examples 10–18 exist under `tests/integration/workflow_examples/` - Each suite exercises the command sequence from the corresponding specification workflow example using mocked LLM providers - Output validation is flexible — checks major structural components without strict character-by-character comparison - All 9 suites run under `nox -s integration_tests` and pass - All 18 workflow example integration suites (examples 1–18) pass together under `nox -s integration_tests` ## Acceptance Criteria - [ ] One `.robot` file per workflow example (examples 10–18) exists under `tests/integration/workflow_examples/` - [ ] Workflow example 10 integration test passes under `nox -s integration_tests` - [ ] Workflow example 11 integration test passes under `nox -s integration_tests` - [ ] Workflow example 12 integration test passes under `nox -s integration_tests` - [ ] Workflow example 13 integration test passes under `nox -s integration_tests` - [ ] Workflow example 14 integration test passes under `nox -s integration_tests` - [ ] Workflow example 15 integration test passes under `nox -s integration_tests` - [ ] Workflow example 16 integration test passes under `nox -s integration_tests` - [ ] Workflow example 17 integration test passes under `nox -s integration_tests` - [ ] Workflow example 18 integration test passes under `nox -s integration_tests` - [ ] All 18 workflow example integration suites pass together without cross-suite interference - [ ] Output validation uses flexible matching (structural checks, not exact character matching) - [ ] Suites are NOT tagged `@E2E` ## Subtasks - [ ] Write `workflow_example_10.robot` through `workflow_example_18.robot` - [ ] Reuse shared integration keywords library from `tests/integration/resources/integration_keywords.resource` - [ ] Map each workflow example to its specification section and document the reference in the suite header - [ ] Run all 9 suites under `nox -s integration_tests` and verify they pass - [ ] Run the full 18-suite integration suite together and verify no cross-suite interference - [ ] Update integration test documentation to mark all 18 workflow example suites as complete - [ ] Verify coverage >= 97% via `nox -s coverage_report` ## Definition of Done - [ ] All acceptance criteria met - [ ] Tests written and passing (coverage >= 97%) - [ ] Code reviewed and approved - [ ] Documentation updated if needed - [ ] No regressions introduced ## Metadata - **Commit message:** `test(integration): implement workflow example integration test suites for specification examples 10–18` - **Branch name:** `test/integration-workflow-examples-10-18` --- **Automated by CleverAgents Bot** Supervisor: Epic Planning Pool | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.2.0 milestone 2026-04-14 04:45:26 +00:00
Author
Owner

Verified — Integration test suites for workflow examples 10-18 are required for v3.2.0 test coverage. MoSCoW: Must-have. Priority: Medium.


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

✅ **Verified** — Integration test suites for workflow examples 10-18 are required for v3.2.0 test coverage. MoSCoW: Must-have. Priority: Medium. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-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.

Reference
cleveragents/cleveragents-core#8986
No description provided.