# Freshyo manual testing guide This guide is for someone testing Freshyo by using the apps — no technical knowledge needed. You only need to use the screens, buttons and test accounts described here. If the app shows it, you can test it. The reference numbers such as `CUST-31`, `ADM-05` or `BR-14` are only for writing down what you tested and reporting a problem. You can ignore them while testing. **What this guide covers:** the customer app (mobile and web), the admin app (mobile and web), the superadmin website, and the cross-app journeys between them. **What it does not cover:** checks that are not visible in the apps. Those are handled separately. --- ## Before you test ### What you need Ask your test coordinator for: - **Test accounts** — a customer account, a second customer account, a brand-new customer account, an admin account for each test area, and a superadmin account. - **Sample data** — two delivery areas (called A and B in this guide), products, delivery slots, and coupons. - **A test phone or browser** — the mobile app on a test phone, and the web apps in a browser. - **A way to take screenshots** — for any failure. Do not use a real customer's account, phone number, address, or payment details. Use only the test accounts and test area given to you. ### Names used in this guide These are just labels for the test data. Your coordinator may use different names; if so, use theirs. | Name | What it means | |---|---| | Customer 1 | The main test customer, with saved addresses in area A | | Customer 2 | A second customer, with an address in area B | | New Customer | A customer with no saved address and no orders | | Admin A / Admin B | Staff accounts for area A and area B | | Superadmin | The account that manages areas, staff and global products | | Area A / Area B | The two delivery areas used for testing | | Product P / Q / G | Test products: P in A, Q in B, G available in both | | Slot S1 / S2 | Future delivery time slots in area A | | Coupon 10% / Coupon ₹100 | Test coupons used for money checks | ### How to write down a result For each check, note: 1. What you did. 2. What you expected to see. 3. What you actually saw. 4. A screenshot, if it failed. Use the reference number from this guide so the team can find the check quickly. ### If you get stuck - If a screen is loading forever, wait up to one minute, then note the screen and try again once. - If data is missing (no products, no slots, no coupons), ask your coordinator; do not change real customer data. - If a test changes money, orders, or customer data, use only the test accounts. --- ## 1. Customer app — mobile and web Use the same steps on the mobile app and on the website unless a step says otherwise. ### 1.1 Sign in, create an account and manage your profile **What this tests:** signing in, creating an account, staying signed in, signing out, changing details, and what happens when an account is suspended. **Steps:** 1. Open the customer app without signing in. 2. Open **Cart** and **Me**. Check that you are asked to sign in, and that you can still browse the Home page. 3. From the Cart sign-in prompt, sign in as Customer 1. Add a product before signing in to check that the cart is still there afterwards. 4. Sign out, then try a wrong password. Sign in correctly. 5. Create a new account with the **New Customer** details. 6. Try creating an account with an existing mobile/email and with missing fields. 7. Close and reopen the app. Check that you are still signed in. 8. Open **Me** → edit your name/profile photo → save → reopen the app. 9. Change your password, sign out, and try the old and new passwords. 10. Sign in as Customer 2. Check that Customer 1's orders, addresses and coupons are not visible. 11. Ask the admin to suspend Customer 1, then try to place an order. Ask the admin to unsuspend and try again. 12. On a disposable test account, use **Delete Me and My Data** and try a wrong confirmation first, then the correct one. **What you should see:** | Check | Expected result | |---|---| | `CUST-09` | Browsing works signed out; Cart and Me ask you to sign in. | | `CUST-10` | You return to the screen you came from; the cart survives sign-in; errors are clear. | | `CUST-11` | A wrong password does not sign you in; Customer 2 cannot see Customer 1's data. | | `CUST-12` | You stay signed in after reopening; an expired sign-in asks you to sign in again safely. | | `CUST-13` | Your name/photo are saved and match what the admin sees. | | `CUST-14` | The new password works and the old one does not. | | `CUST-15` | Wrong confirmation is rejected; correct confirmation removes access. | | `CUST-16` | A suspended customer cannot order; unsuspending allows ordering again. | ### 1.2 Choose the delivery area **What this tests:** the app finding the right delivery area, asking you when it cannot, and keeping the right products and cart when you switch areas. **Steps:** 1. Open the app in area A. Allow location access if asked. 2. Check the delivery area/address shown on Home. 3. Close and reopen the app with location denied, location off, and a point outside the service area. 4. Open the area/address chooser and select area B manually. If a location request arrives late, check that it does not change your choice. 5. Sign in as Customer 1 and switch between the saved addresses in A1 and A2. 6. Add products to the regular cart and the 1-hour cart. Switch to B; cancel the switch, then confirm it. 7. Switch back to A and check the cart. 8. Close the app with a cart and reopen it. **What you should see:** | Check | Expected result | |---|---| | `CUST-01` | The correct area loads once; products and slots appear. | | `CUST-02` | A saved address is used when location is unavailable; otherwise a chooser explains the problem. | | `CUST-03` | A late location result does not override your manual choice. | | `CUST-04` | The selected address decides the delivery zone and charges; another area's address is ignored. | | `CUST-05` | Cancel keeps everything; confirm clears area A selections and loads B. | | `CUST-06` | Each area keeps its own cart; switching back restores it. | | `CUST-07` | A cart is not wiped just because the app picks the first area on launch. | | `CUST-08` | An empty area shows a friendly empty state, not an error. | ### 1.3 Home, search, stores and product details **What this tests:** that area A and area B show the right products, stores, offers and prices, and that product details and add-to-cart work from every entry point. **Steps:** 1. Open Home in area A. Note the products, offers, stores and delivery slots. 2. Switch to area B and compare. 3. Use **Search** for a product name, an offer/tag, and a store name. Also search for something that does not exist. 4. Open **Stores** → a store → a product. Open the global test product G. 5. Open a product with variants, a combo, and a 1-hour product. 6. Add the same product from Home, Search, a store and the product page. 7. Open the quantity selector and try the smallest, largest and an out-of-stock item. 8. Tap an offer, tag or banner and follow where it goes. 9. Open the delivery address/area bar and change the address. **What you should see:** | Check | Expected result | |---|---| | `CUST-17` | Area A shows A + global products; area B shows B + global products; no cross-area products or prices. | | `CUST-18` | Loading, empty, error and refresh states make sense; Retry works. | | `CUST-19` | Search returns only products/stores for the chosen area; no results shows a clear empty state. | | `CUST-20` | Store lists and store pages show the right products; the global store appears in both areas. | | `CUST-21` | Product page shows the correct price, variants, stock, combo contents and 1-hour availability. | | `CUST-22` | The same product added from different screens gives the same item, quantity and price. | | `CUST-23` | You cannot add more than allowed; out-of-stock items cannot be added. | | `CUST-24` | Tapping an offer/banner opens the intended product or store. | | `CUST-25` | The current address is shown; changing it updates the delivery area and prices. | ### 1.4 Cart **What this tests:** adding, changing and removing items, saving the cart, notes, delivery slots, and what happens when an item becomes unavailable. **Steps:** 1. Add a product. Add it again from the product page. 2. Increase and decrease the quantity. Remove a line and cancel the removal; then remove it for real. 3. Close and reopen the app with items in the regular cart and the 1-hour cart. 4. Assign a delivery slot to each item. Leave the cart, come back, and reopen the app. 5. Add a note for the order. Go to checkout, come back, and change the note. 6. Ask your coordinator to mark one test product out of stock or unavailable. Refresh the cart. 7. Close and reopen with an old saved cart. 8. Sign out and sign in as Customer 2 with Customer 1's cart still saved. **What you should see:** | Check | Expected result | |---|---| | `CUST-26` | Adding again merges correctly; changing quantity replaces it; removing affects only that line. | | `CUST-27` | Regular and 1-hour carts both come back after reopening. | | `CUST-28` | Your slot choice is still there after leaving and returning. | | `CUST-29` | Unavailable items are shown clearly and cannot be ordered; if all items are unavailable, checkout is blocked. | | `CUST-30` | The latest note is the one shown at checkout and saved with the order. | | `CUST-37` | A damaged/old saved cart does not create a fake product or a wrong price. | | `CUST-38` | Another customer cannot see or use your cart, address or notes. | ### 1.5 Coupons **What this tests:** which coupons you can see, why some are disabled, and how multiple coupons change the bill. **Steps:** 1. Open the cart with several items and open the coupon list. 2. Look for eligible coupons, a coupon for the other area, a first-order coupon, a minimum-spend coupon, a product-specific coupon, an expired coupon, a used coupon and another customer's coupon. 3. Apply a 10% coupon, then a ₹100 coupon. Remove them and apply them in the opposite order. 4. Change a quantity and check that the discount recalculates. 5. Try a coupon that gives 100% off and a coupon whose discount is bigger than the cart. 6. Check the **Products discount** line in the bill. 7. Open **Me → Coupons** and compare the labels with the cart. **What you should see:** | Check | Expected result | |---|---| | `CUST-31` | Expired, invalid or used-up coupons are not shown. Other coupons show a clear reason when disabled. | | `CUST-32` | The bill and each coupon's saving update when you add, remove or change items. | | `CUST-33` | Applying the same coupons in a different order can give a different total; the total never goes below zero. | | `CUST-34` | The Products discount line appears only when there is a product saving; coupon lines are separate. | | `CUST-36` | The cart total, checkout total and saved order total match. | | `CUST-57` | The Coupons page agrees with the cart: available, used and expired are labelled correctly. | ### 1.6 Checkout and placing an order **What this tests:** choosing an address and slot, applying coupons, paying by cash on delivery, and the safeguards that stop a wrong or duplicate order. **Steps:** 1. Open the cart, select a saved address in area A, assign slots, and tap **Checkout**. 2. Check the address, items, slot, coupon, delivery charge and total. 3. Look at the payment methods. **Cash on Delivery** should be selected; **Pay Online (Coming Soon)** should be disabled. 4. Go back to the cart, change the address, slot, coupon or note, and return to checkout. 5. Tap **Place Order** twice quickly. 6. Place a valid order. 7. Note the order number and total on the success screen. 8. Open **My Orders** and compare the order. 9. As the New Customer with no address, open Cart and Checkout. 10. Try checkout with an item that has no delivery slot. 11. Place a 1-hour order in area A. Then try the 1-hour flow in area B. 12. Use the back button, refresh the browser, and open the success/detail link again. **What you should see:** | Check | Expected result | |---|---| | `CUST-39` | The selected address decides the delivery charge and area. | | `CUST-40` | A customer with no address is asked to add one before checkout. | | `CUST-41` | Each item carries its own delivery slot; no item is sent without a slot. | | `CUST-42` | Only Cash on Delivery is usable; the online option is visibly disabled. | | `CUST-43` | The latest address/slot/coupon/note is shown at checkout. | | `CUST-44` | A fast double tap places only one order. | | `CUST-45` | A failed order shows an error, the button works again, and your cart is kept. | | `CUST-46` | If the response is lost, check My Orders before trying again. | | `CUST-48` | A multi-slot or zero-total order shows the correct order number and total. | | `CUST-49` | 1-hour ordering works in A and is blocked in B. | | `CUST-50` | Back/refresh/deep links do not create a second order or show another order. | | `CUST-35` | An item with no slot, or a slot that has closed, blocks checkout; a 1-hour cart is not blocked by this rule. | ### 1.7 Orders, cancellation and complaints **What this tests:** finding orders, reading the bill, cancelling, ordering again, and raising a complaint. **Steps:** 1. Open **Me → My Orders**. Look at pending, delivered and cancelled orders. 2. Open an order. Check items, address, delivery time, bill, status and notes. 3. Cancel a new order. Enter a reason and confirm. 4. Try cancelling a delivered order. 5. On a cancelled/delivered order, use **Order Again**. 6. Ask the admin to delete or hide a product you ordered. Open the old order. 7. Tap **Raise Complaint**, add a message and an image, and submit. 8. Ask the admin to reply, then reopen the complaint. **What you should see:** | Check | Expected result | |---|---| | `CUST-51` | Orders are listed with the correct status and can be scrolled/paged. | | `CUST-52` | The order detail matches the bill and what the admin sees. | | `CUST-53` | A reason is required; cancelled/delivered orders follow the rules. | | `CUST-54` | Order Again adds the available items; unavailable items are handled clearly. | | `CUST-55` | The complaint is saved and the admin reply is visible. | ### 1.8 Addresses **What this tests:** adding, editing, making default and deleting addresses, and checking that the map location chooses the right delivery area. **Steps:** 1. Open **Me → Addresses**. 2. Add an address using the map and the test area. 3. Try an address outside the service area. 4. Add a second address and make it the default. 5. Edit the address details and move the map pin. 6. Delete an address that is being used by an open order, then a free address. 7. Delete the default address, then the last address. 8. Open the cart and checkout after deleting the last address. **What you should see:** | Check | Expected result | |---|---| | `CUST-56` | The map location picks the correct area/zone; an outside point is rejected; the first address becomes default; an address used by an open order cannot be deleted. | | `CUST-40` | With no address, the app asks you to add one before checkout. | ### 1.9 Profile, coupons and notifications **What this tests:** the remaining customer screens and what happens when the connection is poor. **Steps:** 1. Open **Me** and visit each item: My Orders, Coupons, Addresses, Help & Complaints, Terms and profile settings. 2. Turn the phone/browser offline and open Home, cart and checkout. 3. Allow notifications, add an address, and open a notification link. 4. Use the app with a small screen/keyboard and check that buttons are reachable. **What you should see:** | Check | Expected result | |---|---| | `CUST-58` | Notification permission is handled; the link opens the right order/product. | | `CUST-59` | Offline screens show a clear error and Retry; no fake success. | | `CUST-60` | Keyboard/safe-area/back navigation work; important buttons are readable and reachable. | --- ## 2. Admin app — mobile and web Use the same steps on the admin mobile app and the admin website. The website may ask you to sign in again after a refresh; that is part of the test. ### 2.1 Sign in and area access **What this tests:** admin sign-in, staying signed in, and making sure an admin sees only their own area. **Steps:** 1. Sign in as Admin A. Open the Dashboard. 2. Refresh the page (web) or reopen the app (mobile). 3. Sign out and sign in as Admin B. 4. Use the browser/device back button to return to an Admin A screen. 5. Try to open an admin screen without signing in. **What you should see:** | Check | Expected result | |---|---| | `ADM-01` | Admin A signs in, stays signed in, and sees the correct area. | | `ADM-02` | Admin A and Admin B see only their own orders, products and counts. | | `ADM-03` | After switching to B, Admin A's data is gone and old links are blocked. | | `ADM-04` | Signed-out users cannot reach admin screens or actions. | ### 2.2 Orders **What this tests:** finding orders, reading details, changing status, cancelling, changing the delivery charge, and arranging delivery order. **Steps:** 1. Open **Manage Orders → Orders**. Use the filters and search; scroll to the next page. 2. Ask Admin B to create several newer orders, then return to Admin A and page through A's orders. 3. Open an order. Compare the items, bill, address, notes and customer details. 4. Mark the order **Packaged**, then **Delivered**. 5. Open the customer app and check the status. 6. Cancel another order with a reason. 7. Open a delivered order and try to cancel it. 8. Remove the delivery charge from a test order. 9. Use **Rebalance** on a slot and compare the bill. 10. Open **Delivery Sequences**, change the order, and update one order's map location. 11. Add an admin note and check the customer note. **What you should see:** | Check | Expected result | |---|---| | `ADM-05` | Filters, search and pages show the right orders. | | `ADM-06` | Admin A sees all of A's orders even when other areas have newer orders. | | `ADM-07` | The order detail matches the customer's bill. | | `ADM-08` | Packaged/delivered changes are saved and visible to the customer. | | `ADM-09` | Cancellation needs a reason; a delivered order cannot be cancelled by the customer. | | `ADM-10` | Rebalancing keeps the total and discount correct. | | `ADM-11` | Delivery order and map changes affect only the intended order. | | `ADM-12` | Admin and customer notes appear in the right place. | ### 2.3 Products, prices and stock **What this tests:** creating and editing products, changing prices/stock, handling global products, and avoiding duplicate variants. **Steps:** 1. Open **Products**. Search for Product P and open its details. 2. Create a new test product with two variants, an image, features and tags. 3. Open the customer app in area A and find it. 4. Edit the product's price, stock, offer and 1-hour availability. 5. Edit the global product G's price/stock/suspension for area A. 6. Open the customer app in area B and compare. 7. Suspend a global product in A, reopen it, change only the price, and save. 8. Ask the superadmin to edit G's variants. Count the variants before and after. 9. Delete a product that has orders/variants; then delete a free test product. 10. Open **Prices Overview** and update a price. 11. Create/edit/delete a tag, group and combo; assign products. 12. Upload a product image. **What you should see:** | Check | Expected result | |---|---| | `ADM-13` | The products list and details show the right area and stock state. | | `ADM-14` | The new product is saved and appears only in A. | | `ADM-15` | Price/stock/offer changes are saved and visible to the customer. | | `ADM-16` | Editing a global product in A changes only A's price/stock. | | `ADM-17` | A suspended product stays suspended after an unrelated price change. | | `ADM-18` | A product with orders/variants cannot be deleted; a free one can. | | `ADM-19` | Price edits are saved and the customer sees the new price. | | `ADM-20` | Tags and their order match the customer app. | | `ADM-21` | Groups and slots keep the right products. | | `ADM-22` | A combo shows the right components and price. | | `ADM-34` | Uploaded images appear on the product. | ### 2.4 Stores and delivery slots **What this tests:** store details and the delivery slots customers can choose. **Steps:** 1. Open **Stores**. Create a store, edit it, and upload an image. 2. Open the global store and try to edit it. 3. Delete a store with products/orders, then a free store. 4. Open **Slots**. Create a future slot and assign products. 5. Edit its time, capacity and freeze time. 6. Fill or freeze the slot and open the customer cart. 7. Replicate or copy a slot. **What you should see:** | Check | Expected result | |---|---| | `ADM-23` | Regional stores are editable; the global store is read-only; images are safe. | | `ADM-24` | New/edited/full/frozen slots behave correctly for the customer. | ### 2.5 Coupons, banners and home layout **What this tests:** regional coupons, banners and the order of items on Home. **Steps:** 1. Open **Coupons**. Create a 10% coupon, a ₹100 coupon, one for selected products, and one for selected customers. 2. Use them in the customer app. 3. Edit and invalidate a coupon; try it again. 4. Open **Banners**. Create, edit, activate, deactivate and reorder banners. 5. Check the customer Home in A. 6. Open **Customize App** and change the Popular Items and All Items order. **What you should see:** | Check | Expected result | |---|---| | `ADM-25` | Coupons work only in the right area/for the right products/users. | | `ADM-26` | Only active banners appear, in the chosen order. | | `ADM-27` | The customer Home matches the chosen order. | ### 2.6 Users, complaints and notifications **What this tests:** finding customers, suspending them, adding incidents, replying to complaints and sending notifications. **Steps:** 1. Open **User Management**. Search by Customer 1's name and mobile. 2. Sign in as Admin B and search for the same customer. 3. Open a customer. Suspend, unsuspend, and add an incident note. 4. Open **Complaints**, open a customer complaint, reply and resolve it. 5. Open the customer app and check the reply. 6. Open **Send Notifications**, select a test user, and send a test message. 7. Open **Constants** and change a test setting; check the customer app. 8. Open a screen with no data (for example, a new area with no orders) and use the back/Retry buttons. **What you should see:** | Check | Expected result | |---|---| | `ADM-28` | Customer details are visible only to the right area. | | `ADM-29` | Admin B cannot find Admin A's customers by name or mobile. | | `ADM-30` | Suspension and incidents are saved; notifications go only to selected test users. | | `ADM-31` | Complaints are area-scoped and the customer sees the reply. | | `ADM-33` | The changed setting appears for the customer; the other area is unchanged. | | `ADM-35` | Empty/loading/error screens show a clear message; Retry/back works. | --- ## 3. Superadmin website The superadmin sets up areas, staff, global products and global coupons. Use only the test areas and test accounts given to you. ### 3.1 Sign in and delivery areas **What this tests:** superadmin access, area setup, and the map/zone used for delivery. **Steps:** 1. Sign in as Superadmin. Sign out, sign in again, and refresh. 2. Open **Regions**. Select area A. 3. Review the area name, delivery charge, free-delivery amount, 1-hour settings and support details. 4. If instructed, add a new test area with one delivery zone using the map. 5. Try to save an area without a zone, or with an invalid/duplicate zone. 6. Add, edit and delete a test zone. Try deleting the last zone. 7. Open the customer area chooser and check that the new/edited area appears. 8. Change an area's settings and check the customer app. **What you should see:** | Check | Expected result | |---|---| | `SA-01` | Superadmin signs in and stays signed in; staff/customer pages are not accessible. | | `SA-02` | A new area can be created and appears for customers. | | `SA-03` | Missing/invalid zones are rejected without creating a broken area. | | `SA-04` | A zone can be edited/deleted only when allowed. | | `SA-05` | A new area gets the right products and prices. | | `SA-06` | The new area's products and pages open normally. | ### 3.2 Staff and global stores **What this tests:** creating staff, assigning an area, and managing shared stores. **Steps:** 1. Open **Admin Users**. Add a test admin for area A and one for area B. 2. Change an admin's area/role, then sign in as that admin. 3. Remove a test admin and try to sign in. 4. Open **Global stores**. Create, edit and delete a test global store. 5. Check the store in both customer areas. 6. Sign in as Admin A and try to edit the global store. **What you should see:** | Check | Expected result | |---|---| | `SA-07` | Staff get the right area/role; removed staff cannot sign in. | | `SA-08` | A global store appears in both areas; regional admins cannot edit it. | ### 3.3 Global products **What this tests:** products shared by all areas, with different local prices. **Steps:** 1. Open **Global products**. Create a test global product with two variants. 2. Set different prices for area A and area B. 3. Check the product in both customer areas. 4. Edit the product, save, and save again without changes. 5. Count the variants in the admin/customer screens. 6. Open Create, then Edit, then Create again; check the form fields. 7. Suspend the product in one area and check the other. 8. Use **Elevate** on a regional product. 9. Upload a global product image. **What you should see:** | Check | Expected result | |---|---| | `SA-09` | The global product appears in both areas with the local price. | | `SA-10` | Editing does not create duplicate variants. | | `SA-11` | The form shows the selected product and resets when you start a new one. | | `SA-12` | Suspending in one area does not suspend it in the other. | | `SA-13` | An elevated product remains available in its original area. | | `SA-21` | The image appears in both areas. | ### 3.4 Global coupons, settings and notifications **What this tests:** coupons shared by all areas, global settings, and admin notifications. **Steps:** 1. Open **Global coupons**. Create a percentage coupon and a ₹ discount coupon. 2. Use them in both customer areas. 3. Edit a 20% coupon to ₹50 and save. 4. Use it again and check the discount. 5. Invalidate/delete the coupon and try it again. 6. Open **Constants**. Change a global test setting and compare both areas. 7. Open **Complaints** and reply to a test complaint. 8. Open **Send Notifications → Admin Notifs** and send a test message. 9. Switch between area tabs and refresh. 10. Open an empty screen and a delete confirmation; try Cancel and then Confirm on a disposable test item. **What you should see:** | Check | Expected result | |---|---| | `SA-14` | Global coupons work in both areas. | | `SA-15` | Switching from percentage to ₹ discount uses only the new discount. | | `SA-16` | Global settings apply everywhere; local settings still win. | | `SA-17` | Complaints show the right area and reply. | | `SA-18` | Admin Notifs sends successfully as superadmin. | | `SA-19` | Staff/customer accounts cannot open superadmin screens. | | `SA-20` | Empty/loading/error screens are clear; Cancel does not delete data. | | `SA-22` | Area tabs show the right area and refresh after a rename. | | `SA-23` | A global edit reaches all areas after a short wait. | --- ## 4. Cross-app journeys These checks use more than one app. Keep the same test accounts and data. ### 4.1 Full order journey **What this tests:** the complete path from setup to delivery. **Steps:** 1. Superadmin: confirm area A exists and create Admin A if needed. 2. Admin A: create a test store, product P, future slot S1 and a 10% coupon. 3. Customer 1: open area A, find P, add it, choose S1, apply the coupon and checkout. 4. Place the order with Cash on Delivery. 5. Admin A: find the order, compare the items and bill, mark Packaged, then Delivered. 6. Customer 1: open My Orders and check the status. 7. Compare the order number and total everywhere. **What you should see:** `E2E-01` — the same order and total appear at every step, and the status ends as Delivered. ### 4.2 Global product in two areas **What this tests:** one shared product with different local prices. **Steps:** 1. Superadmin: create global product G with an A price and a B price. 2. Customer 1 in A: open G and note the price. 3. Customer 2 in B: open G and note the price. 4. Admin A: change the A price. 5. Admin B: change the B price. 6. Refresh both customer apps. **What you should see:** `E2E-02` — each area keeps its own price; changing A does not change B. ### 4.3 Switching areas with a cart **What this tests:** that areas do not mix products or carts. **Steps:** 1. Customer 1: add a regular product and a 1-hour product in area A. 2. Switch to area B and cancel; check that A is still there. 3. Switch to B and confirm; add a B product. 4. Switch back to A; check the A cart. 5. Switch to B; check the B cart. 6. Repeat on the website. 7. Close and reopen the app. **What you should see:** `E2E-03` — no product or price from the other area appears; each cart comes back when you return to its area. ### 4.4 Coupons on the bill **What this tests:** multiple coupons and the final payable amount. **Steps:** 1. Build a ₹1000 cart. 2. Apply 10% then ₹100; note the discount and total. 3. Reverse the order; note the difference. 4. Place the order. 5. Compare the cart, checkout, success screen, My Orders and Admin A's order. **What you should see:** `E2E-04` — the total is the same on every screen and never goes below zero. ### 4.5 1-hour delivery **What this tests:** 1-hour products, prices and area availability. **Steps:** 1. In area A, open the 1-hour section and add a 1-hour product. 2. Check the 1-hour price and delivery charge. 3. Place a Cash on Delivery order. 4. Admin A: open the order and confirm it is a 1-hour order. 5. Customer 2 in area B: try the 1-hour section for the same product. **What you should see:** `E2E-05` — A can order; B is blocked; the admin sees the right type of order. ### 4.6 Two delivery slots in one order **What this tests:** one order split into two delivery times with one delivery fee. **Steps:** 1. Add a product for S1 and another for S2 in the same cart. 2. Checkout and place the order. 3. Admin A: open the order and check both slots. 4. Mark one part delivered, then the other. 5. Customer 1: check both statuses. **What you should see:** `E2E-06` — two delivery parts, one delivery fee, and the correct status for each part. ### 4.7 Cancel and use the coupon again **What this tests:** cancelling an order and releasing a one-time coupon. **Steps:** 1. New Customer: place an order with a first-order coupon. 2. Cancel it with a reason. 3. Place a new order and use the same coupon. 4. Place a two-slot order with the coupon and cancel one part. 5. Cancel the other part. 6. Try the coupon again. **What you should see:** `E2E-07` — the coupon becomes usable again only when no part of the order remains. ### 4.8 Website checkout with two slots **What this tests:** the website sends the chosen delivery slot for each item. **Steps:** 1. On the website, add items for S1 and S2. 2. Choose both slots in the cart and open Checkout. 3. Place the order. 4. Open the order and check both slots. 5. Try again with one item that has no slot. **What you should see:** `E2E-08` — the order saves both slots; an item without a slot blocks checkout. ### 4.9 Admin search by area **What this tests:** an admin can find only their own area's customers. **Steps:** 1. Customer 1 orders in A; Customer 2 orders in B. 2. Admin A searches for Customer 2's name and mobile. 3. Admin B searches for Customer 1's name and mobile. 4. Search for a name that exists in both areas. **What you should see:** `E2E-09` — each admin sees only their own area's customers and mobile numbers. ### 4.10 Global update reaches both areas **What this tests:** a global product change appears everywhere. **Steps:** 1. Superadmin: change global product G. 2. Admin A: immediately change a banner or product in A. 3. Wait up to two minutes. 4. Refresh the customer apps in A and B. **What you should see:** `E2E-10` — both areas show the global change; A also shows its local change. ### 4.11 Admin website refresh **What this tests:** an admin website refresh keeps you signed in and keeps the data loading. **Steps:** 1. Sign in to the admin website and open **Slots**. 2. Refresh the browser. 3. Open a slot. 4. Repeat after signing out and in as Admin B. **What you should see:** `E2E-11` — you stay signed in with the right area and the slots load. ### 4.12 Superadmin admin notification **What this tests:** sending a notification to admins. **Steps:** 1. Sign in as Superadmin and open **Send Notifications → Admin Notifs**. 2. Enter a title and message and send. 3. Check the success message. 4. Ask an admin to check for the notification. **What you should see:** `E2E-12` — the message is queued/sent without an error. ### 4.13 Different roles see different things **What this tests:** customers, admins and superadmins cannot use each other's screens. **Steps:** 1. Sign in as a customer and try to open an admin screen by typing its web address. 2. Sign in as an admin and try to open a superadmin screen. 3. Sign in as a superadmin and check that customer/admin-only screens are not available. 4. Use the back button after signing out. **What you should see:** `E2E-13` — each role sees only its own screens; old links do not work after sign-out. ### 4.14 Deleted product in old orders **What this tests:** old orders still show a product after it is removed. **Steps:** 1. Place an order for a test product. 2. Admin A: delete or hide the product. 3. Refresh the customer catalog; the product is gone. 4. Open the old order as the customer and as Admin A. 5. Try Order Again. **What you should see:** `E2E-14` — the catalog hides it, but the old order keeps the name, quantity and price; reorder handles it as unavailable. ### 4.15 Address in another area **What this tests:** the delivery address decides the order's area. **Steps:** 1. Customer 1 is browsing area A. 2. Add/select an address inside area B. 3. Build a cart and open checkout. 4. Check the delivery charge and place the order. 5. Admin B: find the order. 6. Admin A: confirm the order is not there. **What you should see:** `E2E-15` — the order belongs to B and uses B's charges. ### 4.16 Delivered/cancelled messages **What this tests:** status changes and notification links. **Steps:** 1. Place an order and note its number. 2. Admin A: mark it delivered. 3. Open the customer notification/link. 4. Cancel another order with a reason. 5. Open that notification/link. **What you should see:** `E2E-16` — each link opens the correct order with the correct status. --- ## 5. Special regression checks These are the checks that previously found bugs. Run them before the wider testing if you can. ### BR-01 — Customer search stays inside an area 1. Customer 1 orders in A; Customer 2 orders in B. 2. Sign in as Admin A and search for Customer 2 by name and mobile. 3. Sign in as Admin B and search for Customer 1. 4. Search a name used in both areas. **Expected:** each admin sees only their own area's customers. ### BR-02 — Website loads after choosing an area 1. On the website, choose area A. 2. Check that products, slots and delivery charges load. 3. Switch to area B and check again. **Expected:** the page loads normally; no error or blank catalog. ### BR-03 — Editing a global product does not duplicate variants 1. Superadmin: open a global product with two variants. 2. Change a price and save. 3. Save again without changes. 4. Count the variants. **Expected:** still two variants; no duplicate appears. ### BR-04 — Global store image stays after a rejected edit 1. Superadmin: open a global store with an image; note the image. 2. Admin A: try to edit the global store. 3. Refresh the store in both apps. **Expected:** the edit is rejected and the image is still there. ### BR-05 — Global change plus local change 1. Superadmin: change a global product. 2. Within 30 seconds, Admin A: change a banner or product in A. 3. Wait up to two minutes; refresh both areas. **Expected:** both areas show the global change and A also shows its local change. ### BR-06 — Website checkout sends slots 1. Website: add items for S1 and S2. 2. Choose both slots and place the order. 3. Check the order detail. **Expected:** both slots are saved; no "slot required" error. ### BR-07 — New area is usable 1. Superadmin: create a test area with a zone. 2. Open the customer area chooser and select it. 3. Check products/slots/delivery charges. **Expected:** the area is listed and its pages load. ### BR-08 — Global product form does not keep an old draft 1. Superadmin: Global products → Create; type a name but do not save. 2. Click Edit on another product. 3. Click Create again. **Expected:** Edit shows the selected product; Create is empty. ### BR-09 — Old orders in a quiet area 1. Area A has several old orders; Area B creates many new orders. 2. Admin A: open Manage Orders and page through. **Expected:** all A orders appear; the list is not empty. ### BR-10 — Cart survives the first area choice (known issue) 1. Add a product to the cart. 2. Close and reopen the app; let it choose the first area. 3. Open the cart. **Expected:** the cart is still there. If it is empty, record it as `BR-10` (known issue). ### BR-11 — Suspension stays after a price change 1. Admin A: suspend a global product in A. 2. Reopen it, change only the price, and save. 3. Check the customer app in A and B. **Expected:** it is still suspended in A; B is unchanged. ### BR-12 — Coupons never make a total negative 1. Build two cart parts of ₹101 each. 2. Apply two ₹101 coupons. 3. Place the order. **Expected:** each part shows ₹0, not a negative amount; the bill adds up. ### BR-13 — Old orders and discounts (accepted) 1. Open an old order that used a coupon. 2. Check the discount line in the customer and admin views. **Expected:** the discount may show ₹0 for very old orders. This is accepted for now; do not report it as a new bug. ### BR-14 — Changing a global coupon type (known issue) 1. Superadmin: create a 20% global coupon. 2. Edit it to ₹50 and save. 3. Use it in the customer app. **Expected:** the discount should be ₹50 only. If 20% is still applied, record it as `BR-14` (known issue). ### BR-15 — Admin website after refresh 1. Sign in to the admin website. 2. Refresh the page. 3. Open Slots and a slot detail. **Expected:** you stay signed in and the slots load. ### BR-16 — Superadmin admin notification 1. Superadmin: Send Notifications → Admin Notifs. 2. Send a test message. 3. Check the result. **Expected:** the message sends successfully; no error. ### BR-17 — Only Cash on Delivery 1. Open checkout. 2. Look at the payment methods. 3. Place a test order. **Expected:** Cash on Delivery is the only usable method; the online option is disabled. ### BR-18 — No delivery slot 1. Add an item and do not choose a slot. 2. Try to check out. **Expected:** checkout is blocked with a clear message. ### BR-19 — Address decides the area 1. Browse area A, then select an address in area B. 2. Place an order. 3. Check Admin A and Admin B order lists. **Expected:** the order appears in B with B's charges, not in A. ### BR-20 — Order pages stay stable 1. Create orders in A and B. 2. Admin A: page through the order list. 3. Admin B: do the same. **Expected:** every order appears once; pages do not skip or repeat orders. --- ## 6. Other screens (only if your coordinator says they are active) Some screens are not part of normal testing. Test them only if your coordinator confirms they are in use for this release. ### 6.2 Reviews 1. As a customer, open a delivered order or product and write a review with an image. 2. As an admin, open **Reviews** and reply. 3. Check the customer can see the reply. **What you should see:** `COND-02` — the review and reply are saved and visible. If reviews are not active, skip this check. ### 6.3 One-time password (OTP) sign-in 1. Use the test mobile number and the test code provided by your coordinator. 2. Request the code and sign in. 3. Try a wrong/expired code, then the correct one. **What you should see:** `COND-03` — one account is created/signed in, and a wrong code is rejected. Never use a real customer's phone number. ### 6.4 Older fallback pages 1. Open the older login/home/order-details links provided by your coordinator. 2. Check only the pages your coordinator says are still supported. 3. Note any page that looks like a demo or is no longer used. **What you should see:** `COND-04` — supported pages work; unsupported pages are recorded as "not applicable" with a reason. --- ## 7. Known issues | Check | What to expect | |---|---| | `BR-10` | A cart may be cleared when the app chooses the first area on launch. Record it; it is known. | | `BR-14` | A global coupon changed from 20% to ₹50 may still apply 20% in the current build. Record it; it is known. | | `BR-13` | Very old orders may show a ₹0 discount. This is accepted; do not report it as new. | --- ## 8. Reporting a problem Use this simple format: ```text What I was testing: Reference number (for example CUST-31): Account used (Customer 1 / Admin A / Superadmin): Area (A or B): Steps I took: What I expected: What actually happened: Screenshot: Date and time: ``` If the problem involves money, write down the item total, discount, delivery charge and final total. If it involves an order, include the order number.