# Zavvion Events Commercial Lite MVP - Test Data Setup Checklist

The test lead or human architect should prepare this data before assigning testers.

## Accounts

- [ ] Public visitor: no login.
- [ ] Customer 1 with no orders.
- [ ] Customer 2 with at least one completed order.
- [ ] Organiser A with approved status.
- [ ] Organiser B with approved status for tenant isolation tests.
- [ ] Platform organiser support account.
- [ ] Platform admin account.
- [ ] Optional scanner/check-in account if scanner is included in the deployment.

## Events

- [ ] Reserved-only event with two reserved sections.
- [ ] Non-reserved-only event with at least three ticket types.
- [ ] Mixed event with two reserved sections and one non-reserved section.
- [ ] Event with uploaded customer-facing seat-map PDF/image.
- [ ] Event without uploaded customer-facing seat-map PDF/image.
- [ ] Event with donations enabled.
- [ ] Event with donations disabled.
- [ ] Event with merchandise enabled if merchandise is in scope.
- [ ] Event with merchandise disabled.
- [ ] Past-date attempt for validation testing.

## Venues And Seat Maps

- [ ] Venue with at least two reusable seat maps.
- [ ] Reusable seat map A: reserved section only.
- [ ] Reusable seat map B: mixed reserved and non-reserved sections.
- [ ] Seat map with uploaded PDF/image.
- [ ] Seat map with no uploaded PDF/image.
- [ ] Reserved section names that prove section tabs work, for example Sec RR and Sec WW.
- [ ] Non-reserved section, for example Stalls.

## Ticketing

- [ ] Reusable catalogue types: Adult, Child, Senior, Student, VIP, Carer/Companion, Family.
- [ ] Event-level price, quantity, and max/order for each allocated ticket.
- [ ] Removed/unallocated ticket type to prove it does not appear publicly.
- [ ] Section-specific ticket mappings for at least one event.
- [ ] Duplicate allocation attempt data.

## Payment

- [ ] Stripe test publishable key configured.
- [ ] Stripe test secret key configured on server.
- [ ] Stripe webhook signing secret configured.
- [ ] Connected organiser account with test readiness.
- [ ] Test card for success.
- [ ] Test card for failure.
- [ ] Test event/order for duplicate webhook replay.

## Security

- [ ] Known object IDs for organiser A and organiser B.
- [ ] Two customer orders for IDOR tests.
- [ ] XSS label test strings, stored in test notes only.
- [ ] Invalid upload samples: oversized file, wrong MIME file, renamed executable, malformed image/PDF.