Progress0 / 0 done

Sirah Smoke TestA practice restaurant night to check everything works — before a real restaurant uses it.

4 people2 test restaurantsabout 3 hourstick each box as you go

The one thing to watch all night When one person does something, everyone else's screen should update on its own — nobody should have to refresh. If a screen only updates after a refresh, or looks glitchy (something flashes, pops away and comes back, or gets undone a second later), write it in the bug log.

Who does what

Lead + Admin

Keeps time and the bug log. Also the “admin”: approves the new restaurant, and can switch people off. Runs Restaurant B.

Restaurant A — Manager

Signs up Restaurant A, then runs it: seats guests, manages staff, switches to bookings.

Restaurant A — Staff

A limited staff member (can only work the line). A second screen for the same restaurant.

Guests

Uses everyone's phones as the customers — joins lines, books tables, checks notifications.

Before you start

The site is live and working.
Sign-up is open so P2 can make a restaurant.
A second restaurant (B) is ready to go.
Guest phones can receive text codes.
Everything is named starting with “TEST —”.

Heads up: tapping “join” on a guest phone can take a second to confirm (it waits for the server). The old screen-flicker problem was just fixed, so lists should update smoothly now. Note anything that still feels off — a slightly slow join is a known thing, not a surprise.

The night, act by act

Get ready & log in

20 min

AllStaff log in on their screens.
P4Log in a guest with the text-message code — make sure the code actually arrives.
P4Turn on fingerprint / face login on one phone, then log out and back in with it.
P4Allow notifications on every phone.
AllOpen the Arabic version once and check it looks right.

Good if: everyone can actually log in (code arrives, fingerprint works) and every screen opens with no errors.

Open the restaurant

20 min

P2Sign up a new restaurant — fill the details, upload the storefront photo and ID.
P2Submit. You should land on an “awaiting review” screen (can't use it yet).
AdmFind the new request in the admin site, check the photos, and approve it.
P2Log in and set it up: open a line, set tables, add a menu item, set hours.
P2Add P3 as staff who can only work the line.
AdmDo a second quick signup and this time reject it or ask for more info — the merchant should see that and be able to fix and resend.

Good if: the restaurant stays locked until the admin approves it, the admin sees the uploaded photos, and reject / “need more info” works too.

Find it, then the busy night

35 min

P4A guest opens the app, searches or browses, and finds the restaurant (like a real customer would).
P4Open the restaurant, look at the menu, and tap the heart to favorite it.
P4Now 5–6 guests join the line from different phones (allow location if asked).
P2Notify the first guest — their phone buzzes and their screen updates.
P2Seat them, serve them, clear the table.
P3From the second staff screen, seat a different guest.
P2Remove a no-show guest from the line.
P4Try joining the same line twice, and filling every table.
P2Pause the line for a moment, then reopen it.

Good if: a guest can find the restaurant, see the menu, and join — and both staff screens and the guests' phones update on their own, smoothly.

Staff permissions

25 min

P3Try to open Analytics, Settings, and Staff — you should be blocked.
P2Turn on “see analytics” for P3 → P3 can now open it. Turn it off → it's gone.
P2Try to change your own role → you should not be allowed.
AdmSwitch P3 off from the admin site → P3 is locked out right away. Turn back on.

Good if: staff can only do what they're allowed, and switching someone off works instantly.

Two restaurants stay separate

15 min

P4Send a few guests to Restaurant B instead.
P2Check Restaurant A can't see B's guests, and B can't see A's.
AdmFrom the admin site, pull a report — the admin can see both.

Good if: the two restaurants are private from each other; only the admin sees across.

Bookings (reservations)

25 min

P2Switch Restaurant A to booking mode.
AllEvery screen switches to the booking view on its own.
P4Guests book a table — pick a size and a time.
P2Confirm, seat, or cancel a booking → the guest sees the change.
P2Switch back to the line mode.

Good if: the switch happens everywhere by itself, and bookings go through.

Bad internet & mix-ups

20 min

P4Turn a phone's internet off, do something, turn it back on → it catches up.
P2Two staff seat the same guest at the same time → no double, no glitch.
P3Refresh a dashboard page → the whole list is still there.

Good if: nothing gets lost or stuck.

Arabic & Saudi details

10 min

AllSwitch everything to Arabic → all text translates and reads right-to-left.
AllCheck phone numbers, times, and dates look correct.

Good if: Arabic is complete and nothing is cut off.

Notifications

10 min

P2Send the “you're up”, “table ready”, and “line closed” messages.
P4Check they arrive on real phones (iPhone + Android), in both languages.

Good if: the messages show up and open the right screen when tapped.

Wrap up

15 min

P2Close the line for the night — guests should see it's closed.
P2Check the numbers on the dashboard and admin report make sense.
P1Go through the bug log and decide: launch, or fix first.
AllDelete the test restaurants and accounts.

Good if: the numbers add up and all test data is cleaned up.

Bug log — type anything that goes wrong

Click a cell and type. It saves automatically, even if the screen refreshes.

#	App / Merchant / Admin	What went wrong	How bad?

Launch or not? Only launch if nothing important is broken. If something important breaks, fix it and re-run just that act. This is the real live site — use “TEST —” names, no real customer info, and delete everything at the end.