-
Notifications
You must be signed in to change notification settings - Fork 0
Integration test: multi-agent delegation with task decomposition #30
Copy link
Copy link
Closed
Labels
prio:highImportant, should be prioritizedImportant, should be prioritizedscope:medium1-3 days of work1-3 days of workspec:agent-systemDESIGN_SPEC Section 3 - Agent SystemDESIGN_SPEC Section 3 - Agent Systemspec:communicationDESIGN_SPEC Section 5 - Communication ArchitectureDESIGN_SPEC Section 5 - Communication Architecturespec:providersDESIGN_SPEC Section 9 - Model Provider LayerDESIGN_SPEC Section 9 - Model Provider Layerspec:task-workflowDESIGN_SPEC Section 6 - Task & Workflow EngineDESIGN_SPEC Section 6 - Task & Workflow Enginetype:testTest coverage, test infrastructureTest coverage, test infrastructure
Description
Context
End-to-end integration test that validates the full multi-agent orchestration pipeline — from task creation through delegation, decomposition, execution, and result aggregation. This test ensures all M4 components work together correctly.
Acceptance Criteria
Test Scenarios
- Scenario 1: Happy path — Lead decomposes task for 2 agents, both complete successfully, results aggregated
- Scenario 2: Partial failure — One subtask fails, parent task marked with appropriate failure status
- Scenario 3: Loop prevention — Delegation loop is detected and prevented before infinite recursion
- Scenario 4: Parallel execution — Multiple agents execute concurrently, results correctly aggregated
Test Infrastructure
- Mocked LLM (no real API calls)
- Full delegation chain validated (task flows down, results flow up)
- Status transitions validated at each step
- Loop prevention verified with clear assertion messages
- Test is deterministic and repeatable
Dependencies
- Depends on task decomposition and routing engine (Implement task decomposition and routing engine #14)
- Depends on loop prevention (Implement loop prevention (depth limits, dedup, circuit breakers, ancestry) #17)
Design Spec Reference
- Section 5 — Communication
- Section 6 — Task Workflow
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
prio:highImportant, should be prioritizedImportant, should be prioritizedscope:medium1-3 days of work1-3 days of workspec:agent-systemDESIGN_SPEC Section 3 - Agent SystemDESIGN_SPEC Section 3 - Agent Systemspec:communicationDESIGN_SPEC Section 5 - Communication ArchitectureDESIGN_SPEC Section 5 - Communication Architecturespec:providersDESIGN_SPEC Section 9 - Model Provider LayerDESIGN_SPEC Section 9 - Model Provider Layerspec:task-workflowDESIGN_SPEC Section 6 - Task & Workflow EngineDESIGN_SPEC Section 6 - Task & Workflow Enginetype:testTest coverage, test infrastructureTest coverage, test infrastructure