test(integration): workflow example 4 — multi-project dependency update (supervised profile) #768

Closed
opened 2026-03-12 19:38:58 +00:00 by freemo · 0 comments
Owner

Metadata

  • Commit Message: test(integration): workflow example 4 — multi-project dependency update (supervised profile)
  • Branch: test/int-wf04-multi-project

Background

Integration test for Specification Workflow Example 4: Multi-Project Dependency Update. Exercises the supervised automation profile with 4 projects, child plan spawning, dependency-ordered execution, and coordinated apply using mocked LLM providers.

Runs within the standard nox -s integration_tests session using mocked LLM providers.

Expected Behavior

The integration test validates multi-project coordination with deterministic mocked LLM responses. Child plans execute in dependency order, per-project validations pass, and apply proceeds in order.

Acceptance Criteria

  • Robot Framework test suite in robot/ directory (standard integration tests)
  • Test registers 4 projects and exercises multi-project plan creation
  • Test uses integration-appropriate mocking (mocked LLM providers)
  • Test verifies child plan spawning (4 child plans)
  • Test verifies dependency-ordered execution and apply
  • Test passes via nox -s integration_tests
  • Coverage >=97% maintained

Subtasks

  • Write Robot Framework integration test suite for workflow example 4
  • Configure mocked LLM responses for multi-project dependency scenario
  • Create 4 temp repo fixtures
  • Implement supervised multi-project workflow
  • Verify via nox -s integration_tests
  • 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.
  • 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): workflow example 4 — multi-project dependency update (supervised profile)` - **Branch**: `test/int-wf04-multi-project` ## Background Integration test for Specification Workflow Example 4: Multi-Project Dependency Update. Exercises the `supervised` automation profile with 4 projects, child plan spawning, dependency-ordered execution, and coordinated apply using mocked LLM providers. Runs within the standard `nox -s integration_tests` session using mocked LLM providers. ## Expected Behavior The integration test validates multi-project coordination with deterministic mocked LLM responses. Child plans execute in dependency order, per-project validations pass, and apply proceeds in order. ## Acceptance Criteria - [x] Robot Framework test suite in `robot/` directory (standard integration tests) - [x] Test registers 4 projects and exercises multi-project plan creation - [x] Test uses integration-appropriate mocking (mocked LLM providers) - [x] Test verifies child plan spawning (4 child plans) - [x] Test verifies dependency-ordered execution and apply - [x] Test passes via `nox -s integration_tests` - [x] Coverage >=97% maintained ## Subtasks - [x] Write Robot Framework integration test suite for workflow example 4 - [x] Configure mocked LLM responses for multi-project dependency scenario - [x] Create 4 temp repo fixtures - [x] Implement supervised multi-project workflow - [x] Verify via `nox -s integration_tests` - [x] Verify coverage >=97% via `nox -s coverage_report` - [x] 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. - 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 this to the v3.3.0 milestone 2026-03-12 19:38:58 +00:00
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#768
No description provided.