# Event registration browser and device matrix

Choose cells from attendee evidence and product support. Use synthetic attendee data and approved non-chargeable test flows. Never put real attendee or payment data in this sheet.

| Browser / version | OS / version | Real device or emulation | Viewport / input | Locale | Event URL / ticket type | Autofill and fields | Validation recovery | Consent | Submit / record outcome | Hosted checkout handoff | Confirmation | Status / tester / date | Defect ID / owner |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Example: Safari / current supported | iOS / supported | Physical phone | Portrait / touch | en | Event page / RSVP | Verify | Verify | Verify | Verify | Not applicable | Verify | Not run / name / date | — |
| | | | | | | | | | | | | | |
| | | | | | | | | | | | | | |

## Critical path for each selected cell

1. Open official event page and confirm ticket action is usable.
2. Choose a ticket or RSVP; try autofill, date/select controls, keyboard and local characters.
3. Leave a required field empty, read the error, correct it and verify earlier entries remain.
4. Review consent choices, submit once and confirm the intended server-side outcome.
5. Follow approved no-charge checkout or confirmation flow; record provider boundary.
6. Repeat the failed cell after a fix and record the actual result.

## Defect record

- URL and event edition:
- Browser, OS, device and locale:
- Exact steps, expected and observed result:
- Impact: cosmetic / inconvenient / blocks registration or confirmation:
- Redacted evidence and owner:
- Recheck status and date:

A browser compatibility summary helps choose what to inspect; it does not certify the complete checkout.