When should I still use an arbitrary timeout?

Arbitrary timeouts should only be used when testing actual timing-dependent behavior, such as verifying a debounce or throttle interval, and should always be documented.

What is a flaky test?

A flaky test is a test that provides inconsistent results (passing and failing) without any code changes, usually caused by race conditions or environmental timing differences.

Why is polling better than using sleep or setTimeout?

Polling waits for the exact moment a condition is met, whereas sleep waits for a fixed duration that might be too short (causing failure) or unnecessarily long (wasting time).

How does this skill help with CI/CD?

By eliminating timing guesses, tests become more resilient to the slower hardware or shared resources often found in CI environments, leading to more stable build pipelines.

Condition-Based Waiting

Name: Condition-Based Waiting
Author: Activer007

byActiver007

보안 및 테스팅

Eliminates flaky tests by replacing arbitrary timeouts with smart condition polling for actual state changes.

소개

Condition-Based Waiting is a specialized Claude Code skill designed to resolve race conditions and timing dependencies in test suites. It provides patterns and implementation logic to replace fragile sleep and timeout calls with dynamic polling mechanisms that wait for specific events, state changes, or file existence. By ensuring tests wait for actual conditions rather than arbitrary time intervals, this skill significantly improves test reliability, reduces execution time in CI/CD pipelines, and eliminates inconsistent pass/fail behavior across different environments.

주요 기능

Replaces fragile sleep/timeout calls with smart condition polling
Generic waitFor implementation with customizable intervals and timeouts
Domain-specific patterns for events, state machines, and file systems
Guidance on avoiding common pitfalls like CPU-heavy polling or stale data
Documentation patterns for legitimate timing-based test scenarios
0 GitHub stars

사용 사례

Fixing flaky integration tests that fail intermittently in CI environments
Synchronizing tests with asynchronous state changes or event emitters
Reducing test suite execution time by eliminating unnecessary wait durations

소개

주요 기능

Replaces fragile sleep/timeout calls with smart condition polling
Generic waitFor implementation with customizable intervals and timeouts
Domain-specific patterns for events, state machines, and file systems
Guidance on avoiding common pitfalls like CPU-heavy polling or stale data
Documentation patterns for legitimate timing-based test scenarios
0 GitHub stars

사용 사례

Fixing flaky integration tests that fail intermittently in CI environments
Synchronizing tests with asynchronous state changes or event emitters
Reducing test suite execution time by eliminating unnecessary wait durations