condition-based-waiting

Replace fixed timeouts with condition-based waiting that polls for actual state changes. This approach waits for specific conditions—like element visibility or API completion—rather than sleeping arbitrary durations, making tests stable across varying network and system speeds.

Sleep delays pause for a fixed duration regardless of whether the target condition is met, causing flakiness in slow environments. Condition-based waiting continuously checks for the actual condition and returns immediately when satisfied, eliminating unnecessary delays and race conditions.

Implement polling with helper waiters that check for specific conditions—element visibility, API responses, state changes, or event counts—within a defined timeout. The Skill provides waitFor, waitForEvent, waitForEventCount, and waitForEventMatch helpers to handle these patterns.

Yes. Condition-based waiting applies to any async workflow with timing dependencies or race conditions. It works for event-driven state changes, CI pipelines, and multi-threaded tasks by waiting for observable conditions to stabilize rather than guessing durations.

No. Condition-based waiting includes timeout management that throws a defined timeout error if the condition isn't met within the specified duration, preventing infinite waits and providing clear failure signals in tests.