Integration guide
How test purchases stay separate
Organisers test through their normal dashboard. Test and Live use the same app and database, with separate event copies, orders and inventory.
Separate resources
Use the main app and existing Supabase database. Enable single-project testing, apply its migration and configure a Paystack Test secret. Your normal dashboard creates hidden [TEST] copies of assigned events. Test inventory and orders stay separate from real sales.
Use your main API address with a Test key for integrated testing. Your backend uses Test keys; Naija Tickets checks their permissions and creates private test records automatically. The older Partner Demo has its own setup and is optional.
Acceptance checklist
Read the deployment runbook and readiness report. Rehearse migrations in a disposable database, then review the exact pending migration list. Apply additive migrations to the existing database; never reset it.
From the external demo, authenticate, retrieve a marked Test event, select tickets, complete Paystack TEST payment, verify the session/order on the server and return to the demo. Repeat free and group purchases; test claim uniqueness, individual QR and one-time entry, cancellation, expiry, revocation and refunds.
Confirm the public widget at mobile/desktop widths, keyboard navigation and blocked third-party cookies. Configure a durable receiver, test altered/replayed signatures and observe an actual scheduled delivery/recovery. Record which checks actually ran. Email remains deferred.
What is still pending here
A completed real Paystack Test purchase/return, durable public webhook inbox and scheduled-delivery acceptance must be checked on the deployed app. Local mocked/embedded database tests and a successful build do not substitute for them.
Use /developers/readiness for the operator checklist. Do not enable Live flags merely because the source is deployed. A real settlement, physical device/camera test and security/throughput review remain separate operational checks.