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 | pos#1427 KAN-5 | Point of Sale with the POS RMA module installed and a POS session open. An existing POS order with at least one order line is available in the Product/Ticket screen. |
| The RMA is created successfully and is linked back to the originating POS order, so it can be traced from that order. | ||
| Return quantity cannot exceed the quantity sold | pos#1427 KAN-5 | Point of Sale with the POS RMA module installed and a POS session open, with an existing POS order line whose sold quantity is known. |
| The RMA is not created; the return quantity is rejected because it exceeds the originally sold quantity. | ||
| Reason is required before submitting the RMA | pos#1427 KAN-5 | Point of Sale with the POS RMA module installed and a POS session open, with an existing POS order line. |
| The RMA cannot be submitted while the reason is empty; submission is only allowed once a reason is provided. | ||
| Cashier without the group performs a blind closing | pos#1495 KAN-6 | The pos_blind_session_closing module is installed. A user who does NOT have the "Can see POS closing amounts" group enabled in the Extra Rights tab of their user record, and who can open a POS session. |
| The closing screen is blind: expected cash amounts are hidden and only counted amounts can be entered. | ||
| Authorized user sees expected closing amounts | pos#1495 KAN-6 | The pos_blind_session_closing module is installed. A user exists who can open a POS session. |
| The user with the group sees the existing closing view showing expected amounts alongside the counted amounts. | ||
| Order summary panel visible on the Payment Screen | pos#1514 KAN-4 | The module that displays the order on the Payment Screen is installed. A POS session is open with a user able to register orders. |
| A read-only panel is displayed on the right side of the Payment Screen showing all order lines with their quantities and prices, matching the order that was registered. | ||
| Panel updates when the order is modified before payment is finalized | pos#1514 KAN-4 | A POS session is open and an order with at least two lines has been taken to the Payment Screen. |
| The order panel reflects the modification immediately, showing the updated lines, quantities, and prices. The panel remains read-only (it cannot be edited directly). | ||
| Payment flow and keypad behavior unchanged, no configuration needed | pos#1514 KAN-4 | At least two different POS configurations exist, with the module installed. No additional setup has been made on either configuration. |
| The payment flow and keypad behave exactly as before the change and the payment is validated normally. The order panel is present on the Payment Screen in both POS configurations without any additional setup. | ||
| Sales Order PDF prints automatically after conversion when the setting is enabled | pos#1523 KAN-7 | A POS configuration with the "Order to Sale Order" feature available; access to the POS settings and to a POS session where an order can be converted to a sale order. |
| The setting is available in the "Order to Sale Order" configuration section and can be enabled. After the POS order is converted to a sale order, printing of the Sales Order PDF is triggered automatically. | ||
| Behavior unchanged when the setting is disabled | pos#1523 KAN-7 | A POS configuration with the "Order to Sale Order" feature available and the option to print the sales order PDF on conversion disabled. |
| The sale order is created and no Sales Order PDF print is triggered; the conversion behaves exactly as in the current release. | ||
| Sale order created from a POS order shows Full delivery status after pickings are validated | pos#1536 KAN-8 | Point of Sale is available with the POS order to sale order conversion feature enabled, and a product that is tracked in stock (requires delivery) is available for sale. |
| The sale order's delivery status is 'Full' (fully delivered) once all of its pickings have been validated, instead of remaining empty or stale. | ||
| Products that do not require delivery tracking are unaffected by the conversion | pos#1536 KAN-8 | Point of Sale is available with the POS order to sale order conversion feature enabled, and a product that does not require delivery tracking is available for sale. |
| The sale order is created as before, with no change in behavior for the product that does not require delivery tracking. | ||
| Remove a line from a previously-synced POS order | pos#1552 KAN-9 | A point of sale session is open with the picking-keep module installed. An order has been created in the session and has already been synced to the backend (for example, by opening it from the backend while it remained open in the session). |
| The order line is removed and the point of sale session continues to work without crashing; the sale can be completed and is not blocked. | ||
| Picking-keep behavior for a new, unsynced order | pos#1552 KAN-9 | A point of sale session is open with the picking-keep module installed. |
| The existing picking-keep behavior for new or unsynced orders works exactly as before, with no change or error. | ||
| Module installs cleanly on 18.0 | pos#1566 KAN-11 | An 18.0 environment is available with the point of sale application, and the early receipt printing module is available for installation. |
| The module installs successfully on 18.0 with no errors or warnings raised during installation, and it is shown as installed afterwards. | ||
| Existing early receipt printing behavior is preserved after migration | pos#1566 KAN-11 | The early receipt printing module is installed on the 18.0 environment, and a point of sale session can be opened. |
| The module behaves exactly as it did in the prior version; no change in behavior is observed. | ||
| Module version information is updated | pos#1566 KAN-11 | The early receipt printing module is installed on the 18.0 environment. |
| The module's version information reflects the 18.0 release and the README/description content is present and up to date. | ||
| Remove-line button is hidden on the order receipt | pos#1597 KAN-10 | A Point of Sale session is open with the module that adds the remove-line button installed. |
| No remove-line button appears next to any line on the order receipt, and the receipt layout is otherwise displayed normally with no visual regression. | ||
| Remove-line button still works on the active order screen | pos#1597 KAN-10 | A Point of Sale session is open with the module that adds the remove-line button installed. |
| The remove-line button is visible on the active order screen and removing the line works as before. | ||
| Module installs cleanly on 18.0 | pos#1601 KAN-12 | An 18.0 environment with the point of sale application available and the migrated product expiry module for POS available for installation. |
| The module installs without errors or warnings and shows as installed on the 18.0 environment. | ||
| Expiry date display in the POS frontend is unchanged | pos#1601 KAN-12 | The POS product expiry module is installed on 18.0, and a point of sale session can be opened with at least one product that has expiry tracking information. |
| The expiry date is displayed and behaves exactly as it did before the migration, with no visible differences or errors in the POS frontend. | ||
| Check a gift card balance from the Payment screen | retail-pos-demo#37 KAN-49 | A gift card has been issued and its number and balance are known (for example GC-0001 with $25.00). An order has items added and the tester is on the Payment screen. |
| The card's balance is shown next to the box, for example "GC-0001 has $25.00 left.". The tester stays on the Payment screen, and the order, the chosen payment method and the typed number are all still as they were. Nothing on the card or the order is changed by the check. | ||
| Balance check with a blank, unknown, or differently formatted number | retail-pos-demo#37 KAN-49 | An order is in progress, the tester is on the Payment screen with Gift card chosen, and a valid issued gift card number is known. |
| The blank number shows "Enter the gift card number.". The unknown number shows "No gift card with that number.". The number typed with different capitalization and spaces is accepted and shows the card's balance, the same as when paying. | ||
| Remaining balance shown in the confirmation and on the receipt after paying by gift card | retail-pos-demo#38 KAN-49 | A gift card has been issued with a known balance, and an order is ready to pay for an amount less than that balance. |
| The confirmation ends with the card's remaining balance, for example "GC-0001 has $14.72 left.". The receipt shows a "Gift card balance" line with the amount left on the card after the sale. | ||
| Orders not paid by gift card and older orders show no balance line | retail-pos-demo#38 KAN-49 | At least one order exists that was placed before this change (or an order can be completed using a payment method other than gift card). |
| No remaining gift card balance appears in the confirmation or on the receipt for the order not paid by gift card, and the older order shows no "Gift card balance" line. | ||
| Store address and phone appear on the receipt | retail-pos-demo#39 KAN-50 | Access to the Settings screen and to at least one order with a receipt that can be opened. |
| The address and the phone number are shown under the store name on the receipt. | ||
| Blank contact details and the 80-character limit | retail-pos-demo#39 KAN-50 | Settings already has a Store address and Store phone saved, and a receipt can be opened. |
| With both boxes blank the receipt shows nothing extra under the store name. Entering more than 80 characters is not accepted and the message "Keep the address and phone number under 80 characters." is shown. | ||
| Search orders by date range | retail-pos-demo#40 KAN-50 | Several orders exist on different days, including orders on the first and last day of the range to be searched. |
| Only orders from the selected days are listed, with both the From and the To day included. Searching with only one of the two date boxes filled also lists orders and the other box may be left blank. When a date range is combined with the order number or product search, only orders matching both the dates and the search text are listed. | ||
| Reversed date range and Export CSV | retail-pos-demo#40 KAN-50 | Several orders exist on different days and the Orders screen is open. |
| The screen says "The From date is after the To date." and no orders are listed. Export CSV still exports every order regardless of the dates entered. | ||
| Add an order note, complete the sale and see it on the receipt | retail-pos-demo#41 KAN-51 | Cashier is signed in at the Register with items available to add to an order. |
| The note is saved with the completed order and appears on the receipt as "Note: …". After the sale, the "Order note" box is empty for the next order. | ||
| Completing a sale without a note | retail-pos-demo#41 KAN-51 | Cashier is signed in at the Register with items available to add to an order. |
| The sale completes normally with the note left empty, as the note is optional, and no "Note: …" line is shown on the receipt. | ||
| A held order keeps its note and gets it back when resumed | retail-pos-demo#41 retail-pos-demo#42 KAN-51 | Cashier is signed in at the Register with items available to add to an order. |
| The note typed before holding is stored with the held order and is shown again in the "Order note" box when the order is resumed. | ||
| Resuming a held order that had no note | retail-pos-demo#42 KAN-51 | Cashier is signed in at the Register with items available to add to an order. |
| The "Order note" box is empty when the order is resumed. |