test-flake-investigator

To diagnose flaky tests that pass locally but fail in CI, you need to analyze timing, order dependence, environment drift, and parallelism. Collecting failing outputs, logs, and runtime context helps narrow the surface and reproduce the issue across environments.

Timing-related flakiness and order-dependent test failures are caused by resource contention, environment drift, and poor fixture isolation. Analyzing these factors alongside parallelism issues helps isolate the root cause and surface actionable mitigations.

To troubleshoot environment drift causing test suite failures in CI, collect configuration and runtime context to compare against local environments. Isolating fixture usage and checking for resource contention narrows down the discrepancies.

Yes, you can use this to find minimal repro steps for parallelism issues in test suites. It isolates root causes of order dependence and provides verifiable fixes that improve test stability without overfitting to a single CI run.

The best way to fix flaky tests without overfitting to a single CI run is to generate actionable root-cause hypotheses based on broad runtime context, logs, and configuration. This approach ensures recommended mitigations are minimal and verifiable across environments.

Tests fail in CI due to resource contention and fixture isolation when parallel execution environments differ from local setups. Analyzing fixture usage and runtime logs isolates the contention and provides clear owner notes for resolving the instability.