Manual QA Checklist
Use this page after the automated suite is already green. It is the final browser and workflow review before packaging or marketplace submission.
Current automated baseline: this documentation set was aligned after a passing automated suite. Manual QA should focus on the interactive flows that automated checks do not fully cover.
1) Shell and Branding
Verify the shared UI shell
- Check logo, product name, favicon, sidebar, footer, and topbar labels.
- Confirm there are no placeholder company names, dead external links, or template promo widgets.
- Open the docs links from inside the app and confirm they point to the correct pages.
2) Auth and Security
Critical auth flows
- Login, logout, forgot password, reset password, OTP delivery, and TOTP settings.
- Locked, inactive, suspended, and banned account behavior.
- Password-change request submission, admin approval or rejection, and completion after reset.
- Active sessions page and revoking another session.
3) Users, Roles, and Permissions
Admin account management
- Create a user with one role and a temporary password.
- Edit role, status, and contact details.
- Unlock a locked account and trigger a forced password reset.
Access control
- Verify menu items hide correctly for lower-permission users.
- Confirm restricted routes return the correct unauthorized response.
- Check Copilot context loads on authorized pages without 403 errors.
4) Master Data
Categories, units, suppliers, and products
- Create, edit, list, and validate data on each master-data screen.
- Confirm notifications or audit messages use the correct module names and actor names.
- Open index filters, create forms, and edit forms to catch frontend regressions.
5) Operations
Purchases and stock flows
- Create a purchase and inspect invoice and stock effects.
- Create, edit, and delete a stock-out record.
- Create, edit, and bulk-delete stock adjustments, including the skipped-record response path.
- Run Refresh Database only in a safe non-production environment and confirm the preserved account rules are clear.
6) Notifications, Reports, and Copilot
Notifications
- Confirm bell dropdown, unread counts, open action, mark-read action, and bulk actions.
- Verify admin-recipient users see the same scope in the dropdown and notification index.
- Trigger a simple admin activity event such as category creation and confirm a notification row is created.
Reports and Copilot
- Open main report pages, detail pages, and exports.
- Confirm exported PDFs or files use the correct branding.
- Check Copilot prompts on a few operational pages and confirm route-context access is allowed where expected.
7) Evidence Log
Capture these details
- Tester name, date, app version, and environment URL.
- Screens visited and the user role used for each pass.
- Any issue with exact steps to reproduce, route name, and visible error text.
- Whether the issue is code, docs, packaging, or configuration related.