/test Testing Workflow Run comprehensive test suite with parallel execution. When to Use "Run all tests" "Test the feature" "Verify everything works" "Full test suite" Before releases or merges After major changes Workflow Overview Agent Sequence Agent Role Execution 1 arbiter Unit tests, type checks, linting Parallel 1 arbiter Integration tests Parallel 2 atlas E2E/acceptance tests After 1 passes Why This Order? 1. Fast feedback : Unit tests fail fast 2. Parallel efficiency : No dependency between unit and integration 3. E2E gating : Only run slow E2E tests if faster tests pass Execution Phase 0: Pre flight Diagnostics (NEW) Before running tests, check for type errors they often cause test failures: Why diagnostics first? Type check is instant (~1s), tests take longer Diagnostics show ROOT CAUSE, tests show symptoms "Expected int, got str" is clearer than "AttributeError at line 50" Catches errors in untested code paths If errors found: Fix them BEFORE running tests. Type errors usually mean tests will fail anyway. If clean: Proceed to Phase 1. Phase 0.5: Change Impact (Optional) For large test suites, find only affected tests: This returns which tests to run based on what changed. Skip this for small projects or when you want full coverage. Phase 1: Parallel Tests Phase 2: E2E Tests (If Phase 1 Passes) Test Scopes Full Suite Feature Scope Quick Check Example Example with Type Errors Failure Handling If Phase 1 fails: Flags quick : Unit tests only no e2e : Skip E2E tests coverage : Include coverage report watch : Re run on file changes