Table of Contents

1. INTRODUCTION……………………………………………………………………………………………………………………………….2

1.1 Purpose……………………………………………………………………………………………………………………………………………..2

1.2 Project Overview…………………………………………………………………………………………………………….…………………2

2. IN-SCOPE…………………………………………………………………………………………………………………………………………2

2.1 Out of Scope …………………………………………………………………………………..………………………………………………..2

3. TEST ASSUMPTIONS………………………………….……………………………………….……………………………………………3

3.1 Key Assumptions…………………………………………………………………………………….…………………………………………3

3.2 General Assumptions……………………………………………………………………………………………..…………………………3

4. TEST SCHEDULE……………………………………………………………………………………………………………………………….3

4.1 Test Scenario…………………………………………………………………………………..…………………………………………………3

4.2 Test Case…………………………………………………………………………………………………………………….……………………3

4.3 Test Data………………………………………………………………………………………………………………………………………….3

4.4 Test Execution…………………………………………………………………………….…………………………………………………..3

4.5 Test Cycle………………………………………………………………………………………………………………………………………..3

4.6 Start Date………………………………………………………………………………………………………………………………………..3

4.7 End Date……………………………………………………………………………………………………….………………………………..3

5. ROLES AND RESPONSIBILITIES…………..…………………………………………………………….………………………………3

5.1 Project Manager……………………………………………………………………………………………………………………………..4

5.2 Test Lead………………………………………………………………………………………………………………….……………………..4

5.3 Development Personnel………………………………………………………………..…………………………………………………4

5.4 Tester……………………………………………………………………………….………………………………………………… …………..4

5.5 Business Analyst……………………………………………………………………………………………………………………………..5

6. TEST DELIVERABLES………………………………………………………………….…………………………………………………….5

6.1 Test Plan…………………………………………………………………………………………..……………………………………………..5

6.2 Functional Test Cases………………………………………………………………………………………………………………………5

6.3 Test Scenario……………………………………………………………………………………………………………………………………5

6.4 Daily/Weekly Status Report……………………………………………………………………………………………………………..5

6.5 Test Closure Report………………………………………………………………..………………………………………………………..5

7. Test Environment………………………………………………………………….………………………………………………………..5

8. Test Tools…………………………………………………………………………………..……………………………………………………6

9. Defect Management……………………………………………………………….………………………………………………………6

9.1 Critical Defect…………………………………………………………………………….……………………………………………………6

9.2 High Priority Defect………………………………………………………………………………………………………………………….6

9.3 Medium Priority Defect………………………………………………………………..………………………………………………….6

9.4 Low Priority Defect…………………………………………………………………………………………………………………………..7

10. ENTRY CRITERIA…………………………………………………………………………………………………………………………….7

11. EXIT CRITERIA…………………………………………………………………………….…………………………………………………7

INTRODUCTION

PURPOSE

This test plan describes the testing approach and overall framework of the GLOVO application:

 Test Strategy: A test strategy is a collection of recommendations that explain the test design and
testing procedures.
 Test Management:Test management refers to organizing and controlling test to ensure high-grade
software app testing.

PROJECT OVERVIEW

The Glovo application specializes in last-mile logistics, primarily connecting users with
businesses, and couriers, offering on-demand services from local restaurants, grocers and
supermarkets, and high street retail stores via its mobile app.

IN SCOPE

Our test plan covers the following areas

1. Regression testing: - This involves ensuring that previous functionality of our application is
working as expected and that recent changes have not produced any bugs.
2. Integration testing: - The main purpose of integration testing is to check that individual modules
work together correctly when combined.
3. System testing: - This entails testing the whole system. All of the modules/components are
linked together to see whether the system performs as planned. After Integration Testing,
System Testing is carried out.
4. Acceptance testing: - This will be conducted to confirm that specification requirements are met.

OUT OF SCOPE
In this document we will not be covering:

Non-functional testing

TEST ASSUMPTIONS

KEY ASSUMPTIONS

All production Live data required are available in the system prior to start of Functional Testing

GENERAL ASSUMPTIONS

 Exploratory Testing will be carried out on the Live App.

 Performance testing is not considered for this estimation.
 The Test Team will be provided with valid login details.
 The test team are to check all possible cases for proper test conduct.

TEST SCHEDULES

This outlines the following

SCHEDULE REMARKS
Test Scenario This describes the test of the functionality of the Glovo app to be tested e.g.
Verify if the enter button is clickable or not.
Test cases A set of instructions that the tester is expected to follow to achieve a specific
output during the software testing.
Test data This is information that will be used as input to perform the tests for identifying
and locating the defects in the Glovo application.
Test execution This will be carried out to ensure the fulfillment of the requirements and
specifications of the software.
Test cycles Two cycles will be performed during the functional testing. This will ascertain
that any likely bugs identified in the first will be fixed in the second.
Start date 1st of july 2023
End date 15th of july 2023
TEST LEAD
Welcoming the testers at the beginning of new test run and thanking them in the end of the run in the
workspace chat

Addressing the issues raised by testers in workspace chat, mostly within two hours (not during night hours)

Checking the run feedback from testers

 Building and leading the testing team to the success of the project.
 Develop test strategy and test plans for projects
 Participate in developing and reviewing the test policies for organization.
 Defining the scope of testing within the context of every release and every software testing level or
cycle.
 The use of resources in an effective way and managing the resources for software testing.
 Applying the appropriate test measurement and metrics for the software product and testing team.
 Identify and resolve the project risks in testing team

DEVELOPMENT PERSONNEL

 Review testing deliverables (test plan, cases, scripts, expected results, etc.) and provide timely
feedback.
 Assist in the validation of results.
 Support the development and testing processes being used to support the project.
 Certify correct components have been delivered to the test environment at the points specified in
the testing schedule.
 Keep project team and leadership informed of potential software delivery date slips based on the
current schedule.
 Define processes/tools to facilitate the initial and ongoing migration of components.

TESTER

 Gather the test requirements

 Review the project documents to understand the requirements and identify the errors

 Assist the Test Lead to prepare the test plan

 Setup and verify the test environment

 Test the software at different levels and record the results

 Identify, report and track the defects

 BUSINESS ANALYST

 Work with Testing team to create test plans

 Create and execute the system test cases

 Review test cases prepared by Testing team

 Provide requirements clarifications when required by Testing Team.

TEST DELIVERABLES

At the completion of the test activities the following will be made available.

S/No. Deliverable Name Author Reviewer

1. Test Plan Test Lead Project Manager/ Business Analyst’s

2. Functional Test Cases Tester Business Analyst’s Sign off

3. Test Scenario Business analyst Test Lead

4. Daily/weekly status report Tester/ Test Lead Test Lead

5. Test Closure report Test Lead Project Manager

TEST ENVIRONMENT

The test cases will be run on these environment

Android phone and iphone, web.

TEST TOOLS
The test tools to be used include

Microsoft Word & Microsoft Excel

DEFECT MANAGEMENT

In the process of testing, when a defect is identified it is the responsibility of the Defect Manager to
review the severity of the defects and facilitate with the technical team the fix and its implementation,
communicate with testers when the test can continue or should be halt, request the tester to retest,
and modify status as the defect progresses through the cycle.

And we would be categorizing these defects into four parts,regression testing, integration testing,
system testing, and acceptance testing

Regression testing: This involves ensuring that previous functionality of our application is working as
expected and that recent changes have not produced any bugs.

Integration Testing: This will involve checking individual components or units of a software project to
expose defects and problems to verify that they work together as designed.

System Testing: The process in which a quality assurance (QA) team evaluates how the various
components of an application interact together in the full, integrated system or application.

Acceptance Testing: This test technique will be performed to determine whether or not the software
system has met the requirement specifications.

ENTRY CRITERIA

The team will be able to verify the availability of the test data and their readiness for use.

EXIT CRITERIA

No open Critical and High severity defects were detected.

Test environment cleanup were completed and a new back up of the environment initiated.