Delivery flows combine location, order state, timing and background execution. A controlled route makes regressions easier to reproduce before field testing.
Create a safe test order
- Use a staging account and non-production order.
- Choose test addresses that contain no customer data.
- Define expected pickup, en-route, near-destination and arrival states.
- Keep a server-side trace ID for the complete run.
Run the route
- Start outside the pickup area.
- Cross the pickup geofence and confirm the expected state.
- Continue at a fixed speed with a screen-off interval.
- Approach the destination and compare arrival timing with the acceptance criteria.
Check failures deliberately
- Pause the route to simulate a stationary courier.
- End the mock session to see how stale location is handled.
- Deny background permission in a separate run.
- Confirm the UI explains delayed or unavailable tracking without inventing a precise position.
Common questions
Should this be used on live customer orders?
No. Use authorized test accounts and staging or synthetic orders.
What should I log?
Log coordinates, timestamps, reported accuracy, app state, order state and relevant server events.
Use responsiblyReceiving apps can detect or reject mocked locations. Follow applicable laws and third-party terms; do not use FlashGo to mislead others or bypass restrictions.