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