test(integration): implement workflow example integration test suites for specification examples 1–9 #8982

Open
opened 2026-04-14 04:35:09 +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. The specification's Workflow Examples section defines concrete command sequences and expected outputs representing real user journeys. This issue covers the first 9 workflow examples (examples 1–9). Integration tests use mocked LLM providers (unlike E2E tests which use real API keys), making them fast and suitable for the standard CI pipeline. Without these tests, the documented workflow examples have no automated regression coverage.

Expected Behavior

When this issue is complete:

  • Robot Framework integration test suites for workflow examples 1–9 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

Acceptance Criteria

  • tests/integration/workflow_examples/ directory exists with one .robot file per workflow example (examples 1–9)
  • Each suite references the corresponding specification section in its header
  • Workflow example 1 integration test passes under nox -s integration_tests
  • Workflow example 2 integration test passes under nox -s integration_tests
  • Workflow example 3 integration test passes under nox -s integration_tests
  • Workflow example 4 integration test passes under nox -s integration_tests
  • Workflow example 5 integration test passes under nox -s integration_tests
  • Workflow example 6 integration test passes under nox -s integration_tests
  • Workflow example 7 integration test passes under nox -s integration_tests
  • Workflow example 8 integration test passes under nox -s integration_tests
  • Workflow example 9 integration test passes under nox -s integration_tests
  • Output validation uses flexible matching (structural checks, not exact character matching)
  • Suites are NOT tagged @E2E

Subtasks

  • Create tests/integration/workflow_examples/ directory
  • Write workflow_example_01.robot through workflow_example_09.robot
  • Implement shared integration keywords library (tests/integration/resources/integration_keywords.resource) for CLI invocation with mocked LLM
  • 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
  • Update integration test documentation to list workflow example suites

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 1–9
  • Branch name: test/integration-workflow-examples-1-9

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. The specification's Workflow Examples section defines concrete command sequences and expected outputs representing real user journeys. This issue covers the first 9 workflow examples (examples 1–9). Integration tests use mocked LLM providers (unlike E2E tests which use real API keys), making them fast and suitable for the standard CI pipeline. Without these tests, the documented workflow examples have no automated regression coverage. ## Expected Behavior When this issue is complete: - Robot Framework integration test suites for workflow examples 1–9 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 ## Acceptance Criteria - [ ] `tests/integration/workflow_examples/` directory exists with one `.robot` file per workflow example (examples 1–9) - [ ] Each suite references the corresponding specification section in its header - [ ] Workflow example 1 integration test passes under `nox -s integration_tests` - [ ] Workflow example 2 integration test passes under `nox -s integration_tests` - [ ] Workflow example 3 integration test passes under `nox -s integration_tests` - [ ] Workflow example 4 integration test passes under `nox -s integration_tests` - [ ] Workflow example 5 integration test passes under `nox -s integration_tests` - [ ] Workflow example 6 integration test passes under `nox -s integration_tests` - [ ] Workflow example 7 integration test passes under `nox -s integration_tests` - [ ] Workflow example 8 integration test passes under `nox -s integration_tests` - [ ] Workflow example 9 integration test passes under `nox -s integration_tests` - [ ] Output validation uses flexible matching (structural checks, not exact character matching) - [ ] Suites are NOT tagged `@E2E` ## Subtasks - [ ] Create `tests/integration/workflow_examples/` directory - [ ] Write `workflow_example_01.robot` through `workflow_example_09.robot` - [ ] Implement shared integration keywords library (`tests/integration/resources/integration_keywords.resource`) for CLI invocation with mocked LLM - [ ] 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 - [ ] Update integration test documentation to list workflow example suites ## 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 1–9` - **Branch name:** `test/integration-workflow-examples-1-9` --- **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:25 +00:00
Author
Owner

Verified — Integration test suites for workflow examples 1-9 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 1-9 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#8982
No description provided.