AppzCart Clinic · Manual UI testing

Testing a release before it is deployed

For the clinic team and testers  ·  Manual UI testing only  ·  Updated 02-11-2026

Before every release, the team tests the web app by hand, each person on one role's account, to make sure every patient flow still works end to end. These four pages are all you need. Open them straight from this folder in Chrome or Edge.

0 · How the flow worksWith screenshots: how Reception sends a patient to the Nurse, and the Nurse to the Doctor or DMO, then Lab and Complete Visit. Read this first. 1 · Test strategyWhat kinds of testing we do, test data and accounts, how a test run goes, defect severity, and when a release is ready. 2 · High-level scenariosThe complete patient journeys across roles, run together by the team. 3 · Detailed scenariosEvery case, role by role: sign-in, Reception, Nurse, DMO, Doctor, Lab, Clinic Admin, Reports. 4 · Team plan · 03-11-2026One tester per role. Mark Pass / Fail as you go, then Export to Excel with a dashboard.

In what order

  1. Read how the flow works and the strategy once.
  2. On test day, open the team plan, type your name in your role's block and follow the day's timetable.
  3. Use the high-level and detailed pages to read a case in full or to print it.
  4. At the end, Export to Excel and send the file to the test lead.

Keeping this up to date

All the cases are in one file, test/cases.js. The detailed page, the high-level page and the team plan all read it. When a feature changes, change its cases there. For the next test day, copy the team plan page with the new date in its name.