Uber Eats Application Test Plan: Components, Scenarios, and Testing

This report presents a comprehensive test plan for the Uber Eats application, detailing various components and scenarios to ensure its functionality and user experience. The plan covers a range of features, including checking fund availability, the mobile interface, estimated time of arrival (ETA) of food, order customization, order tracking, communication with the driver, and restaurant categorization. The testing methodology incorporates black box, white box, and grey box testing approaches to validate the application's performance. Each component is broken down into specific scenarios, with corresponding test cases that outline the test ID, priority, description, pre-conditions, test steps, test data, expected results, and status. The report also includes recommendations for enhancing the user interface, such as saving previous orders and adding payment options. The conclusion emphasizes the importance of application testing for a user-friendly experience. The report is a sample report contributed by a student on Desklib, a platform providing AI-based study tools and solved assignments.

Running Head: TEST PLAN
Application Test Plan of Uber Eats
Name of the Student
Name of the University
Author Note

1TEST PLAN
Table of Contents
Overview..........................................................................................................................................2
Introduction......................................................................................................................................2
Testing.............................................................................................................................................3
Components and Scenario...............................................................................................................3
Test Case..........................................................................................................................................5
Component 1: Check Funds Availability....................................................................................5
Component 2: Mobile Interface...................................................................................................6
Component 3: ETA of Food........................................................................................................8
Component 4: Customizing the order........................................................................................10
Component 5: Tracking the Order.............................................................................................11
Component 6: Communicating with the Driver........................................................................12
Component 7: Categorizing Restaurants...................................................................................13
Acquisition and preferred method.................................................................................................14
Recommendation...........................................................................................................................15
Conclusion.....................................................................................................................................15
Reference.......................................................................................................................................16

2TEST PLAN
Overview
Application testing is a type of software testing that aims to find errors in the application.
In this process the entire application is tested. It enhances the overall quality of the application,
saves the time for development and reduces cost (Stafford 2016). The testing is carried out so
that the application can operate smoothly and meet its requirements. In the application testing,
there exists several phases in the lifecycle of testing with the components of test planning, test
execution, requirement analysis, bug reporting and test design (Veen, Barratt and Goods 2019).
There are three methodologies that are applicable for application testing such as black
box testing, white box testing and the grey box testing.
Introduction
Uber Eats is an online based application that is a food delivery platform, it gets the food
from the restaurants to the end user as per their order placed through the application (DeBruyne
2017). This application provides several features such as it offers the option of several
restaurants, availability of different payment method, Real time order tracking facility, shows
continuous order status, easy user interface and order scheduling (Kirubakaran and Karthikeyani
2013).
The test plan will discuss the various features of the application along with the
components like checking the fund availability, mobile interface, estimated time of arrival of the
food, customizing the order, Tracking the order, communicating with the driver and categorizing
restaurants (Sahu and Pawa 2019).

3TEST PLAN
Testing
The methods of application testing is required to ensure the credibility of the application and
organised method can lead to stable product at the end. There are three ways of carrying out of
the testing are:
Black Box Testing- This test usually used for functional, non-functional and regression testing.
It is independent of the way that the input transformation to output or the internal structure
(Khatri et al. 2015). The strategies that are used in this testing are Decision Table, equivalence,
state transition and boundary value testing.
White Box Testing- This testing is used for the purpose of checking the internal security holes,
functionality of the loops, structure of the paths and checks the code of the application (Kurian et
al. 2017). The strategies used are path coverage and code coverage analysis.
Grey Box Testing- It is carried out combining both the above testing and finds the defects in the
structure of the application.
Components and Scenario
There exists several components in the application of Uber Eats and those can be tested
individually (Dudley, Banister and Schwanen 2017). The associated scenarios of the components
are evaluated to understand the system functionality.
The components and scenarios of the Uber Eats application will be tested are:
1. Check Funds Availability
 Check fund
 Generate report

4TEST PLAN
2. Mobile Interface
 User registration
 User log in
 Food searching
3. ETA of food
 Average delivery time
 Delivery instruction
4. Customizing the order
 Availability of food options
 Customization of dish
5. Tracking the order
 Real- time tracking
6. Communication with the driver
 Contacting through call and message
7. Categorizing restaurants
 Customizing according to location
 Customization according to veg or non-veg food.

5TEST PLAN
Test Case
Component 1: Check Funds Availability
Scenario 1: Check fund
Test Case ID C001
Priority High
Designer Uber Technologies Inc.
Description of Test The availability of the fund can be checked.
Pre-condition The funds are available or not
Test steps Open application
Check fund in the wallet section
Test Data Opens app
Go to profile
Check wallet
Expected Result Shows the available amount
Post-Condition Valid user can check his fund and cash backs in the app
Status Pass
Comments Balance is shown in the wallet section
Scenario 2: Generate Report
Test Case ID C002
Priority High
Designer Uber Technologies Inc.
Description of Test Check if the report is generated or not

6TEST PLAN
Pre-condition Presence of the fund details
Test steps Open app
Opens profile section
Opens wallet option
Test Data App opening
Wallet option checked
Payment method: Paytm or Cash
Transactions are available
Expected Result Transaction report can be obtained
Post-Condition Valid user can see his transactions of funds
Status Pass
Comments The user can manage funds through variable payment options
Component 2: Mobile Interface
Scenario 1: User Registration
Test Case ID C003
Priority High
Designer Uber Technologies Inc.
Description of Test Check whether new user can register in the app or not
Pre-condition The user must be new and have the detains ready for
registration
Test steps Open the App

7TEST PLAN
Enter Contact Number
Obtain the OTP and enter it
Input personal detail
Register
Test Data 5162659465
Daniel Radcliff
33, session road, UK
Expected Result Registration successful message
Post-Condition User can search for food
Status Pass
Comments Access granted by the admin
Scenario 2: User Log in
Test Case ID C004
Priority High
Designer Uber Technologies Inc.
Description of Test User log in again after registration
Pre-condition The contact number must be valid
Test steps Open the application
Enters the valid contact number
Test Data 5162659465
Expected Result Pop up od welcome
Post-Condition Valid contact number can log in

8TEST PLAN
Status Pass
Comments Notify user of successful log in
Scenario 3: Food Searching
Test Case ID C005
Priority High
Designer Uber Technologies Inc.
Description of Test Searching of food in the application
Pre-condition The entered food for searching must be valid
Test steps Enter the name of the food or restaurant in the search section
Options are shown with categories
Favourable option is chosen
Test Data Chines
80 Restaurants available
Click on one restaurant
Expected Result Menu is available
Post-Condition User can search for food as per cuisine or restaurant
Status Pass
Comments Easily favoured food and restaurant can be searched
Component 3: ETA of Food
Scenario 1: Average Delivery Time
Test Case ID C006

9TEST PLAN
Priority Medium
Designer Uber Technologies Inc.
Description of Test After placing order the arrival time is provided by the app
Pre-condition The order must be accepted by the restaurant
Test steps Order placed
Pop up option of estimated time of arrival
Test Data Crispy fish with chilly honey Sauce
ETA- 45 min.
Expected Result The time is given by the app in the past order section
Post-Condition Order details with ETA is available in the Upcoming order
section.
Status Pass
Comments Average delivery time is available for users’ convenience
Scenario 2: Delivery Instruction
Test Case ID C007
Priority Medium
Designer Uber Technologies Inc.
Description of Test Check if the user can provide instruction of the delivery
Pre-condition Options must be available to the user
Test steps After Order placed
Option to customize delivery timing by adding notes
Test Data Note: Do not ring bell when reach my location

10TEST PLAN
Expected Result Delivery confirmed with considering note.
Post-Condition The order is placed with note.
Status Pass
Comments Notification for order confirmation
Component 4: Customizing the order
Scenario 1: Availability of food
Test Case ID C008
Priority High
Designer Uber Technologies Inc.
Description of Test Check whether the desired food in available through the app
Pre-condition Enter valid name of the food
Test steps Open search window
Type the food name
Check availability of food in desirable restaurant
Test Data Pasta with white sauce
Expected Result Available in 40 restaurants
Post-Condition Desirable food is available
Status Pass
Comments Options are displayed
Scenario 2: Customization of Dish

11TEST PLAN
Test Case ID C009
Priority Medium
Designer Uber Technologies Inc.
Description of Test Check if customization of a particular dish is available or not
Pre-condition Options for customization must be available
Test steps Opens application
Search for food
Customize the food
Place order
Test Data Pasta is searched from the search section
Customization option: Add white sauce and jalapeno
Expected Result Order accepted
Post-Condition Order is confirmed from the restaurant
Status Pass
Comments Order confirmation message is pop-up
Component 5: Tracking the Order
Scenario 1: Real-time tracking
Test Case ID C010
Priority High
Designer Uber Technologies Inc.
Description of Test Check if the place order can be tracked or not
Pre-condition GPS of the device must be activated