condition-based-waiting

Eliminate flaky tests by replacing arbitrary sleep delays with condition polling. This ensures tests wait for actual state changes rather than fixed delays, producing deterministic and consistent results across environments.

Condition polling continuously checks a boolean state or predicate at configured intervals until a timeout is reached. It fixes intermittent failures by synchronizing test execution on actual events instead of relying on unreliable timing guesses.

Replace setTimeout in end-to-end tests by implementing a waitFor helper with a condition getter and descriptive message. Configure reasonable timeouts to wait for actual state changes instead of fixed delays.

Yes, condition-based waiting applies to unit, integration, and end-to-end tests. It stabilizes tests relying on timing, asynchronous events, external tool ticks, or parallel execution where fixed delays cause race conditions.

The best way to wait for a specific number of events is using event helpers with custom predicate matchers. This ensures the test waits for the required event count and provides explicit timeout errors for clear failure reasons.

Tests fail intermittently because fixed delays cause race conditions when execution speeds vary across environments. Replacing guesswork timeouts with deterministic condition polling ensures tests wait for actual state changes and produce consistent results.