Integration testing
Use staging to prove both the API contract and your operational behaviour before requesting production access.
Test setup
- Use staging credentials and resolve staging response and subscription type IDs.
- Register test customers with recognisable external references.
- Configure a staging webhook receiver over HTTPS.
- Use the Responder Simulator in the staging AURA portal to progress callouts through dispatch, arrival, completion, and closure.
Staging callouts are not closed by a live control room. The Responder Simulator is how you progress and close them, and each step emits the same webhook event as a live response. See Testing with the Responder Simulator for the step-to-event mapping.
Core scenarios
Product-specific scenarios
For People Protect, test poor GPS accuracy, background/foreground movement, an expired subscription, and customer cancellation.
For Property Protect, test an unknown external reference, a deleted Fixed Location, CSV validation and callbacks, and an alarm for a site that already has an active callout.
For white-label, test first launch, authentication, subscription choices, panic and tracking, support links, notifications, deep links, and store-ready builds for every enabled brand and environment.
Evidence for go-live
Keep a short test record containing the scenario, timestamp, environment, request correlation or resource IDs, observed result, and owner. Never paste tokens, secrets, full customer profiles, or payment data into the record.
Continue with Production readiness and the go-live checklist for your product.
