condition-based-waiting

Replace arbitrary delays like Task.Delay with condition polling using WaitForAsync, which waits for actual state changes instead of guessing timing. This eliminates race conditions in asynchronous tests by polling a specific condition—event occurrence, state change, count increment, or file existence—until it becomes true or timeout occurs, ensuring deterministic test behavior.

Use a generic polling mechanism that accepts a condition function, timeout, and poll interval. WaitForAsync evaluates your condition repeatedly at short intervals until it returns true or the timeout expires, with explicit error messages on failure. This approach works across unit and integration tests for events, state transitions, and asynchronous operations.

Yes. Condition-based polling replaces Task.Delay by actively checking for state changes rather than sleeping for a fixed duration. It includes cancellation support, configurable timeouts and poll intervals, and descriptive timeout errors, making tests more reliable and faster than arbitrary delays.

Implement condition polling with clear timeout handling and descriptive error messages. Instead of hoping a fixed delay is long enough, poll for the actual condition your test needs—such as an event being fired or a counter reaching a value—and fail explicitly with the condition description if the timeout is exceeded.

Sleep delays are arbitrary and cause flaky tests because they guess at timing; waiting for conditions polls for actual state changes and passes immediately once the condition is met. Condition polling is faster, more reliable, and eliminates race conditions by ensuring your test proceeds only when the required state actually exists.