fixing-flaky-tests
1
总安装量
1
周安装量
#49681
全站排名
安装命令
npx skills add https://github.com/rileyhilliard/claude-essentials --skill fixing-flaky-tests
Agent 安装分布
amp
1
opencode
1
kimi-cli
1
github-copilot
1
antigravity
1
Skill 文档
Fixing Flaky Tests
Target symptom: Tests pass when run alone, fail when run with other tests.
Diagnose first
Test passes alone, fails with others?
â
ââ Same error every time â Shared state
â ââ Database, globals, files, singletons
â
ââ Random/timing failures â Race condition
â ââ Use `condition-based-waiting` skill
â
ââ Resource errors (port, file lock) â Resource conflict
ââ Need unique resources per test/worker
Quick diagnosis:
- Run failing test 10x alone – does it always pass?
- Run failing test 10x with the suite – same error or different?
- Check error message – mentions port/file/connection?
Shared state (deterministic failures)
Tests pollute state that other tests depend on. Fix by isolating state per test.
| State Type | Isolation Pattern |
|---|---|
| Database | Transaction rollback, savepoints, worker-specific DBs |
| Global variables | Reset in beforeEach/afterEach |
| Singletons | Provide fresh instance per test |
| Module state | jest.resetModules() or equivalent |
| Files | Unique paths per test, temp directories |
| Environment vars | Save/restore in setup/teardown |
Database isolation (most common):
# Python: Savepoint rollback - each test gets rolled back
@pytest.fixture
async def db_session(db_engine):
async with db_engine.connect() as conn:
await conn.begin()
await conn.begin_nested() # Savepoint
# ... yield session ...
await conn.rollback() # All changes vanish
// Jest: Reset mocks between tests
beforeEach(() => {
jest.clearAllMocks()
jest.resetModules() // Clear module cache before test
})
afterEach(() => {
jest.restoreAllMocks() // Restore spied functions
})
See language-specific references for complete patterns.
Race conditions (random failures)
Tests don’t wait for async operations to complete.
Use the condition-based-waiting skill for detailed patterns on:
- Framework-specific waiting (Testing Library
findBy, Playwright auto-wait) - Custom polling helpers
- When arbitrary timeouts are acceptable
Quick summary: Wait for conditions, not time:
// Bad
await sleep(500)
// Good
await waitFor(() => expect(result).toBe('done'))
Resource conflicts (port/file errors)
Multiple tests or workers compete for same resource.
Worker-specific resources:
# Python pytest-xdist: unique DB per worker
@pytest.fixture(scope="session")
def database_url(worker_id):
if worker_id == "master":
return "postgresql://localhost/test"
return f"postgresql://localhost/test_{worker_id}"
// Jest/Node: dynamic port allocation
const server = app.listen(0) // OS assigns available port
const port = server.address().port
File conflicts:
import tempfile
@pytest.fixture
def temp_dir():
with tempfile.TemporaryDirectory() as d:
yield d
Language-specific isolation patterns
| Stack | Reference |
|---|---|
| Python (pytest, SQLAlchemy) | references/python.md |
| Jest / Testing Library | references/jest.md |
| Playwright E2E | references/playwright.md |
Verification
After fixing, verify the fix worked:
# Run the specific test many times
pytest tests/test_flaky.py -x --count=20
# Run with parallelism
pytest -n auto
# Jest equivalent
jest --runInBand # First verify serial works
jest # Then verify parallel works