triage-ci-flake

To reproduce flaky CI test failures locally, you must execute a mandatory reproduction workflow that differentiates between development and bundled code environments. This structured approach isolates timing, bundling, or environment differences causing the intermittent CI failures.

E2E tests time out in CI due to race conditions, test pollution, or bundling differences between local development and bundled code. Systematically debugging these flaky test failures involves reproducing the CI environment locally to isolate the specific timing issue.

The best way to debug intermittent test failures from bundling differences is following a systematic workflow that isolates issues by running specific command executions. This process distinguishes between local development and bundled code execution to find the root cause.

You isolate race conditions and test pollution in a CI environment by systematically reproducing the flaky failures locally. This debugging workflow guides you through specific command executions to identify timing and environment differences before proposing fixes.

Yes, this flaky test debugging workflow supports both Vitest and Playwright. It systematically reproduces and debugs intermittent test failures across these testing frameworks, differentiating between local development and bundled code execution environments to isolate root causes.