Shorten deliberate test waits

Reduce waits whose timing requirements are known, preserving the timeout or consistency behavior the test is intended to cover.

View in Markdown

Prompt

Evaluate and apply this CI technique to my repository: Shorten deliberate test waits.

Reduce waits whose timing requirements are known, preserving the timeout or consistency behavior the test is intended to cover.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/shorten-proven-test-waits.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.

Shorten deliberate sleeps in tests and examples

The Claude Agent SDK's error-handling example, which CI runs on every pull request, asked for a 60-second sleep to trigger a 10-second timeout. The change asks for 5 seconds and times out at 3, so the timeout path still runs.

The PR's estimate is that the shorter sleep removes 50+ seconds from the examples job; the same PR also raises that step's timeout. Source

Use it when: A test or a CI-run example sleeps for a fixed time only to exercise a timeout or a slow path.
Before applying it: The sleep and the timeout it triggers shrink together, so the timeout branch still runs and is asserted.

Shorten only waits whose consistency is already proved

Chroma reduced 80 fixed 2-second waits, from three call sites, to 200 milliseconds; Couchbase reduced per-operation waits while adding a service readiness probe.

Chroma’s PR estimates the Run Chroma tests step drops from 160 seconds of sleeping to about 16 seconds. Source

Use it when: A service exposes no usable readiness predicate and repeated conservative waits dominate tests.
Before applying it: Prefer a real completion signal; retain coverage and stress slow runners before choosing a lower bound.

How companies used this technique

Shorten deliberate sleeps in tests and examples

Shorten only waits whose consistency is already proved

Related techniques

Complete the fixture before its timeout fires

Wait for observable readiness instead of sleeping

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