test-flakiness

Flaky test detection aggregates pass/fail outcomes across multiple CI runs to identify intermittent failures without code changes. It reads JUnit XML or plain-text CI logs, builds per-test result history, and classifies likely failure causes like timing issues or order dependencies.

Intermittent failures without code changes indicate flaky tests caused by timing or async issues, order dependency, random seed usage, resource leaks, external state, floating-point comparisons, or scene and prefab load races. Analyzing CI log history isolates these non-deterministic behaviors.

Yes, bulk scanning of available test result artifacts is supported. It reads existing CI logs and regression-suite quarantine sections to determine which tests fluctuate between pass and fail, then updates quarantine report files with user approval.

The best way to quarantine flaky tests is to classify them by root cause, recommend whether to quarantine immediately, investigate soon, or monitor, prepare a flakiness report, and update the quarantine registry with explicit user approval.

Yes, it processes Jest JUnit XML output and plain-text CI logs for regression testing. It builds per-test result history from these formats to identify intermittent failures and classify likely causes like timing issues or resource leaks.

Detection relies on having sufficient CI run history and accessible test result artifacts. It classifies likely failure causes and recommends remediation, but updating quarantine report files and applying fixes requires explicit user approval and intervention.