
Test
Run comprehensive test suites with parallel unit, integration, and E2E execution
What You Can Do
You can orchestrate a complete testing strategy that balances speed with thoroughness. Claude runs type diagnostics first to catch root causes, executes unit and integration tests in parallel for efficiency, then sequences E2E tests only after faster tests pass. This workflow prevents wasted time on slow tests when foundational issues exist.
Features
Type checks before test execution to identify root causes instantly
Runs unit and integration tests simultaneously for faster feedback
Triggers end-to-end tests only after unit/integration tests pass
Organized workflow from fast tests to slow tests
Identifies which test layer failed and why, not just that tests failed
Optional detection of affected tests based on code changes
Visual test results organized by phase and agent responsibility
Example Output
Example 1: Full test pass
Phase 0: Diagnostics ✓ (0 errors)
Phase 1: Unit Tests ✓ (24 passed)
Phase 1: Integration Tests ✓ (8 passed)
Phase 2: E2E Tests ✓ (6 passed)
All tests passed in 47 seconds
Example 2: Type error caught early
Phase 0: Diagnostics ✗
Error: Expected int, got str at src/utils.ts:12
Error: Missing required property 'id' at src/models.ts:35
→ Fix type errors before running tests (estimated 2 min)
Example 3: Integration test failure
Phase 0: Diagnostics ✓ (0 errors)
Phase 1: Unit Tests ✓ (24 passed)
Phase 1: Integration Tests ✗ (1 failed: Database connection)
→ E2E tests skipped (integration layer unstable)
What's Included
- SKILL.md: Complete testing workflow specification with agent sequence and execution phases
- Test orchestration framework: Structured approach to unit, integration, and E2E test coordination
- Diagnostic checklist: Pre-flight type checking procedures to prevent false test failures
- Phase execution guide: Step-by-step process from diagnostics through parallel and sequential test stages
- Troubleshooting decision tree: How to interpret which test layer failed and what to fix first
Who It's For
- QA Engineers — Automating and optimizing full test suite execution workflows
- Software Engineers — Verifying code quality before commits, PRs, and releases
- Release Engineers — Gating deployments with comprehensive test validation
- DevOps/CI-CD Specialists — Structuring test pipelines with parallel and sequential phases
- Tech Leads — Ensuring team testing standards are met before code merges
Best For
- Pre-release testing — Running full test suites before production deployments
- Pull request validation — Comprehensive test execution before code review approval
- Type safety verification — Catching type errors before they cause test failures
- Performance regression detection — Running E2E tests only after unit/integration layers pass
- Fast feedback loops — Identifying failures in unit tests (seconds) before waiting on E2E (minutes)







