Loading challenge...
Poll-Until-Ready Job
Start a job and poll its status to ready or failed instead of sleeping for a fixed duration
What you will learn
- Implement poll-until-ready instead of brittle fixed-duration sleeps when automating async workflows
- Assert on a stable data-* state attribute (data-status) rather than transient visible text
- Handle terminal branches explicitly — both the success (ready) and failure (failed) outcomes
Poll-Until-Ready Job
Kick off a background job and poll its status until it transitions to ready (or failed) — never sleep for a fixed duration
Clicking Start job issues a POST /api/lab/job that returns a signed jobId. The job then walks through queued → processing → ready based purely on elapsed time (sealed in the jobId), so the timing is deterministic but not instant.
Tick Seed failure before starting to make the job end in failed instead — practise handling the unhappy branch.
Run a Job
Start, then poll every 700ms until terminal
Status: idle
Testing Tips
Automation hints
- ✓ Click
#job-start, then poll — do NOTpage.waitForTimeout(10000); fixed sleeps are flaky and slow - ✓ Use Playwright
expect.poll/toPasson#job-statusand assert itsdata-statusattribute reachesready - ✓ Read terminal state from
#job-status[data-status](not the visible text) — it cyclesqueued → processing → ready - ✓ Check
#seed-failfirst to drive thefailedbranch, then assert#job-errorrenders and#job-resultnever appears - ✓ The status is derived server-side from a signed
jobIdatGET /api/lab/job?id=…(Cache-Control: no-store) — you cannot shortcut it from the client
