condition-based-waiting

Replace arbitrary delays with condition-based waiting that polls for actual state changes. Instead of setTimeout or sleep calls, use waitFor conditions to check for specific events, state transitions, or file existence, ensuring deterministic test results across all environments.

Condition-based waiting replaces guesswork timing by monitoring for actual state changes using polling. It works across unit, integration, and CI environments, supporting patterns like waitForEvent and waitForEventCount with configurable timeouts and 10ms polling intervals.

Yes. This approach eliminates race conditions by waiting for precise state changes rather than fixed delays. It applies to tests relying on asynchronous operations, event emissions, count changes, and file operations, converting intermittent failures into reliable, deterministic tests.

Replace each setTimeout with a waitFor condition that checks for the actual state change you're waiting for—such as waitForEvent for event emissions, waitForEventCount for counter changes, or waitForEventMatch for specific conditions, with configurable timeout and deterministic polling.

CI failures often stem from timing assumptions that vary across environments. Condition-based waiting solves this by polling for real state changes instead of arbitrary delays, achieving consistent pass rates by replacing environment-dependent timing with deterministic state verification.