Translate workflow examples to E2E tests #679

New issue

Closed

opened 2026-03-11 03:36:03 +00:00 by brent.edwards · 2 comments

brent.edwards commented

2026-03-11 03:36:03 +00:00

Member

In the documentation file /docs/specification.md is a section named "Workflow Examples". This section contains 18 examples, fully worked out with the expected output.

This issue is to transform those 18 examples into end-to-end tests that validate that the code is working correctly.

In the documentation file `/docs/specification.md` is a section named "Workflow Examples". This section contains 18 examples, fully worked out with the expected output. This issue is to transform those 18 examples into end-to-end tests that validate that the code is working correctly.

brent.edwards added the

labels

2026-03-11 03:36:03 +00:00

freemo added the

Points

Priority

Medium

labels

2026-03-11 05:36:35 +00:00

brent.edwards was assigned by freemo

2026-03-11 05:36:35 +00:00

freemo added this to the v3.6.0 milestone

2026-03-11 05:36:35 +00:00

freemo commented

2026-03-11 05:36:36 +00:00

Owner

PM Triage (Day 31):

Labels: Type/Testing, Priority/Medium, MoSCoW/Should have, State/Unverified, Points/13
Milestone: v3.6.0
Assignee: @brent.edwards (author, QA specialist)

Assessment: Good quality improvement proposal. Translating 18 specification workflow examples into E2E tests will validate functional correctness against the spec. Assigned to v3.6.0 as this is quality hardening work — not blocking current milestones.

Note: This relates to #658 (E2E mock issue). Consider addressing both together for a unified E2E testing strategy.

**PM Triage (Day 31)**: - **Labels**: `Type/Testing`, `Priority/Medium`, `MoSCoW/Should have`, `State/Unverified`, `Points/13` - **Milestone**: v3.6.0 - **Assignee**: @brent.edwards (author, QA specialist) **Assessment**: Good quality improvement proposal. Translating 18 specification workflow examples into E2E tests will validate functional correctness against the spec. Assigned to v3.6.0 as this is quality hardening work — not blocking current milestones. **Note**: This relates to #658 (E2E mock issue). Consider addressing both together for a unified E2E testing strategy.

freemo added

and removed

labels

2026-03-11 20:21:34 +00:00

freemo commented

2026-03-12 19:22:53 +00:00

Owner

This issue has been superseded by more granular tickets.

The original scope — translating the 18 specification workflow examples into tests — has been split into two parallel efforts:

18 integration test tickets (with integration-appropriate mocking, e.g., mocked LLM providers) added as children of the renamed Epic "Milestone Acceptance and Workflow Example Integration Tests" (formerly "E2E Integration Testing"). These are assigned to brent.edwards with milestones spread by feature.
18 true E2E test tickets (zero mocking, real LLM API keys, real subprocess invocation) under a new Epic "E2E testing suite for acceptance criteria and workflow examples". These are assigned to freemo.

Closing as State/Wont Do since the work is fully captured in the replacement tickets.

This issue has been superseded by more granular tickets. The original scope — translating the 18 specification workflow examples into tests — has been split into two parallel efforts: 1. **18 integration test tickets** (with integration-appropriate mocking, e.g., mocked LLM providers) added as children of the renamed Epic "Milestone Acceptance and Workflow Example Integration Tests" (formerly "E2E Integration Testing"). These are assigned to brent.edwards with milestones spread by feature. 2. **18 true E2E test tickets** (zero mocking, real LLM API keys, real subprocess invocation) under a new Epic "E2E testing suite for acceptance criteria and workflow examples". These are assigned to freemo. Closing as `State/Wont Do` since the work is fully captured in the replacement tickets.

freemo

2026-03-12 19:23:02 +00:00