Hello Devs, I am currently working on creating sanity test documentation for the following areas:
- Order Entry (Sales Orders and Purchase Orders) - Order Fulfillment (Sales Orders) The goal of this document is to serve as a reference and guideline for performing quick validation checks during tag or version releases. We already have an existing document on the OFBiz wiki: https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Sanity+Test I believe we can expand and refine it further for these targeted functional areas. At present, I am focusing on defining high-level test scenarios for creating Sales Orders from the backend. Below are the initial test cases I have drafted: *Sales Order Entry – High-Level Validation Scenarios:* - Verify that the user can select the Product Store and Sales Channel to initiate the order. - Verify that a customer can be searched and selected using the lookup functionality. - Verify that entering the Product ID and Quantity correctly adds the item to the cart. - Verify that the added product appears in the cart with the correct quantity and price. - Verify that a success message is displayed after adding an item to the cart. - Verify that a new shipping address can be created and saved for the customer. - Verify that an existing shipping address can be selected from the available list. - Verify that a shipping method (e.g., UPS Guaranteed Next Day) can be selected. - Verify that a payment method (e.g., Offline, COD, or Credit Card) can be selected. - Verify that the order review screen displays the correct product details, quantity, and total amount. - Verify that clicking "Create Order" generates a unique Order ID. - Verify that the system navigates to the Order View page after order creation. - Verify that the order initially has a "Created" status and displays the "Approve Order" option for COD or Offline payments. - Verify that the order status is automatically set to "Approved" when a Credit Card payment is successfully processed. I would appreciate your feedback on these scenarios, including any suggestions for improvement or additional cases that should be considered. We can further discuss how to incorporate your inputs into the document. Please note that this is intended to be a high-level sanity checklist to ensure that core functionality is working as expected, and it does not cover detailed or exhaustive test cases. I will also be sharing similar test scenarios soon for Purchase Order creation and Sales Order fulfillment. Thanks in advance for your time and input. Kind Regards, Arpit Mor Business Analyst & Quality Engineer *HotWax Systems* *Enterprise open source experts* office: 0731-3622711 http://www.hotwaxsystems.com
