flaky-test-specialist

Fix intermittent flaky test failures by diagnosing timing issues and race conditions, replacing arbitrary timeouts with condition-based waits, and verifying the fix by running the test repeatedly in CI.

Race conditions and timing-dependent flakiness in Vitest are caused by missing waits, improper async/await handling, shared state, and network timing issues. Applying deterministic patterns and test isolation resolves these failures.

Replace arbitrary sleeps with condition-based waits in Playwright by using proper waitFor methods and async/await handling to remove timing dependencies and stabilize end-to-end test execution.

Yes, this approach works for both Vitest unit tests and Playwright end-to-end tests by applying framework-specific best practices to improve test isolation, clean resources, and mock network timing.

The best way to debug flaky tests caused by shared state and resource leaks is to reset state, clean resources, add tracing logs or screenshots, and run tests in isolation to identify the root cause.

Use fake timers or deterministic network mocks to stabilize flaky tests when facing non-deterministic network timing issues or concurrent operations that require controlled, predictable execution environments.