Complete Order Class

[Taghunter98]

Ticket Title: Complete Order Class for Item Ordering and Checkout System

Priority: High

Description: This ticket focuses on completing the implementation of the Order class within the JavaGo package. The goal is to finalise the order workflow, including item selection, basket management, checkout, and payment processing.

Related Issue: #Order-Class-Development (link to the corresponding issue)

Current State:

• The order method allows the user to select items from the menu and add them to the basket.
• The total price of the items is tracked, and the system provides an option to either go back to the menu or proceed to checkout.
• Terminal class is being used to manage the UI in the console.

Tasks:

1. Order Number Generation:

   • Implement a method to generate a random orderNumber. The format should resemble something like ORD123456.

2. Server Name Input:

   • Prompt the user to enter the server's name, which will be displayed on the receipt.

3. Payment Process:

   • Add a method for handling payment where the user is asked to input payment details (you can mock the payment process).
   • Ensure the paymentSuccess boolean is updated based on the user’s response or mock validation.

4. Receipt Generation:

   • Once the payment is successful, print a receipt that includes:
     • User's name and order number.
     • List of all items ordered, along with prices.
     • Total price.
     • Server name.
     • Payment confirmation status.
   • Format the receipt clearly using the Terminal.printHeader() method for a structured view.

5. Error Handling:

   • Handle cases where the user enters an invalid item name.
   • Handle invalid input for returning to the menu or proceeding to checkout.
   • Ensure that invalid input for payment is managed, and the user can retry.

6. Code Refactoring:

   • Move some logic (e.g., checking if an item exists) into separate helper methods to make the order method cleaner and easier to maintain.

Acceptance Criteria:

• The Order class should allow users to browse a menu, add items to the basket, and checkout.
• A random orderNumber should be generated for each order.
• The user should be able to input the server’s name.
• The payment process should be simulated, and a receipt should be printed on successful payment.
• Edge cases such as invalid inputs for item names or payment should be properly handled.
• The code should be clean and modular, with some logic moved into helper methods.

Test Plan:

• Write unit tests to validate the following:
  1. Item selection correctly adds the item to the order and updates the total.
  2. Correct generation of order numbers and handling of server names.
  3. Payment flow behaves as expected, including success and failure cases.
  4. Receipt is printed with correct formatting and information.

[Taghunter98]

Changes

• Added random id generation
• Refactored code in smaller methods
• Added payment method with checks to payment class
• Receipt is now generated