preen-test-flakiness

To fix flaky tests in a CI/CD pipeline, you analyze test files to detect anti-patterns like time-based waits and retries. This skill pinpoints intermittent failure sources and replaces nondeterministic elements with stable, condition-based synchronization mechanisms.

Intermittent test failures without code changes are typically caused by nondeterministic elements such as race conditions, fragile sleep calls, and non-deterministic data. These anti-patterns create timing dependencies that cause unpredictable CI/CD build results.

You replace sleep and setTimeout calls in automated tests by implementing condition-based waits. This involves refactoring test files to use stable waiting and synchronization mechanisms that wait for specific states rather than arbitrary time durations.

Yes, this skill can detect race conditions in your test suites. It proactively analyzes test files to identify common flaky test patterns, focusing specifically on resolving race conditions, time-based waits, and retry mechanisms.

No specific testing frameworks are required as dependencies. The tool operates by analyzing your test files directly to identify flake sources and implement stable waiting mechanisms, making it applicable to test suites exhibiting intermittent failures across various setups.