Flaky Test
Run the same commit five times: it sometimes passes and sometimes times out. Check waiting conditions and shared accounts first; do not hide red with endless retries.
↳Repeatedly run the same commit first to rule out changing code.
Confirm unchanged code, changing result: Passing and failing on the same version and case points to an uncontrolled test, environment, or concurrency condition. A case that always fails is more like a reproducible defect and needs a different path.
Look for observable sources of variance: Check whether the test waits for a true completion signal, cases share an account or port, data remains, or CI differs from local. Record failure frequency and logs, then fix the cause.
You can say this to an AI Agent
This login test times out intermittently on the same commit. Run it repeatedly and retain each log, inspect wait conditions, shared accounts, and test data; find a reproducible source of variance before merely increasing retries.
Select page elements for precise AI edits
Click a button, text, or card, note the change, then copy its exact location to AI.
Open Selector Pro website↗