Test plan For Whatsapp

Index

1. INTRODUCTION
2. BUSINESS BACKGROUND
3. TEST OBJECTIVES
4. SCOPE
5. TEST TYPES IDENTIFIED
6. PROBLEMS PERCEIVED
7. ARCHITECTURE
8. ENVIRONMENT
9. FUNCTIONALITY
10.SECURITY
11.PERFORMANCE
12.USABILITY
13.TEST TEAM ORGANIZATION
14.SCHEDULE
15.CONFIGURATION MANAGEMENT
 Test plan
1. Introduction
This test plan is designed to:
 Describe the approach used by tester during testing.
 Organize and implement the test process.
 Describe the testing strategy and steps.

2. Business Background
 The following product is Meta platforms.
 It is a product from Meta which is freeware, cross platform,
centralized instant messaging and voice-over-IP
 More than 5 billion active users are present on WhatsApp.
 Approximately market value of WhatsApp is around 19 billion dollors

3. Test Objectives
The Objective of this assessment was to check and validate the overall
functionality of the software as per the described requirements. This includes
the functions like proper person to person chatting, proper behavior of whole
system, synchronization between the various functions, voice call and video
call, payment on whatsapp, group setting, privacy setting on whatsapp, voice
messages , linked devices, community setting etc
The main objective is to see the working structure of WhatsApp
application and see the proper synchronization of all features with each
other.

4. Scope
As per objectives, the initial scope is to check all
Major/minor functionalities of the ‘WhatsApp’ software.
Inclusions:
 a. Firstly for testing will be done after development so the black
box testing will be done.
b. The ‘WhatsApp’ itself will be used for testing.
c. The latest version of WhatsApp is used.

Exclusions:
a. The testing approach like white box testing will not be used, because the
‘WhatsApp’ software is already developed.
b. Since some testing can only be done during the development process but
this software is already developed by Meta so some testing like Unit
testing, Integration testing , System testing cannot be done.

5. Test type identified

The software is already developed so the testing like smoke testing is
possible on it. The Black Box Testing can be implemented on this
project/product. Reason of black box testing is we cannot interfere with the
internal structure of the product, because it is already developed.
After this still the acceptance testing, usability testing, UI testing,
performance testing can be used for software.

6. Problems Perceived
a. Test cases were challenging to design while unclear functional
specifications.
b. It was difficult to identify all possible inputs in limited testing
time.
c. It was difficult to identify all possible inputs in limited amount of
time. As result making test case can be slow and difficult.
d. It was difficult to identify tricky inputs because of the test cases are
not developed based on specification.
e. There might be some errors in some internal structure or any logic
which cannot found now by our black box testing.
 7. Architecture
Following is the architecture of WhatsApp application which consist
various modules

8. Environment
The following project was tested in Android operating system as it is a
mobile application. Except that no other special tools or framework were
used for the testing.
9. Functionality
Sr. No Test Scenarios

1. Verify that registering an existing mobile number for new user

account
2. Verify that on successful registration all the contacts in the users
contact directory get imported to WhatsApp contact list
3. Verify that the user can set DP and status on WhatsApp

4. Verify that all the contacts are saved as before

 Test strategy
 Scope
• Reviewing documents, approving documents and carrying out
tests are done by testers, Pratiksha Jadhav, Sakshi Shinde
Test activities Done by Timeline

Analyzing module Pratiksha Jadhav 5 Dec 2022

Creating test case Pratiksha Jadhav 5 Dec 2022
Executing test case Sakshi Shinde 6 Dec 2022
Reviewing test results Sakshi Shinde 6 Dec 2022

 Test approach
• Process of testing:
The first individual module was taken for testing and analyzed. The
module was reviewed and specifications were noted. According to the
main functionality of the module test cases were created and executed.
The output was acknowledged and its status was updated in test cases.
• Roles and responsibilities of each team member
 1. Sakshi Shinde: Analyzing the module and the specifications of
the product.
2. Pratiksha Jadhav: Creating the test cases as per the
requirements and the specifications of the modules.
3. Pratiksha Jadhav: Executing the test cases provided by team
members and getting the results.

Sakshi Shinde: Reviewing the test results and setting a status in test
cases either pass or fail.

• Type of testing:
The functionality testing was done on this module.
• Testing approach used:
The analytical approach was used for the testing. No extra special
automation tools were used in testing, whole testing is done manually.

 Test Environment
Windows operating system was used, any version of windows can be
used. For setup, the ‘Notepad’ is used as it is already installed in
windows. There was no need of backup so nothing for backup was used.

 Testing tools:
For testing no special tools were used, only single ‘Notepad’ was
used.
 Risk analysis.
No risk or defects were found.
 Review
All these activities are reviewed and signed off by the team members.
Everything in this module was perfect and fine. No risks, defects or
bugs were found.
10. Security
Sr. No Scenarios

1. Verify whether the user is able to verify the number successfully or

not.
2. Check that OTP comes within the given time period or not
3. Check OTP when the user enters the wrong OTP

4. Verify the maximum attempt for filling the wrong OTP

5. Verify that when the user enters the mobile number in the WhatsApp
app which is already registered
6. Verify that after the successful verification all elements are properly
visible
7. Verify that all the WhatsApp contact lists showing or not

8. Check whether the user is able to set the DP or not

9. Check that user is able to set the status or not on the WhatsApp app

10. Check that user able to send the WhatsApp message to any WhatsApp
contact
11. Check that user can able to make call to a correct contact

 Risk Identified & Mitigation Planned

-No risk or defects was found after the execution of the test cases.
-Since no risk is found, there is no potential need of testing.
 Test strategy
 Scope:
• Reviewing documents, approving documents and carrying out tests
are done by testers, Pratiksha Jadhav, Sakshi Shinde
Test activities Done by Timeline

Analyzing module Pratiksha Jadhav 7 Dec 2022

Creating test case Pratiksha Jadhav 7 Dec 2022
Executing test case Sakshi Shinde 8 Dec 2022
Reviewing test results Sakshi Shinde 8 Dec 2022

 Test approach
• Process of testing:
The first individual module was taken for testing and analyzed. The
module was reviewed and specifications were noted. According to the
main functionality of the module test cases were created and executed.
The output was acknowledged and its status was updated in test cases.
• Roles and responsibilities of each team member
1. Pratiksha Jadhav: Analyzing the module and the specifications
of the product.
2. Pratiksha Jadhav: Creating the test cases as per the
requirements and the specifications of the modules.
3. Sakshi Shinde: Executing the test cases provided by team
members and getting the results.
4. Pratiksha Jadhav: Reviewing the test results and setting a status
in test cases either pass or fail.
• Type of testing:
The security testing was done on this module.
• Testing approach used:
The analytical approach was used for the testing. No extra special
automation tools were used in testing, whole testing is done manually.
11. Usability
Sr. No Scenarios

1. Check if WhatsApp is easy to use or not

Check whether is Search and calls sections are available on-screen or
2. not

3. Check if the user is able to see all sections individually

Check if the user is able to see unread messages contacts and group-
4. wise
Verify that user can send message to any individual selected from his
5. contact list.
Verify that Chats window contains all the chat list with DP and name
6. and last message preview of the other person with whom chat was
initiated

7. Verify that user can share or receive a contact with the other person
8. Verify that user can send and receive message in group chats

Verify the user can mark chats as favorite and access all chats marked
9. as favorite from the Favorites section.

 Risk Identified & Mitigation Planned

-No risk or defects was found after the execution of the test cases.
-Since no risk is found, there is no potential need of testing.
 Test strategy
 Scope:
• Reviewing documents, approving documents and carrying out tests
are done by testers, , Pratiksha Jadhav, Sakshi Shinde
Test activities Done by Timeline

Analyzing module Pratiksha Jadhav 9 Dec 2022

Creating test case Pratiksha Jadhav 9 Dec 2022
Executing test case Sakshi Shinde 10 Dec 2022
Reviewing test results Sakshi Shinde 10 Dec 2022

 Test approach
• Process of testing:
The first individual module was taken for testing and analyzed. The
module was reviewed and specifications were noted. According to the
main functionality of the module test cases were created and executed.
The output was acknowledged and its status was updated in test cases.
• Roles and responsibilities of each team member
5. Pratiksha Jadhav: Analyzing the module and the specifications
of the product.
6. Pratiksha Jadhav: Creating the test cases as per the
requirements and the specifications of the modules.
7. Sakshi Shinde: Executing the test cases provided by team
members and getting the results.
8. Pratiksha Jadhav: Reviewing the test results and setting a status
in test cases either pass or fail.
• Type of testing:
The usablity testing was done on this module.
• Testing approach used:
The analytical approach was used for the testing. No extra special
automation tools were used in testing, whole testing is done manually.
12.Performance
Sr. No Scenarios

1. Check the WhatsApp performance when the application is

continuously used.
2. Check the WhatsApp performance when the user uses multiple
functions like sending videos, images, and text at the same time
3. Check the WhatsApp performance when users use multiple chats at
same time
4. Check the WhatsApp performance when user send data to multiple
contacts at a same time
5. Check the WhatsApp performance when user use the video call for
longer time

 Risk Identified & Mitigation Planned

-No risk or defects was found after the execution of the test cases.
-Since no risk is found, there is no potential need of testing.
 Test strategy
 Scope:
• Reviewing documents, approving documents and carrying out tests
are done by testers, Pratiksha Jadhav, Sakshi Shinde
Test activities Done by Timeline

Analyzing module Pratiksha Jadhav: 11 Dec 2022

Creating test case Pratiksha Jadhav: 11 Dec 2022
Executing test case Sakshi Shinde 12 Dec 2022
Reviewing test results Sakshi Shinde 12 Dec 2022
  Test approach
• Process of testing:
The first individual module was taken for testing and analyzed. The
module was reviewed and specifications were noted. According to the
main functionality of the module test cases were created and executed.
The output was acknowledged and its status was updated in test cases.
• Roles and responsibilities of each team member
9. Pratiksha Jadhav: Analyzing the module and the specifications
of the product.
10.Pratiksha Jadhav: Creating the test cases as per the
requirements and the specifications of the modules.
11.Sakshi Shinde: Executing the test cases provided by team
members and getting the results.
12.Pratiksha Jadhav: Reviewing the test results and setting a status
in test cases either pass or fail.
• Type of testing:
The performance testing was done on this module.
• Testing approach used:
The analytical approach was used for the testing. No extra special
automation tools were used in testing, whole testing is done manually.

13. Test team organization

Our test team is of four members,
1. Pratiksha Jadhav
2. Sakshi Jadhav

Each member has given some specific responsibilities and roles according to
their skills and knowledge. Every individual member has to perform their
own task to with collaboration to do effective testing with great efficiency.
 14. Schedule
The testing should start from day 1 December 2022 to 10 December 2022
by following specified schedule.

Sr. Testing activity Activity done by Task Task

No. started completed
1. Gathering the information Pratiksha Jadhav 1 Dec 2022 2 Dec 2022
and specification of product. Sakshi Shinde
2. Planning the test and test Pratiksha Jadhav 2 Dec 2022 4 Dec 2022
strategy. Sakshi Shinde
3. Test case development Pratiksha Jadhav 4 Dec 2022 6 Dec 2022
Sakshi Shinde
4. Test environment setup Pratiksha Jadhav 6 Dec 2022 6 Dec 2022
Sakshi Shinde
5. Test case execution Pratiksha Jadhav 7 Dec 2022 9 Dec 2022
Sakshi Shinde
6. Results Review Pratiksha Jadhav 9 Dec 2022 10 Dec 2022
Sakshi Shinde
7. Test Closure Pratiksha Jadhav 11 Dec 11 Dec 2022
Sakshi Shinde 2022
15. Configuration Management
Following software and hardware configurations will be used in testing,

Sr. no. Name Quantity Status

1. Computer system, i5 11gen , 512 1 used

SSD, 8gb ddr4x ram, 3.8gb iris
graphics card
2. WhatsApp version 2.22.24.79 - used

3. Microsoft Excel 2021 - used

4. Microsoft Word 2021 - used