Manual test scenarios generated from tracked changes. Pass/Fail and Notes are filled in by a tester while actually running each test.
| Test | Source | Precondition | Steps | Expected Result | Pass/Fail | Notes |
|---|---|---|---|---|---|---|
| Create an RMA from a POS order line and confirm it links to the order | OCA/pos#1427 KAN-5 | The new POS RMA module is installed and the POS session is open with a logged-in cashier. At least one completed/paid POS order exists containing a product line with a known quantity (for example, 5 units). The tester also has access to the backend RMA list to verify the created record. |
| The RMA is created successfully and a confirmation is shown in the POS without errors. Opening the RMA record in the backend shows the correct product, the return quantity entered, the reason entered, and a reference linking it back to the originating POS order. | ||
| Return quantity greater than the quantity sold is rejected | OCA/pos#1427 KAN-5 | The new POS RMA module is installed, a POS session is open, and a completed POS order exists with a product line of a known quantity (for example, 5 units). |
| Submission is blocked and a clear validation message explains that the return quantity cannot exceed the quantity originally sold. No RMA record is created for that order line. | ||
| Reason is required before an RMA can be submitted | OCA/pos#1427 KAN-5 | The new POS RMA module is installed, a POS session is open, and a completed POS order exists with at least one product line. |
| With the reason left empty, submission is blocked and the tester is told the reason is required; no RMA is created. After entering a reason, the RMA is created successfully and is linked to the originating POS order. | ||
| Cashier without the permission group performs a blind closing | OCA/pos#1495 KAN-6 | The blind session closing module is installed. A point-of-sale with a cash payment method is configured and has an opening balance. A test user has point-of-sale access but does NOT have the "Can see POS closing amounts" right enabled in their user record's Extra Rights tab. |
| The closing screen shows no expected cash amount, no expected total and no difference between expected and counted values. Only the counted amount field is available for input. The entered counted amount is accepted and the session closes successfully. | ||
| Authorized user sees expected amounts during closing | OCA/pos#1495 KAN-6 | The blind session closing module is installed. A point-of-sale with a cash payment method is configured. A test user has point-of-sale access and has the "Can see POS closing amounts" right enabled in the Extra Rights tab of their user record. |
| The closing screen displays the expected cash amount alongside the counted amount and shows the resulting difference, exactly as in the standard closing view. The session closes successfully with the difference recorded. | ||
| Granting the right takes effect on the next closing screen | OCA/pos#1495 KAN-6 | The blind session closing module is installed. A test user initially does NOT have the "Can see POS closing amounts" right. An administrator account is available to edit user rights. |
| Before the right is granted the closing screen hides all expected amounts; after the right is granted and the user logs back in, the same closing screen now displays the expected amounts and the difference against the counted amount. | ||
| Order summary panel appears on the Payment Screen with correct line details | OCA/pos#1514 KAN-4 | The module that shows the order on the payment screen is installed. A Point of Sale configuration exists with at least three sellable products with different prices, and a payment method is available. The tester has access to open a POS session. |
| A read-only order summary panel is shown on the right side of the Payment Screen. It lists every order line with the same product names, quantities and prices as recorded on the order screen, and the total matches. The payment keypad and payment method buttons remain fully visible and usable, with no overlap or cut-off content. | ||
| Panel updates live when the order is changed before payment is finalized | OCA/pos#1514 KAN-4 | A POS session is open with an order containing at least two products, and the tester is currently on the Payment Screen with the order summary panel visible. |
| The order summary panel reflects the modified order: the changed quantity and the newly added product line appear, and the displayed total matches the updated order total. No stale lines or outdated amounts remain. | ||
| Existing payment flow and keypad behavior are unchanged, and the panel is read-only | OCA/pos#1514 KAN-4 | A POS session is open with an order containing several products. At least one cash payment method and one other payment method (for example bank/card) are configured. |
| The order summary panel is read-only: clicking lines does not allow editing, removing, or changing quantities. The keypad, payment method selection, partial payment handling, remaining/change calculation and validation all behave exactly as before the change. The new order's Payment Screen shows its own correct summary panel with no leftover data from the previous order, and no extra configuration or setting was needed to make the panel appear. | ||
| Sales Order PDF is produced automatically when the print option is enabled | OCA/pos#1523 KAN-7 | A Point of Sale is configured with the "Order to Sale Order" functionality active, and the user has access to Point of Sale settings. At least one sellable product is available in the POS. |
| The POS order is converted into a sales order, and immediately afterwards the Sales Order PDF is generated and offered for printing/download without any extra manual action. The PDF content matches the sales order just created (customer, products, quantities and totals). | ||
| Behavior is unchanged when the print option is disabled | OCA/pos#1523 KAN-7 | A Point of Sale is configured with the "Order to Sale Order" functionality active, and the option to print the Sales Order PDF on conversion is turned off. |
| The POS order is converted into a sales order exactly as before, and no Sales Order PDF is generated or offered for printing. | ||
| New setting is visible and persists in the POS configuration | OCA/pos#1523 KAN-7 | Access to the Point of Sale configuration settings with the "Order to Sale Order" functionality available. |
| The new print option is shown inside the existing "Order to Sale Order" section and is only available/relevant when that functionality is active. The chosen value (on or off) is correctly saved and shown each time the configuration is reopened. | ||
| Delivery status shows Fully Delivered after converting a POS order with stock-tracked products | OCA/pos#1536 KAN-8 | Point of Sale is installed with the POS-to-sale-order feature enabled for the session's user. A product that is tracked in inventory (storable/delivery-tracked) is available for sale with enough stock on hand. A customer record exists. A POS session is open. |
| The sale order exists with the product and quantity taken from the POS order, its linked delivery is validated (Done), and the Delivery Status on the sale order reads Fully Delivered rather than staying empty, Pending or Nothing Delivered. | ||
| Delivery status stays correct when reopening or refreshing the sale order | OCA/pos#1536 KAN-8 | A sale order has just been created from a POS order with stock-tracked products and its deliveries have been validated, as in the previous scenario. |
| The Delivery Status consistently shows Fully Delivered in both the list view and the order form, and does not revert to a stale or empty value after reloading. | ||
| No change for products that are not delivery tracked | OCA/pos#1536 KAN-8 | Point of Sale is installed with the POS-to-sale-order feature enabled. A product that is NOT tracked in inventory (a service or non-storable consumable) is available for sale. A customer record exists. A POS session is open. |
| The sale order is created correctly with the right customer, product and amounts. No unexpected delivery is generated for the non-tracked product, and the order's delivery information behaves exactly as it did before this change (no incorrect Fully Delivered status forced onto an order that has nothing to deliver). | ||
| Remove a line from an order that was already synced to the backend | OCA/pos#1552 KAN-9 | A Point of Sale configured with the picking-keep behavior enabled for sale orders is open. A cashier user is logged into the POS session. At least two sellable products with stock are available. |
| The POS session stays responsive with no error dialog, crash, or blocked screen at any point. The line is removed as requested, the order can be paid and validated, and the resulting order in the backend reflects only the remaining lines with its delivery/picking information intact. | ||
| Picking-keep behavior still works for a brand-new, unsynced order | OCA/pos#1552 KAN-9 | A Point of Sale configured with the picking-keep behavior enabled is open, with a cashier logged in and sellable products in stock. |
| The order is completed without errors and the delivery/picking is created and linked exactly as it was before this fix — no change in behavior for new orders. | ||
| Mixed edits on a previously-synced order | OCA/pos#1552 KAN-9 | A POS session is open with the picking-keep behavior enabled, and three products with stock are available. |
| All edits are accepted without any error message or session crash. The validated order contains the expected lines and quantities, and its delivery/picking matches the final contents of the order. | ||
| Module installs cleanly on the new version | OCA/pos#1566 KAN-11 | A clean instance of the new platform version with the Point of Sale application available and an administrator login. |
| The module installs without any error or warning dialog and appears as Installed. The Point of Sale application and its configuration screens open normally after installation. The module's displayed version corresponds to the new platform release and its description page renders correctly. | ||
| Print a receipt early, before the order is finalized | OCA/pos#1566 KAN-11 | The early receipt printing module is installed. A point-of-sale configuration exists with receipt printing enabled, and at least one sellable product with a price is available. A cashier user can open a POS session. |
| The early receipt option is available and can be used before the order is finalized. A receipt is generated showing the current order lines and total. The order remains open and can still be modified or paid afterwards; no error is shown and the session stays usable. | ||
| Normal order completion and receipt are unaffected | OCA/pos#1566 KAN-11 | The early receipt printing module is installed and an open point-of-sale session exists with at least one sellable product available. |
| The order is paid and validated as usual, the standard receipt is produced with the correct lines, totals and payment information, and the session closes without errors. Behavior matches the previous version of the module, with no missing buttons, duplicated receipts or error messages. | ||
| Remove-line button no longer appears on the order receipt | OCA/pos#1597 KAN-10 | Point of Sale is installed with the module that adds the remove-line button enabled. A POS session is open with at least one product available for sale. |
| No remove-line button (or any delete/remove control) appears next to any line on the receipt, either on screen or in the printed output. The receipt shows the product lines, quantities, prices and totals correctly with no missing, misaligned or overlapping elements. | ||
| Remove-line button still works on the active order screen | OCA/pos#1597 KAN-10 | Point of Sale is installed with the module that adds the remove-line button enabled. A POS session is open with at least two products available for sale. |
| The remove-line button is visible on each line of the active order screen. Clicking it removes only the selected line, the remaining lines stay intact, and the order total recalculates correctly. | ||
| Receipt reprinted from order history has no remove-line button | OCA/pos#1597 KAN-10 | Point of Sale is installed with the module that adds the remove-line button enabled, and at least one order has already been paid and validated in the current or a previous session. |
| The reprinted receipt displays all order lines with correct quantities, prices and totals, and no remove-line button appears on any line. |