Overview
This guide is for QBM support teams and power users. It gives a practical checklist to confirm important workflows still work after changes. Testing should be done in a test company or controlled environment whenever possible.
Core Tests
- Log in as administrator and as a normal user.
- Open company, customer, vendor, item, account, and bank lists.
- Create and save a simple master record in a test company.
- Check permissions by confirming restricted users cannot open restricted screens.
- Run a common report and export it.
- Preview and print a common document.
- Send a test email if email settings are used.
- Create and restore or verify a backup according to support policy.
Transaction Tests
| Area | Test |
|---|---|
| Sales | Create quote/order/invoice or sales receipt, receive payment, print/PDF/email, and review customer balance. |
| Purchases | Create purchase order or bill, pay bill, print, and review vendor balance. |
| Inventory | Create adjustment or transfer and confirm quantity changes in stock reports. |
| Banking | Create deposit or payment and review bank transaction list. |
| Accounting | Create a test journal and review Trial Balance impact. |
POS Tests
- Open POS and confirm workstation settings.
- Scan or select an item and complete a cash sale.
- Test card or alternate tender if configured.
- Print or preview receipt.
- Test refund or void according to permissions.
- Close or review POS batch and daily report.
Integration Tests
- Confirm integration settings are saved and visible only to authorized users.
- For PintAE, submit or prepare a controlled test invoice according to the guide.
- For WooCommerce or Shopify, test connection, item match, order import, and logs.
- For Dineplan, test items, cash sales import, and logs.
- For Emaar, test daily or monthly sales calculation before upload.
- For tax-free or mall integrations, test only with approved sample data.
Evidence To Record
- QBM version and database/company tested.
- Tester name and date.
- Workstation or server name.
- Documents created for testing.
- Reports exported or printed.
- Errors found and screenshots if safe to share.
- Final pass/fail status and next action.