Enatega App: Order History Bug Report

Introduction

This document details a critical bug found within the Enatega Customer Application, specifically affecting the order history functionality. The issue causes significant confusion and frustration for users as it displays incorrect order information. This can lead to a loss of trust in the application and potentially impact user retention. The bug manifests in two primary ways: first, the order history persistently shows details of an old order from 'The Dessert Table' restaurant, regardless of the user's actual order history; second, when a new order is placed, the current order number is incorrectly replaced with a previous order number. This report outlines the steps to reproduce the bug, the expected behavior, and provides additional context to aid in its resolution.

Bug Description

The Enatega Customer Application exhibits a significant flaw in its order history feature. After a customer places an order from any restaurant within the application, navigating to the order history section often reveals details of a very old order specifically from the restaurant named 'The Dessert Table.' This occurs irrespective of the customer's actual recent orders. Furthermore, when a new order is placed, the application incorrectly updates the current order number, replacing it with a number from a previous order. This misrepresentation of order information poses a serious usability issue, potentially leading to order discrepancies and customer dissatisfaction. The persistence of the 'The Dessert Table' order details suggests a potential issue with data caching or incorrect database querying, while the incorrect order number assignment points to a flaw in the order processing logic. Addressing this bug is crucial for maintaining the integrity of the application and ensuring a positive user experience.

The impact of this Enatega app bug on the user experience cannot be overstated. Customers rely on accurate order history to track their purchases, confirm order details, and manage their spending. When the order history displays incorrect information, users may become confused about the status of their orders, leading to frustration and potentially contacting customer support for clarification. This not only creates an inconvenience for users but also increases the workload for support staff. The persistent display of 'The Dessert Table' order, even after placing orders from other restaurants, indicates a significant issue with data handling within the application. This could stem from a faulty database query, an issue with data caching, or a problem with the way order information is stored and retrieved. The incorrect order number assignment further exacerbates the problem, making it difficult for users to track their current orders and potentially leading to delivery issues or order mix-ups. Therefore, resolving this bug is essential for ensuring a smooth and reliable user experience within the Enatega Customer Application. The development team should prioritize investigating the root cause of this issue and implementing a fix as quickly as possible. This includes thoroughly reviewing the application's database interaction, data caching mechanisms, and order processing logic to identify and rectify the underlying problem.

Reproducing the Enatega Customer Application Order History Bug is relatively straightforward, making it easier for developers to identify and address the issue. By following a series of steps, one can consistently replicate the erroneous behavior. First, the user must launch the Enatega Customer Application on their mobile device. Once the application is open, the user should select any restaurant from the available options and proceed to place an order as they normally would. After the order has been placed, the user should navigate to the profile menu, typically located in the bottom navigation bar or a similar intuitive location. Within the profile menu, there should be an option labeled 'Order History' or a similar phrase indicating past orders. Selecting this option should display a list of the user's previous orders. However, this is where the bug manifests. Instead of showing the current or most recent order, the order history will likely display the details of an old order from the restaurant 'The Dessert Table,' regardless of which restaurant the user actually placed their recent order with. Furthermore, if the user checks the details of their current, in-progress order, they will likely find that the order number displayed does not match the actual order number assigned to their recent purchase. This discrepancy between the displayed order number and the actual order number can lead to further confusion and difficulty in tracking the order.

Steps to Reproduce

1. Go to 'Enatega Customer Application.'
2. Click on any restaurant.
3. Place an order.
4. Go to the profile menu button.
5. Select 'Order History' under 'My Orders.'
6. Check 'Current Orders' details and match its order number with your order which is in progress.

Expected Behavior

Under 'Current Orders,' the application should display the current/in-progress orders and not previous orders. Additionally, the order details, including the order number, must accurately match the current order.

Actual Behavior

The application consistently shows details of an old order from 'The Dessert Table,' regardless of the user's actual order history. When a new order is placed, the current order number is incorrectly replaced with a previous order number.

Supporting Evidence

A screen recording demonstrating the bug can be found at WhatsApp.Video.2025-01-15.at.11.49.12.AM.mp4.

The expected behavior of the Enatega Customer Application's order history feature is that it should accurately reflect the user's current and past orders. When a user navigates to the 'Order History' section, they should see a chronological list of their orders, with the most recent orders appearing at the top. Each order entry should display relevant details such as the restaurant name, order date and time, order total, and a unique order number. For current or in-progress orders, the application should provide real-time updates on the order status, such as 'Order Placed,' 'Order Confirmed,' 'Preparing,' 'Out for Delivery,' and 'Delivered.' The order number displayed for each order should be unique and should accurately correspond to the order placed by the user. This allows users to easily track their orders and refer to them if they have any questions or concerns. In contrast to the current buggy behavior, where users are shown outdated information or incorrect order numbers, the expected behavior ensures a seamless and transparent ordering experience. Users should be able to rely on the order history to provide an accurate record of their transactions and the status of their orders. This builds trust in the application and encourages continued usage. When the order history functions as intended, it empowers users to manage their orders effectively, track their spending, and resolve any potential issues with ease. The development team should prioritize restoring this expected behavior to ensure a positive user experience and maintain the integrity of the Enatega Customer Application.

Device Information

• Device: [e.g., Infinix Hot 50]
• OS: [e.g., Android]
• Browser: [e.g., Application]
• Version: [e.g., 22]

The device information provided is crucial for the development team to effectively debug and resolve the issue. Knowing the specific device, operating system, browser (if applicable), and application version helps narrow down the potential causes of the bug. For example, the bug might be specific to a particular device model due to hardware or software incompatibilities. Similarly, the operating system version can play a role, as certain bugs might only manifest on specific OS versions due to changes in APIs or system behavior. If the application uses a web browser component, knowing the browser version is also important, as browser-specific issues can arise. The application version is essential for tracking whether the bug was introduced in a recent update or has been present in previous versions. This information allows developers to focus their efforts on the relevant areas of the codebase and testing environments. For instance, if the bug is only reproducible on a specific device model and OS version, the development team can prioritize testing on that configuration. If the bug was introduced in a recent update, they can examine the changes made in that update to identify the potential source of the problem. Therefore, providing detailed device information is a critical step in the bug reporting process, as it significantly aids in the efficient resolution of the issue. The development team can use this information to create a targeted testing strategy, reproduce the bug in a controlled environment, and ultimately implement a fix that addresses the root cause of the problem.

Conclusion

The Enatega Customer Application exhibits a critical bug within its order history functionality. This bug causes the application to display incorrect order information, leading to user confusion and potential frustration. The primary manifestations of the bug include the persistent display of an old order from 'The Dessert Table' and the incorrect assignment of order numbers for current orders. The steps to reproduce the bug are straightforward, involving placing an order and then navigating to the order history section within the application. The expected behavior is that the order history should accurately reflect the user's current and past orders, with correct order details and status updates. However, the actual behavior deviates significantly from this expectation, hindering the user's ability to track their orders effectively. The provided screen recording and device information offer valuable context for the development team to investigate and resolve this issue. Addressing this bug is crucial for ensuring a positive user experience, maintaining trust in the application, and preventing potential order-related complications. The development team should prioritize identifying the root cause of the bug, implementing a fix, and thoroughly testing the solution to prevent future occurrences. The integrity of the order history feature is paramount to the overall usability and reliability of the Enatega Customer Application, and its prompt resolution is essential for maintaining customer satisfaction and the application's reputation.

For more information on mobile app bug reporting and testing best practices, you can visit Mobile App Testing Guide.