
Test Automation Strategy Builder
Design robust test frameworks and eliminate flaky test chaos
What You Can Do
You'll design maintainable, scalable test automation frameworks tailored to your tech stack and team. Claude helps you diagnose and fix flaky tests by identifying root causes (race conditions, async issues, data isolation problems) and providing targeted solutions. You'll establish testing strategies that reduce debugging time, improve CI/CD reliability, and create lasting documentation your team can follow.
Features
Create modular, maintainable automation frameworks with clear separation of unit, integration, and E2E tests
Identify root causes (race conditions, missing waits, stale elements, data isolation) and implement proven stabilization strategies
Build scalable UI automation using abstraction layers and DRY test code principles
Design reliable setup, teardown, and isolation patterns that prevent cross-test contamination
Master timeouts, explicit waits, and race condition detection in async/await test code
Design test execution pipelines optimized for parallelization and reliable feedback
Track and optimize test execution speed to catch degradation early
Generate standards and runbooks so your team maintains quality over time
Example Output
Example 1: Architecture Recommendation
Testing Pyramid Design:
- Unit Tests (Jest): 60% of suite, 2-5ms each → Business logic, utilities
- Integration Tests (Playwright): 30% of suite, 50-200ms each → Components, APIs
- E2E Tests (Cypress): 10% of suite, 2-5s each → Critical user flows only
Repository Layout:
├── tests/unit/, integration/, e2e/
├── fixtures/ # Test data
├── utils/page-objects/ # UI abstraction layer
└── .env.test # Test configuration
Example 2: Flaky Test Fix
Problem: Intermittent "button not clickable" failures (15% fail rate) Root Causes: Missing network idle wait, stale DOM refs, scroll race condition Solution:
// After: stable with explicit waits
await page.waitForLoadState('networkidle');
await page.locator('button#submit').scrollIntoViewIfNeeded();
await page.locator('button#submit').click();
Result: 100% pass rate after 50 consecutive runs
Example 3: Test Data Strategy
- Per-test database transaction with automatic rollback
- Factory pattern for creating realistic test entities
- Parallel worker isolation using unique seeds
- Sensitive data masking in CI logs
What's Included
- SKILL.md file: Complete test automation strategy framework with workflows and checklists
- Framework comparison matrix: Unit vs. integration vs. E2E trade-offs and tool selection
- Page Object Model templates: Playwright and Cypress examples with base classes
- Test data patterns: Factory, fixture, and API setup method examples
- Flaky test diagnosis tree: Decision flowchart for identifying root causes
- CI/CD pipeline templates: GitHub Actions, GitLab CI, and Jenkins configurations
- Test isolation checklist: Database, environment, and concurrency patterns
- Async/await troubleshooting guide: Waits, timeouts, race condition detection
- Test metrics dashboard template: Monitoring pass rates and execution trends
Who It's For
- QA engineers and test automation specialists — Designing new frameworks or refactoring existing suites
- Full-stack and backend engineers — Building robust test suites and establishing standards
- Engineering leads — Setting testing best practices and quality standards across teams
- DevOps engineers — Optimizing test pipelines and CI/CD integration
- Developers debugging tests — Troubleshooting flaky tests, race conditions, and failures
Best For
- Designing test automation architecture — Planning frameworks, pyramid structure, tool selection
- Fixing flaky and intermittent tests — Diagnosing race conditions, async issues, data isolation
- Establishing test data strategies — Designing setup/teardown patterns and test isolation
- Building UI automation layers — Creating scalable Page Object Models and reducing maintenance
- Optimizing test execution — Parallelization, performance profiling, CI/CD pipeline design
- Creating test standards — Establishing naming conventions and metrics for your team







