Epic: Milestone Acceptance and Workflow Example Integration Tests #401

Open
opened 2026-02-23 20:34:33 +00:00 by freemo · 1 comment
Owner

Background

Covers all milestone acceptance criteria integration test suites and workflow example integration test suites. Each milestone's verification suite validates the feature set delivered in that milestone using integration-appropriate mocking (e.g., mocked LLM providers). Workflow example tests translate the 18 specification workflow examples into Robot Framework integration tests.

See Forgejo dependency links for child issues.

Expected Behavior

Each milestone has a dedicated integration test suite that validates the full feature set delivered in that milestone. Workflow example integration tests validate the command sequences and expected outputs from the specification's Workflow Examples section. Tests use integration-appropriate mocking (e.g., mocked LLM providers) and run within the standard nox -s integration_tests session.

Definition of Done

This Epic is complete when all child issues (tracked via Forgejo dependency links) are closed and merged. All milestone integration suites and workflow example integration tests pass.

## Background Covers all milestone acceptance criteria integration test suites and workflow example integration test suites. Each milestone's verification suite validates the feature set delivered in that milestone using integration-appropriate mocking (e.g., mocked LLM providers). Workflow example tests translate the 18 specification workflow examples into Robot Framework integration tests. See Forgejo dependency links for child issues. ## Expected Behavior Each milestone has a dedicated integration test suite that validates the full feature set delivered in that milestone. Workflow example integration tests validate the command sequences and expected outputs from the specification's Workflow Examples section. Tests use integration-appropriate mocking (e.g., mocked LLM providers) and run within the standard `nox -s integration_tests` session. ## Definition of Done This Epic is complete when all child issues (tracked via Forgejo dependency links) are closed and merged. All milestone integration suites and workflow example integration tests pass.
freemo self-assigned this 2026-02-24 03:37:58 +00:00
freemo changed title from Epic: E2E Integration Testing to Epic: Milestone Acceptance and Workflow Example Integration Tests 2026-03-12 19:22:09 +00:00
freemo added this to the v3.2.0 milestone 2026-03-17 18:32:04 +00:00
Author
Owner

Label compliance fix applied:

  • Replaced orphaned label State/In Progress with valid label State/In progress
  • Reason: State/In Progress (capital P) is an orphaned label. The correct label is State/In progress (lowercase p).

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

Label compliance fix applied: - Replaced orphaned label `State/In Progress` with valid label `State/In progress` - Reason: `State/In Progress` (capital P) is an orphaned label. The correct label is `State/In progress` (lowercase p). --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
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 Depends on
#200 test(e2e): add M5 ACMS + context suites
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core#401
No description provided.