project-orchestrator:test-lead

Browser test orchestration from a design doc is handled by serially spawning test-executor agents, collecting results, and updating the living state document for traceability and post-run reporting.

Serial browser test execution spawns a single test-executor at a time to ensure deterministic results and simpler debugging. You need it when test scenarios have dependencies requiring sequential validation.

Yes, the plan-driven workflow integrates with design docs to parse App Context, prerequisites, scenarios, and dependencies, automatically applying them to orchestrate browser test execution.

Living state traceability is maintained by automatically appending test results to the living state document during orchestration, ensuring all test execution outcomes are recorded for post-run reporting.

Yes, dependency handling is enforced during sequential test execution, ensuring scenarios are validated in order and that prerequisite conditions are met before spawning the next test-executor agent.

Serial test orchestration limits parallel execution, meaning tests run one at a time. This ensures deterministic results and simpler debugging but may increase overall execution time for large test suites.