Wait for observable readiness instead of sleeping

Poll the service or state the test actually needs, with a bounded timeout and useful failure output.

Prompt

Evaluate and apply this CI technique to my repository: Wait for observable readiness instead of sleeping.

Poll the service or state the test actually needs, with a bounded timeout and useful failure output.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/poll-readiness.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How companies used this technique

Read what each company changed and follow the original sources.

Poll the condition the test actually needs

MongoDB vector tests replaced fixed sleeps with polling. Couchbase used its Search service ping for startup.

Use it when: Repeated waits dominate an eventual-consistency integration suite.
Before applying it: Validate content or version readiness and fail clearly on a deadline; a matching count alone can miss same-size updates.

Wait until the database answers a query

StarSling’s agent replaced MSSQL’s TCP probe with sqlcmd SELECT 1 and let Compose --wait coordinate readiness. ClickHouse received a native query healthcheck too. This adapts the fixed-sleep recipe to semantic health checks and redundant polling.

Use it when: Integration tests race database startup or wait through conservative startup delays.
Before applying it: Probe the actual operation required by tests and fail on timeout. Follow-up #15895 awaited asynchronous deletions exposed by faster storage.

Wait for readiness with a bounded poll

Stripe sync-engine replaced fixed sleeps with a waitFor helper that polls a condition, returns as soon as it holds and throws when the deadline passes. Stripe Android’s UI test waits for a snackbar to hide only when it overlaps the element it needs to tap.

Use it when: Tests sleep for a fixed period before checking an asynchronous result.
Before applying it: Probe the capability the next step needs; an open port can come before migrations or workers are ready. Keep tests that intentionally verify timeouts unchanged.

Wait for the connection the test actually uses

SubmitQueue's MySQL healthcheck used localhost, which selected a Unix socket, while its clients connected over TCP and could start too early. The fix probes 127.0.0.1 and removes the second retry loop from test setup. OPT17 is adapted to a readiness probe that checked the wrong interface.

The author reproduced the local startup errors, then reported four consecutive orchestrator passes and three gateway passes after the fix. Source

Use it when: Containers report healthy before the network interface used by the tests accepts connections.
Before applying it: Probe the same protocol, authentication and readiness condition the consumer uses, keep a bounded startup timeout with logs, and keep any retries until the new probe is proven.

How companies used this technique

Poll the condition the test actually needs

Wait until the database answers a query

Wait for readiness with a bounded poll

Wait for the connection the test actually uses

Related techniques

Complete the fixture before its timeout fires

Shorten deliberate test waits

Balance test work across shards

Company Playbooks

Related guides

Cut repeated test setup

Shard tests across parallel jobs

Diagnose slow tests in CI

Optimize Playwright tests

Make Vitest run mode explicit