e2e-test-optimizer

Replace arbitrary waitForTimeout calls with smart waits that target specific conditions: navigation waits for page loads, state-transition waits for DOM changes, and network waits for API responses. This eliminates flakiness by waiting only as long as needed for the actual event, not a fixed duration.

Yes, test sharding enables parallel execution by distributing tests across CI workers. Configure sharding in your CI pipeline to split tests by shard ID and total shard count, reducing total runtime while maintaining test isolation.

Combine smart waits to eliminate timeout delays, enable test sharding for parallel execution, and optimize mock setups to reduce overhead. Together, these reduce both flakiness and total runtime.

Arbitrary waitForTimeout durations often mismatch between local and CI environments due to resource differences. Smart waits adapt to actual state changes, eliminating environment-dependent timeouts and improving reliability across all contexts.

Playwright supports test sharding through configuration, but CI integration requires explicit shard setup. This Skill guides CI sharding configuration to parallelize test execution without additional dependencies.

The primary anti-pattern is waitForTimeout with arbitrary durations. Replace these with targeted waits: use waitForNavigation for page navigation, waitForSelector or waitForFunction for DOM state, and network event handling for API calls.