You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Story 5.1] Cross-epic integration test suite #378
Each story has unit tests against its own boundaries, but no test exercises the full path: parallel tool dispatch → one tool triggers new_task → TaskScheduler manages subtask → child completes → parent resumes with result. This is where cross-component bugs surface. Using Gemini CLI's wave-based execution log pattern: an executionLog: string[] array traces the full lifecycle and ordering invariants are asserted against it.
Wire real implementations of TaskScheduler, TaskRegistry, DispatchState, and ToolExecutionContext with mocked I/O (mock LLM responses, mock file system, in-memory TaskHistoryStore).
Use sequential Vitest execution (not test.concurrent) — these tests have inherent ordering dependencies.
Use vi.useFakeTimers() + controlled promises for deterministic scheduling.
Test scenarios:
Parallel read tools:[read_file, list_files] → both start concurrently (wave 1). Assert executionLog has both start events before either end event.
Mixed parallel + sequential:[read_file, execute_command] → read_file in wave 1, execute_command in wave 2 after wave 1 completes.
Child completion resumes parent: From scenario 3, child completes → scheduler releases permit → parent resumes with tool_result in userMessageContent.
Rejection cancels unstarted tools:[read_file_A, read_file_B, write_to_file] with pLimit(2) → A and B dispatched, write_to_file queued. User rejects A → write_to_file cancelled. B finishes normally. Assert 3 results: tool_denied, tool_result, tool_cancelled.
maxConcurrency = 1 backward compatibility: Scenarios 1–4 with maxConcurrency = 1 and flag off. Assert strictly serial execution matching current behavior.
Activity