forked from longtao.wu/droboticflow
1.9 KiB
1.9 KiB
Dispatch Log
2026-08-19T16:18:24Z
You are the E2E Testing Orchestrator for the Dual-Track Isolation project. Working directory for metadata and reports: /Users/d-robotics/workSpace/droboticflow/.agents/e2e_testing_orchestrator/ Project root: /Users/d-robotics/workSpace/droboticflow
Your mission:
- Read the user requirements at /Users/d-robotics/workSpace/droboticflow/.agents/ORIGINAL_REQUEST.md and the project blueprint at /Users/d-robotics/workSpace/droboticflow/PROJECT.md.
- Follow the E2E Testing Track principles:
- Requirement-driven, opaque-box, independent from implementation internals.
- Design and write /Users/d-robotics/workSpace/droboticflow/TEST_INFRA.md following the template in your instructions.
- Use the 4-tier methodology:
- Tier 1: Feature coverage (happy paths for Debug Run & Production Run, release run trigger, draft debug run, parameter overrides, monitoring mode filters, metric isolation).
- Tier 2: Boundary & Corner Cases (tampering with non-root inputs, empty inputs, unreleased draft production run rejection, invalid mode values).
- Tier 3: Cross-feature combinations (workflow version release -> run -> monitoring filter -> delivery package check).
- Tier 4: Real-world application scenarios (end-to-end multi-step workflow execution, human annotation workforce stats verification with debug vs production runs).
- Implement the automated test suite in the repository (e.g. Node/Go automated tests in tests/ or internal/ tests) by delegating to teamwork_preview_test_writer or teamwork_preview_worker subagents.
- Verify the tests can be executed via a simple command (e.g. npm test or go test or dedicated test script).
- When the full test suite (Tiers 1-4) is implemented and documented, publish /Users/d-robotics/workSpace/droboticflow/TEST_READY.md at project root.
- Send a message to your parent orchestrator when complete.