test(integration): verify M4 success criteria — subplans and parallel execution #405

New issue

Closed

opened 2026-02-23 22:17:26 +00:00 by freemo · 2 comments

freemo commented

2026-02-23 22:17:26 +00:00

Owner

Metadata

Commit Message: test(integration): verify M4 success criteria — subplans and parallel execution
Branch: test/m4-e2e-verification

Description

Robot Framework integration test suite that exercises the complete M4 success criteria verification sequence: plan execution that spawns multiple subplans, subplan tree viewing, and verification of merged results. Uses integration-appropriate mocking (e.g., mocked LLM providers).

Acceptance Criteria

Robot test executes a plan that spawns multiple subplans during Execute
Robot test views the subplan tree via agents plan tree
Robot test verifies merged results via agents plan diff
Assertions verify parallel subplan execution works with max_parallel
Assertions verify three-way merge combines non-conflicting changes
Assertions verify merge conflicts are surfaced correctly
Assertions verify parent plan tracks all subplan statuses
nox passes with coverage >=97%

Verification Commands

# Full M4 verification sequence (from specification)
agents plan use local/refactor-action local/monorepo
agents plan execute <plan_id>
agents plan tree <plan_id>
agents plan diff <plan_id>

Subtasks

Write Robot Framework integration test suite covering all acceptance criteria above
Verify all assertions pass against working implementation
Tests (Behave): N/A (this is an integration test issue)
Tests (Robot): The Robot test suite IS this issue's deliverable
Tests (ASV): N/A (no benchmark needed for integration verification)
Verify coverage >=97% via nox -s coverage_report
Run nox (all default sessions), fix any errors

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.

## Metadata - **Commit Message**: `test(integration): verify M4 success criteria — subplans and parallel execution` - **Branch**: `test/m4-e2e-verification` ## Description Robot Framework integration test suite that exercises the complete M4 success criteria verification sequence: plan execution that spawns multiple subplans, subplan tree viewing, and verification of merged results. Uses integration-appropriate mocking (e.g., mocked LLM providers). ## Acceptance Criteria - [ ] Robot test executes a plan that spawns multiple subplans during Execute - [ ] Robot test views the subplan tree via `agents plan tree` - [ ] Robot test verifies merged results via `agents plan diff` - [ ] Assertions verify parallel subplan execution works with max_parallel - [ ] Assertions verify three-way merge combines non-conflicting changes - [ ] Assertions verify merge conflicts are surfaced correctly - [ ] Assertions verify parent plan tracks all subplan statuses - [ ] `nox` passes with coverage >=97% ## Verification Commands ```bash # Full M4 verification sequence (from specification) agents plan use local/refactor-action local/monorepo agents plan execute <plan_id> agents plan tree <plan_id> agents plan diff <plan_id> ``` ## Subtasks - [ ] Write Robot Framework integration test suite covering all acceptance criteria above - [ ] Verify all assertions pass against working implementation - [ ] Tests (Behave): N/A (this is an integration test issue) - [ ] Tests (Robot): The Robot test suite IS this issue's deliverable - [ ] Tests (ASV): N/A (no benchmark needed for integration verification) - [ ] Verify coverage >=97% via `nox -s coverage_report` - [ ] Run `nox` (all default sessions), fix any errors ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done.

freemo added the

Rows
Columns