condition-based-waiting

Condition-based waiting replaces fixed delays with polling that checks for a specific condition before proceeding. Instead of `await sleep(5000)`, you evaluate a condition repeatedly until it's true or a timeout expires, eliminating race conditions and flaky timing dependencies in asynchronous tests.

Use condition polling to wait for events, state readiness, or resource availability instead of arbitrary delays. This approach reduces flakiness by allowing tests to proceed as soon as the actual condition is met, rather than waiting a fixed duration that may be too short or wastefully long.

Yes. Domain-specific helpers like waitForEvent, waitForEventCount, and waitForEventMatch provide targeted polling for common async test scenarios, allowing you to wait reliably for events to fire, accumulate to a threshold, or match expected criteria before assertions.

Look for hardcoded `setTimeout` or `sleep` calls, tests that occasionally fail under load, or assertions that race against asynchronous operations. Replace those arbitrary delays with condition polling to stabilize flaky behavior and reduce test execution time.

Timeout-based waiting pauses execution for a fixed duration regardless of whether the expected state has arrived. Condition polling checks repeatedly whether a condition is satisfied and proceeds immediately when true, making tests faster and more reliable without guessing required delay duration.

The Skill provides a generic waitFor utility with configurable timeout and periodic condition evaluation built in, requiring no additional dependencies. It includes ready-to-use helpers for common patterns, making it self-contained for async test stabilization.