How to test food delivery order tracking on a real phone
Run these food delivery order tracking test cases on phones real Indian users own — not an emulator. The cases below cover the happy path and the edges that only break on a real device: OEM battery savers on MIUI and ColorOS, autofill and OTP handling, reboots, poor networks and app-switching. Download them as CSV or Excel, run them yourself, or have 99tests testers run them on real phones and send back a verified pass/fail report in 3 business days. These three matter most on a real phone:
Call the partner through the masked number — Masked calling runs over the real carrier network and needs a real phone call.
Status notifications while the app is in the background — Push delivery to a backgrounded app depends on the real phone and its OS.
Partner's phone is switched off or busy — How the masked line handles unreachable phones depends on real carriers.
Order tracking keeps a hungry customer informed from the moment the restaurant accepts the order to the knock at the door: statuses, a live map, an ETA and a way to reach the delivery partner. It fails in the field when battery savers on budget phones hold back the Arrived alert, when masked calls break on dual-SIM phones, and when GPS drift in dense lanes and high-rises puts the partner at the wrong gate.
36 test cases8 release-blocking (P1)15 need a real phoneUpdated 2026-10-29
From the reviews. Wrong or out-of-date information was food delivery apps' top malfunction (7 of 22 malfunction reviews), ahead of crashes and freezes (5).
Place a food order and stay on the tracking screen
Watch each status change: confirmed, preparing, picked up, on the way
Receive the food and wait for the Delivered status
Open My orders
Expected: Each status appears once, in order, with its time in IST, and the order moves from active to past orders after delivery.
FD-02
Live map shows the partner and the route
P2functional
Open the tracking screen after the partner picks up the order
Watch the partner's marker for two or three minutes
Pinch to zoom out, then tap the recentre button
Expected: The marker moves along roads towards your pin without jumping across buildings, and recentre fits both the partner and your location on screen.
FD-03
ETA updates at each stage
P2functional
Note the ETA shown right after placing the order
Note it again when a partner is assigned and when the food is picked up
Compare it with the actual delivery time
Expected: The ETA is revised at each stage, never shows zero or a negative time while the food is still on the way, and switches to a running late message if it slips.
FD-04
Partner details appear once a partner is assigned
P2functional
Place an order and wait on the tracking screen
Look at the partner card when the status changes to assigned
Expected: The card shows the partner's name with Call and Chat buttons. The partner's personal phone number is not shown anywhere.
FD-05
Call the partner through the masked number
P1functionalreal phone
Once a partner is assigned, tap Call on the tracking screen
Let the call connect and talk to the partner
Check the number shown in your phone's call log
Expected: The call connects to the partner, and the call log shows the masked or virtual number, not the partner's personal number.
Why a real phone: Masked calling runs over the real carrier network and needs a real phone call.
FD-06
Chat with the partner
P2functional
Tap Chat on the tracking screen and send a message such as Gate 2, tower B
Reply from the test partner app
Send a quick reply if the app offers them
Expected: Messages appear on both sides in the order sent, with times, and no phone numbers are shown in the chat.
FD-07
Status notifications while the app is in the background
P1functionalreal phone
Place an order, allow notifications, then press Home
Wait without opening the app until the order is delivered
Expected: A notification arrives for each key status, such as preparing, picked up, arriving and delivered, close to the time each one happens.
Why a real phone: Push delivery to a backgrounded app depends on the real phone and its OS.
Validation & negative6
FD-08
Restaurant rejects the order soon after it is placed
P1negative
Place a prepaid order at the test restaurant
Reject the order from the restaurant test panel
Look at the tracking screen and the notifications
Expected: The tracking screen says the restaurant cancelled the order, gives the reason if one was entered, and shows a refund initiated for the amount paid.
FD-09
Restaurant runs late with the food
P2negative
Place an order at the test restaurant
From the restaurant panel, keep it in preparing well past the ETA
Expected: The app shows a delay message and a new ETA instead of a frozen or expired timer, and offers help or contact options.
FD-10
Restaurant cancels after a partner is assigned
P2negative
Wait until a partner is assigned to your order
Cancel the order from the restaurant test panel
Look at the partner card and the Call button
Expected: The order shows as cancelled, the partner card with its Call and Chat buttons disappears, and refund details appear for a prepaid order.
FD-11
Restaurant marks an item unavailable after you order
P1negative
Place a prepaid order with three items
Mark one item unavailable from the restaurant test panel
Respond to any prompt the app shows
Expected: You are asked to accept the change or cancel, the bill drops by that item's price, and the partial refund amount is shown on the order.
FD-12
Order marked delivered but not received
P1negative
Mark a test order delivered from the partner app without handing it over
Open the order in the customer app
Look for a way to report that it was not received
Expected: The order screen offers a not received or help option on the order itself, and submitting it shows a reference and a status you can come back to.
FD-13
Partner's phone is switched off or busy
P2negativereal phone
Switch off the test partner's phone, or keep it busy on another call
Tap Call on the tracking screen
Expected: You hear or see a message that the partner cannot be reached, and the app suggests chat or help. No personal number is revealed.
Why a real phone: How the masked line handles unreachable phones depends on real carriers.
Edge cases7
FD-14
Refund status after a restaurant cancellation
P1edge
Have a prepaid UPI order cancelled by the restaurant
Open the order and go to the refund section
Reopen it after the refund is marked processed
Expected: The refund shows the amount, the original payment method, a status such as Initiated then Processed, and a reference you can match in the UPI app or bank statement.
FD-15
Cancelled cash on delivery order shows nothing to refund
P2edge
Place a cash on delivery order
Cancel it from the restaurant test panel
Open the order details
Expected: The order shows as cancelled with no amount due and no refund line, so the customer is not told to expect money back.
FD-16
Partner is reassigned mid-delivery
P2edge
Wait until a partner is assigned
Reassign the order to another partner from the test panel
Tap Call on the tracking screen
Expected: The new partner's name and map position replace the old ones, and Call reaches the new partner, not the previous one.
FD-17
Statuses arrive late or out of order
P2edge
From the test panel, send Picked up before Preparing for a test order
Then send Preparing again
Watch the tracking screen
Expected: The screen never moves back from a later status to an earlier one, and the timeline shows each status only once.
FD-18
Two orders active at once
P2edge
Place two orders from different restaurants a few minutes apart
Open tracking from the home screen banner
Wait for notifications from both orders
Expected: You can switch between both orders, each with its own map and ETA, and every notification names the restaurant or order it refers to.
FD-19
Delivery in a dense lane with look-alike buildings
P2edgereal phone
Save an address with the pin on your building in a dense neighbourhood
Place an order and follow the partner on the map as they arrive
Note whether the partner reaches the right gate without calling
Expected: The partner's marker ends at your pin, and the address text, landmark and pin all point to the same building.
Why a real phone: GPS drift between closely packed buildings only shows up at a real location.
FD-20
High-rise delivery with tower, floor and gate details
P2edgereal phone
Save an address with tower, floor, flat number and gate instructions
Order from a high floor of a tall building
Watch the map and status as the partner reaches the gate
Expected: Arrived shows when the partner reaches the gate, not while they are blocks away, and the tower, flat and gate details appear in the partner app.
Why a real phone: Indoor and high-rise GPS readings cannot be faked convincingly on an emulator.
Interruptions & network6
FD-21
Return to tracking after a long time in the background
P2interruptionreal phone
Open tracking, then use other apps for about twenty minutes
Return to the food app from recent apps
Expected: Status, ETA and map catch up to the current state within a few seconds, without first showing stale information as if it were live.
Why a real phone: Real Android background limits decide whether the app is paused or restarted.
FD-22
Tap a status notification after the app was killed
P2interruptionreal phone
With an order in progress, swipe the app away from recent apps
Wait for the next status notification
Tap the notification
Expected: The app opens straight to that order's tracking screen with the current status, not the home screen.
Why a real phone: Notification delivery to a killed app and its launch vary across OEM skins.
FD-23
Phone is in a metro dead zone when the order is picked up
P2interruptionreal phone
With an order in progress, enter an underground metro stretch or a lift
Stay offline while the order is picked up and on its way
Return to coverage and open the app
Expected: The screen catches up to the current status, and you do not get a burst of stale notifications for steps that are already over.
Why a real phone: Real dead zones and delayed push delivery cannot be reproduced on an emulator.
FD-24
Live map on a weak 2G or 3G signal
P2interruptionreal phone
Switch the phone to 2G or 3G, or stand in a weak-signal spot
Open tracking while the partner is on the way
Expected: Status text and ETA keep updating even if map tiles load slowly, and the screen says when the location was last updated instead of freezing.
Why a real phone: Real Jio, Airtel or Vi fallback to 3G or 2G is uneven, unlike throttling.
FD-25
Partner calls you while the tracking screen is open
P2interruptionreal phone
Keep the tracking screen open
Have the test partner call you through the masked line
Answer, end the call and return to the app
Expected: The call shows a masked number rather than the partner's own, and after the call the tracking screen is still open and up to date.
Why a real phone: Needs a real incoming carrier call while the app holds the screen.
FD-26
Call the partner from a dual-SIM phone with the registered number on SIM 2
P2compatibilityreal phone
Use a dual-SIM phone whose registered number is on SIM 2
Set SIM 1 as the default SIM for calls
Tap Call on the tracking screen
Expected: The app or the dialer lets you call from the registered number, or the masked line still connects. The call never fails without an explanation.
Why a real phone: Masked lines often check the calling number; SIM choice needs real dual-SIM hardware.
Device & OS4
FD-27
Out for delivery and Arrived alerts with battery saver on
P1compatibilityreal phone
On Xiaomi, Realme, Vivo or Oppo phones, turn on battery saver
Place an order, then swipe the app away from recent apps
Wait for the Out for delivery and Arrived notifications
Expected: Both notifications arrive before or as the partner reaches the door, with sound if the app's notification settings allow it.
Why a real phone: Each OEM battery saver restricts push and background work differently.
FD-28
Track a full delivery on a budget phone
P2performancereal phone
On a 3–4 GB RAM phone, keep the tracking screen open for the whole delivery
Note the battery level and how warm the phone is, before and after
Expected: The app does not restart, the map stays responsive, and the battery drop is in line with a navigation app used for the same time.
Why a real phone: Battery drain, heat and memory pressure only show up on real budget hardware.
FD-29
Ongoing notification or Live Activity follows the order
P3compatibilityreal phone
Place an order on Android, and on an iPhone if your app supports Live Activities
Lock the screen and watch the ongoing notification or lock-screen widget
Wait until the order is delivered
Expected: The lock-screen item shows the current status and ETA, updates as the order moves, and disappears or shows Delivered at the end.
Why a real phone: Lock-screen and ongoing notification behaviour differs by OEM skin and iOS version.
FD-30
Notifications denied for the app
P3compatibility
Deny the notification permission when the app asks
Place an order and keep the app open
Expected: The tracking screen still updates inside the app, and the app explains once, at a sensible moment, that status alerts are off and how to turn them on.
Security & privacy3
FD-31
Masked number stops working after delivery
P2securityreal phone
Call the partner through the app during delivery
After the order is delivered and the period your app sets has passed, redial from the call log
Expected: The call does not reach the partner, and you hear a message that the order is complete or that the number is no longer active.
Why a real phone: Needs real calls over the masked line before and after delivery.
FD-32
Shared tracking link shows only what is needed
P2security
Tap Share tracking and send the link to another phone
Open the link on that phone without logging in
Open it again after the order is delivered
Expected: The link shows status, ETA and map only, with no phone numbers, full address or order items, and it stops showing live location after delivery.
FD-33
Log out with an order in progress
P2security
Log out while an order is on its way
Log in as a different account on the same phone
Tap an older status notification from the first account
Expected: The second account sees no tracking for the first account's order, and the old notification opens the login or home screen, not the order details.
Accessibility & language3
FD-34
Use the tracking screen with TalkBack
P2accessibility
Turn on TalkBack and open an active order
Move through the status, ETA, partner card, Call and Chat
Wait for the status to change
Expected: Each item has a clear label, Call is read as Call delivery partner, and a status change is announced without you having to move focus.
FD-35
Tracking screen and alerts in Hindi
P2localization
Switch the app language to Hindi
Place an order and follow it until delivery
Read the statuses, delay messages and notifications
Expected: Statuses, delay and refund messages and notifications are all in Hindi without truncation, and times are shown in IST in one consistent format.
FD-36
Tracking at the largest font and display size
P3accessibility
Set font size and display size to the largest in phone settings
Open an active order's tracking screen
Expected: The status timeline and ETA wrap without overlapping, and the Call and Chat buttons stay visible above the map.
In the field
Where food delivery order tracking breaks on real phones
On Xiaomi, Realme, Vivo and Oppo phones with battery saver on, the Out for delivery and Arrived alerts come late or not at all once the app is swiped away.
Masked calls fail when the phone's default calling SIM is not the registered number, and the customer only hears an error tone.
In dense lanes and high-rises, GPS drift puts the partner's marker or the Arrived status at the wrong building or gate.
After a lift or metro dead zone, the app replays every missed status as a burst of notifications, or shows a stale map as if it were live.
Restaurant edits and cancellations update the status but not the bill, so the partial refund is missing or shows the wrong amount.
ETAs count down to zero and stay there while the food is still on the way, instead of saying the order is running late.
Run these 36 cases on real phones
They fit the Standard package: 10 × 45-minute sessions on 4 phones or browsers of your choice, up to ~50 cases, ₹18,999 + GST ($249), verified report in 3 business days.
The 8 P1 cases alone fit Starter (₹9,999 + GST).
Download the CSV, pick the package at checkout and upload the file with your build. Testers run them on their own phones, on Jio, Airtel and Vi.
How do you test food delivery tracking without a real delivery every time?
Use a test restaurant, a test panel and a test partner account on a second phone, so you can accept, delay, edit, reassign and cancel orders on demand. Push statuses in normal and unusual orders and watch the customer app. Keep a few real deliveries for GPS accuracy, masked calls and notifications, which a test panel cannot fake.
Why do delivery notifications fail on some Android phones?
Many phone makers ship battery savers that stop background work and delay push messages once an app is swiped away or left unused. Behaviour differs across Xiaomi, Realme, Vivo, Oppo and Samsung skins, and can change with OS updates. Test with battery saver on and the app swiped away, and note how late each alert arrives.
What should a tester check in masked calling?
That calls connect in both directions without showing either side's personal number, including in the call log. Check what happens when the partner is unreachable, when the customer's registered number is on the second SIM, and after delivery, when the masked line should stop connecting. Also check that a reassigned order calls the new partner.
Your AI wrote the test cases. Run them on real phones.
99tests runs your cases, AI-generated ones included, on the phones, laptops and browsers your users own. Every finding is verified, serious bugs come with a screen recording, and each case comes back pass, fail, blocked or not run.