UI workflow
Scenario
Async File Processing
Upload a file, then poll a real job-status endpoint until it resolves (~5s) — complete about 75% of the time, failed the rest, requiring a retry. No fixed sleeps will reliably pass this one.
How this works
- · Uploading creates a job whose outcome (succeed or fail, ~75%/25%) is decided once at creation time, not re-rolled on every poll — so the result stays consistent no matter how many times you check it.
- · The status page polls a real endpoint; a job reports "processing" for exactly 5 seconds of wall-clock time from creation before resolving to complete or failed — a fixed short sleep in a test will still see "processing".
- · Retrying a failed job re-rolls both the timer and the outcome from scratch, exactly like re-submitting a new job would.
What you'll practice
- Polling an endpoint until a job resolves, instead of a fixed sleep — processing takes exactly 5 seconds
- A progress bar that updates from real percentages, not a fake CSS animation
- A ~25% failure rate requiring a "Retry" action, and re-polling after retrying
- Seeding an already-resolved job via API (see the Test Data page) to skip the wait entirely in a real test
- 1 Upload →
- 2 Status