UI workflow
Scenario
Support Ticket Submission
Submit a support ticket with an optional file attachment, then track it — and close it — from a My Tickets list. Covers the validation-error path too, not just the happy path.
How this works
- · Submission requires a subject and priority; missing them renders real inline validation errors rather than a generic failure banner. The file attachment is optional and validated on both the client and server.
- · Tickets are stored in your session cookie — My Tickets reads that same list, so closing a ticket there is immediately reflected everywhere else that reads it.
- · No email or real ticketing backend is simulated beyond this — it is deliberately just the two pages plus the cookie-backed store.
What you'll practice
- A form with an optional file attachment, including a validation error path (subject required, file size cap)
- A list view of everything you've submitted, with status badges
- A "close ticket" action that changes state you can assert on afterward
- Seeding several tickets at once via API (see the Test Data page) instead of submitting the form repeatedly
- 1 Submit →
- 2 My Tickets