QA Test Guide
This guide is for people who test the product by hand. You do not need to know how it is built. Each Module of the product has a Manual of test cases: follow each case exactly as written, tick Pass or Fail, and report anything that does not match.
Words used in this guide
| Word | Meaning |
|---|---|
| Module | One area of the product with its own Manual, such as Services or Teams. |
| Manual | The test cases of one Module: an index page and one page per group of cases. |
| Case | One test with an ID such as AUTH-01, steps, and an expected result. |
| Persona | The kind of person you play in a case, with its account, devices, language and theme. |
| Lens | One way of looking at every screen, such as design, copy or accessibility. |
| Run log | The record of one Persona playing one Module, kept under Run logs. |
| Round | One pass through every case of every Module. |
Rules every manual follows
- The manuals are written in English. Where a case quotes product text, it quotes it exactly, in the language the case names (English or Bangla).
- No developer terms (code, database, API). Every step names a button, a page or a message you can see.
- Phone first. Every case is written for a 390 px wide screen. Cases that look different on a laptop say so.
How to use this guide
- Read Before you start once: where to test, your accounts, the safety rules, and how to walk every case. Then read Checks on every module.
- Pick a Module from the table below and open its Manual. Work through its cases from top to bottom, because later cases often rely on earlier ones.
- For each case, do the numbered steps in order and compare what you see with the Expected result. Match the text exactly, including capital letters and Bangla spelling.
- Mark the case Pass if everything matches. Mark it Fail if anything differs, then follow Reporting a bug.
- If a step is not possible (for example a button is missing), do not guess. Mark the case Blocked, note which step, and report it.
Before you mark a case, you can compare your screen with the expected screenshots. They are in the shared Google Drive folder QA screenshots; the team sends you the link.
- The folder has one folder per Module, named like the Module in lower case with dashes (Sign-in and security is
sign-in-and-security), then one folder per case ID, for examplesign-in-and-security/AUTH-01/. - Each picture's name gives the step, the screen width in px (390 is a phone), light or dark mode, and the language (
bnBangla,enEnglish).2-390-light-bn.pngis step 2 on a phone, light mode, Bangla;2-1440-dark-en.pngis step 2 on a wide laptop screen, dark mode, English. - To see every step with its expected text next to the pictures, download the Module folder (Drive saves it as a .zip file), unzip it, and double-click the file
index.htmlinside. It opens in your browser.
Case format
Every case in this guide looks like this:
| Field | Meaning |
|---|---|
| ID | A short code such as AUTH-01. Use it when you report a bug. |
| Who | The kind of person to test as, for example a signed-out visitor, a Supporter, a Creator, a Team Member or a Manager. |
| Before | What must be true before step 1. |
| Steps | Numbered actions. Do exactly these and nothing else. |
| Expected result | What you must see when the steps are done. |
| Result | [ ] Pass [ ] Fail [ ] Blocked, tick one. |
Copy the pages of the Manual you test, tick the boxes in your copy, and send the copy back as Before you start describes. Do not edit the original.
Modules
Managers are the platform's staff; their Modules test the staff site, which is in English only.
| Module | What it covers |
|---|---|
| Sign-in and security | Email code sign-in, two-factor, sessions, email change, closing an account. |
| Marketing website | Public pages, language switch, forms. |
| Public page | A Creator's Public page, Coffee gifts, Rewards and claims. |
| Creator onboarding | First-time setup and the creator agreement. |
| Identity verification and tax | The identity check on a computer and a phone, the Reviewer's decision, emails, and the Tax page. |
| Services | Turning the Newsletter and the Shop on and off, service requests and their answers, the Gifts page. |
| Page editor and Share kit | Editing the Public page, the eight Share kit tools, the stream alert link. |
| Newsletter | Writing and publishing posts, a Newsletter editor's limits, the reader's feed, Memberships and paid posts. |
| Shop for Supporters | Browsing a shop, the cart, paying online and cash on delivery, orders, returns, reviews and downloads. |
| Shop studio for Creators | Products, orders, returns, reviews, shop settings and a fulfilment member. |
| Earnings, payouts and billing | Balance, Payout requests, Fees owed, transactions, storage add-ons and billing history. |
| Messages, notifications and emails | Chats, the bell and its notifications, notification settings, unsubscribing, and every email. |
| Home feed, following, supporters and activity | The Home feed, following, a Creator's activity page and the supporters page. |
| Teams | The Team page, Roles and permissions, invitations, Team activity, Access requests and the team emails. |
| Settings and Connected apps | Profile, notifications, theme and language, Team access, and connecting an AI tool. |
| Safety and moderation | Reporting a Creator, the staff screens that act on reports, and deactivating a page. |
| Manager: content review | The staff screens a Content manager uses besides the report queue. |
| Manager: support | Users, Log in as user, and the other screens a Support manager uses. |
| Manager: finance | Payouts, refunds, Fees owed, tax certificates and the other screens a Finance manager uses. |
| Manager: super admin and developer tools | Managers, Platform settings, Add-ons and the Developer pages only a Super admin can use. |
| Desktop app and installed web app | The download page, the desktop app on Windows, Linux and a Mac, and the installed web app on a phone. |
| Access-leak check | Trying to reach what is not yours, for every kind of person; the results by role and area. |
| Cross-module journeys | Four stories that cross Modules: a gift to a refund, a Team Member's order, an identity check to a payout, an order to a review. |
Personas
Each kind of tester has a card: who they are, which account and permissions they use, what they want, what they distrust, and the devices, language and theme they prefer. See Personas and lenses. Developers who run or extend the AI persona kit read QA persona kit.
Coverage
The QA coverage list maps every page, email, permission and money state to a Module, a Persona and case IDs. Rows with no case ID are gaps. A check fails when the code has something the list does not.
Test rounds
Each Round is one pass through every Module. Write down in your copy of each Manual:
- The date and the person testing.
- The browser, device, and screen size used.
- The language of the site (Bangla or English).
Example: 2026-11-10, Rina, Chrome on Pixel 7, 390 px, Bangla.
Repeat the Round when the team announces a new release.