barrier-concurrency-testing

Instead of setTimeout (flaky) or sleep (slow), use barriers to pause execution at exact interleave points. The test controls when each concurrent operation proceeds, making race condition tests deterministic and reproducible on every run.

When to use: Testing concurrent operations, flush conflicts, parallel mutations, race windows between read and write, lock contention scenarios, any code where timing affects correctness.

When not to use: Sequential-only code, simple unit tests, UI components, read-only operations, code with no concurrency concerns.

장벽과 지연된 약속을 사용한 결정적 경쟁 조건 테스트. 불안정한 setTimeout 기반 타이밍 테스트를 재현 가능한 인터리빙 제어로 대체합니다. 출처: apankov1/quality-engineering.