ANDROID EMULATION TESTING REPORT FOR URBAN LUNCH APP
PRODUCT OVERVIEW
Urban Lunch is an app designed to personalize business lunches by combining orders from different restaurants in the city. The app was created to address the lack of variety in business lunches offered by single-cuisine restaurants. With Urban Lunch, users can mix and match dishes from multiple restaurants into one order, providing a diverse dining experience.
Key Features
Variety in One Order:
Combine dishes like gazpacho, sushi, and mango mousse with chia in a single order.
Simple Process:
- Select a restaurant as the pick-up point.
- Choose dishes from a comprehensive list.
- Confirm the order.
Efficient Delivery:
Couriers collect the prepared dishes from the respective restaurants, bring them to the pick-up point, and pack them carefully for the customer to collect and enjoy.
TESTING PROCESS
The testing process included automated scripts to verify the functionality of key features, ensuring that users could select multiple restaurants, combine dishes, and complete the order process without issues. Test cases covered user interactions, validation checks, and edge cases to ensure a robust and reliable app experience.
Selecting a pick-up location
- Ensure no pick-up points are selected by default.
- Check highlighting and selection of pick-up points upon tap.
- Confirm repeated tap cancels selection.
- Ensure selecting a new pick-up point updates the selection.
- Verify selected pick-up point name displays in the footer.
Choosing and adding dishes
- Ensure no dishes are pre-selected by default.
- Verify highlighting and selection of dishes upon tap.
- Confirm repeating tap cancels selection.
- Ensure adding selected dishes to the basket and proceeding to checkout is possible.
Choosing and adding restaurants
- Verify no restaurants are pre-selected by default.
- Ensure highlighting and selection of restaurants upon tap.
- Confirm selecting a new restaurant updates the selection.
- Verify selected restaurants display on the summary page.
Summary page
- Ensure order details are correct before confirmation.
- Verify order summary displays selected dishes, pick-up point, and restaurants.
- Confirm option to edit the order before finalizing.
- Ensure submitting the order leads to a confirmation screen.
Final Confirmation
- Verify confirmation message displays after order submission.
- Ensure confirmation details include pick-up point, selected dishes, and restaurants.
| Test Case Description | Status |
|---|---|
| The map shows the pickup points | PASSED |
| Ensure no pick-up points are selected by default | PASSED |
| Check highlighting and selection of pick-up points upon tap | PASSED |
| Confirm repeated tap cancels selection | PASSED |
| Ensure selecting a new pick-up point updates the selection | PASSED |
| Verify selected pick-up point name displays in the footer | PASSED |
| Confirm drop-down list contains all restaurants | PASSED |
| Validate each dish item displays the name, -/+, and arrow buttons | PASSED |
| Ensure tapping on the list (except +) navigates to the dish details screen | PASSED |
| Verify clicking + adds the dish to the order list from the nearest restaurant to the pick-up point | PASSED |
| Verify clicking + adds the dish amount without any errors in the GUI | FAILED |
| Check the order progress displayed in the footer | PASSED |
| Ensure "Next" button in the footer is inactive if no dishes are in the order list and active otherwise | PASSED |
| Verify the return arrow navigates back to the dish list | PASSED |
| Confirm tapping the restaurant name adds the dish to the order list | PASSED |
| Ensure the dish list is scrollable if it exceeds screen length | PASSED |
| Verify the total amount calculation includes the price of all prepared dishes and delivery | FAILED |
| Confirm tapping the "Order" button navigates to the order tracking screen | PASSED |
| Validate the map displays pick-up points, restaurant locations, and routes | PASSED |
| Ensure the list of dishes and associated restaurants are displayed and scrollable | FAILED |
| Confirm the final cost (Amount) matches the sum of ordered dishes | PASSED |
| Verify automatic switch to the "Order is delivered" screen when the timer expires | PASSED |
| Ensure the map shows the correct pick-up point location | FAILED |
| Test error message for denied geolocation access | PASSED |
| Verify error message when attempting to order without adding dishes | PASSED |
| Confirm clicking "I got the order" button marks the order as completed, shows a feedback bar, and redirects to the initial screen for a new order | PASSED |
| Ensure the costs of each product match the costs outlined in the requirements | FAILED |
| Ensure the delivery time countdown matches the advertised delivery time when ordering | FAILED |
ANALYSIS OF FAILED TEST CASES
1. Verify clicking + adds the dish amount without any errors in the GUI
- Issue Description:
When increasing the quantity of the "Tomato Soup with Croutons" item using the + button, the price text overlaps with the restaurant name when the quantity exceeds 9 items. This issue worsens when the quantity exceeds 99 items, causing further overlap and making it difficult for users to read the information clearly. - Impact:
Poor user experience due to UI elements overlapping, leading to potential confusion and frustration when placing large quantity orders. - Recommendation:
- UI Adjustment: Modify the GUI layout to dynamically adjust the placement of price text based on the quantity selected, ensuring it does not overlap with adjacent elements.
- Testing Focus: Conduct thorough GUI testing with varying quantities of all menu items to ensure no overlaps occur across different screen sizes and resolutions.
2. Verify the total amount calculation includes the price of all prepared dishes and delivery
- Issue Description:
The total amount displayed on the order confirmation screen did not consistently include delivery costs or accurately sum up the prices of all ordered dishes. In some instances, delivery charges were omitted from the total, leading to incorrect billing. - Impact:
Financial discrepancies and user dissatisfaction when the total amount billed does not match the expected sum, potentially affecting trust in the app's payment system. - Recommendation:
- Backend Validation: Review the backend calculation logic to ensure all components of the order, including delivery fees, are correctly factored into the total amount.
- Integration Testing:Perform comprehensive integration testing to validate that the final calculated amount accurately reflects the cost of all ordered items and associated fees.
3. Tracker Screen: Long dish names are cut off, and quantities are not aggregated
- Issue Description:
On the order tracking screen, long dish names are not fully visible and get cut off. Additionally, multiple items of the same dish are listed individually rather than aggregating the quantity ordered into a single line item (e.g., "Dish Name x3"). - Impact:
This results in a cluttered and unclear order tracking screen, making it difficult for users to understand their orders and potentially causing confusion. - Recommendation:
- UI Enhancement: Implement text truncation with ellipsis for long dish names to ensure they fit within the allocated space. Aggregate quantities for the same dish to display them as a single line item.
- Testing and Validation: Conduct extensive UI testing to verify the display of long dish names and quantity aggregation across different screen sizes and resolutions.
4. Ensure the costs of each product match the costs outlined in the requirements
- Description:
The Vegan Beet Burger was listed at $25 per burger on the ordering screen, whereas the requirement document lists it at $15 per burger. When ordering two Vegan Beet Burgers, the total was incorrectly displayed as $30. - Impact:
This discrepancy in pricing can lead to overcharging customers and potential loss of trust in the app's accuracy. - Recommendation:
- Pricing Correction: Review and correct the pricing logic for all products to ensure they match the requirements. Conduct thorough testing to validate the displayed prices against the requirement document.
5. Ensure the delivery time countdown matches the advertised delivery time
- Issue Description:
The delivery time countdown did not match the advertised delivery time when placing an order, leading to inconsistencies in the order tracking. - Impact:
Incorrect delivery time estimates can lead to customer dissatisfaction and reduced trust in the app's reliability. - Recommendation:
- Time Calculation Correction: Review and correct the delivery time calculation logic to ensure it accurately reflects the advertised delivery times. Test with various order scenarios to validate the consistency of the delivery time countdown.
CONCLUSION
The Urban Lunch app was tested extensively using Android Studio and a Virtual Pixel 5 emulator with API 31. While most test cases passed successfully, several critical issues were identified, particularly concerning UI display, total amount calculation, and pricing discrepancies. Addressing these issues will improve the app's usability, accuracy, and overall user experience.
Go Back To Home Page