Add scenarios for the failure paths nobody can reproduce by hand
Timeouts, server errors, and empty states made reproducible on demand instead of only in production.
The ticket
Add mock scenarios for the failure paths that cannot be reproduced by hand: timeouts, server errors, and empty results.
Acceptance criteria
- A scenario exists for each failure mode the surface can hit
- A test asserts the interface behaviour for each
- Screenshots of the visual states are attached
- Scenarios are selectable without a code change
What lands as proof
A screenshot per failure state and a test per scenario, which together are the first proof these paths render at all.
Why teams defer it
- Reproducing a timeout by hand means breaking something on purpose, which nobody wants to do on a shared environment.
- Empty and error states get designed last and verified never, so they are usually the first thing a new user sees go wrong.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: add mock scenarios for the failure paths that cannot be reproduced by hand: timeouts, server errors, and empty results. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means a test per scenario, plus screenshots for the visual states, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.