Remove readiness sleeps from browser tests
A fixed delay is either too short on CI or unnecessarily long locally.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Browser testing · Asynchronous behavior
Estimated field mix
- Quality engineering100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional web team reruns red builds until they pass. Shared clocks, leaked state, and unawaited work make failures hard to trust.
Setup prerequisites
- Create a small local application with three deliberately flaky tests using synthetic data and local endpoints.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Wait for a specific observable ready state.
- Bound the wait and report the missing condition.
- Handle a failed request without waiting indefinitely.
Implementation constraints
- Do not increase global timeouts to mask failures.
Verification to include
- Run with fast and delayed local responses.
- Return an error and verify a useful bounded failure.
Deliverables
- Condition-based browser waits.
Rollout and recovery
Replace sleeps incrementally; keep traces for failures during adoption.
Value of the work
For the engineer: Practice controlled diagnosis, isolation, and test reliability measurement.
For the team: Recover useful failure signals and reduce blind reruns without hiding product defects.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.