ePractical 12

1. Test Plan
Test Plan Topic: WhatsApp application test plan
Prepared By: Kumud Patil
Date: 14/12/2021
1.0 Introduction:
The popularity of WhatsApp as a preferred social media platform in the so-called global
South, and in rural areas, has often been related to economic constraints and poor
broadband infrastructure which limit everyday online communication to the use of
smartphones and messaging, with the additional factor that some mobile phone plans
allow people to use these apps for free .Some have argued, WhatsApp proved attractive
in these markets because it offered a cheap alternative to SMS and conventional voice
calls . But WhatsApp has also been enthusiastically taken up by urban middle class
individuals with disposable income and fast Internet connections, and with considerable
experience of using mainstream social media platforms to communicate. For these
people, it is not cheap one-on-one messaging, but other functions of the app, such as
the group messaging feature and encryption, that are likely to be enticing them to turn
to WhatsApp for everyday online interactions.
WhatsApp groups allow personal connections and conversations to take place between
groups of up to 256 users. They afford connectivity, facilitate the formation of collective
identities, and give rise to networks of weak and strong ties. This feature makes the app
more like a social network rather than just a text messaging or voice call service. As
people use it to communicate in and through groups, the app gives rise not only to new
kinds of one-to-one talk, as well as corporate and public service messaging, but also to
new kinds of collective life and sociability. Although the average WhatsApp group is
fewer than 10 people ,research suggests that in countries like Brazil and India these
numbers are higher
2.0 Objectives and Tasks
2.1 Objectives:
Functional correctness. Validation that the application correctly supports
required business processes and transactions. List all of the business
processes that the application is required to support. Also list any standards
for which there is required compliance.
Authorization. Verification that actions and data are available only to those
users with correct authorization. List any key authorization requirements that
must be satisfied, including access to functionality and data.

2. Service level. Verification that the system will support the required service
levels of the business. This includes system availability, load, and
responsiveness. List any key performance indicators (KPIs) for service level,
and the level of operational effort required to meet KPIs.
Usability. Validation that the application meets required levels of usability.
List the required training level and user KPIs required.
2.2 Tasks:
 Writing test cases for application
 Executing them on the application
 Noting down the actual result
 Comparing them with expected result.
 Updating Status.
3.0 Scope:
3.1 General:
The scope of work is defined at the beginning of the testing process. A project team should
clearly understand what features and functions there are to be tested and which ones are out
of scope. To determine the scope of testing, the project specification, budget, and customer’s
requirements should be taken into account.

3. 3.2 Tactics:
Sr No. Component Start Date End Date Member
1 Messaging Component 15-12-2021 15-12-2021 Kumud Patil
2 Send Video
Component
15-12-2021 15-12-2021 Kumud Patil
3 Send Audio
Component
15-12-2021 15-12-2021 Kumud Patil
4 Send Files Component 15-12-2021 15-12-2021 Kumud Patil
5 Create & Add Contact 15-12-2021 15-12-2021 Kumud Patil
6 Create & Add Group 15-12-2021 15-12-2021 Kumud Patil
7 Add People in Group 15-12-2021 15-12-2021 Kumud Patil
8 Add Status 15-12-2021 15-12-2021 Kumud Patil
9 Watch Status 15-12-2021 15-12-2021 Kumud Patil
4.0 Testing Strategy:
4.1 Major Activities
User mode selection
Mode vs Computer testing
Mode vs User testing
Win And Loose condition testing.
Draw condition testing.
Reset Button Testing.

4. 4.2 Techniques:
 Unit Testing
Definition:
A unit test is a way of testing a unit - the smallest piece of code that
can be logically isolated in a system. In most programming languages, that is
a function, a subroutine, a method or property. The isolated part of the
definition is important.
Participants: Kumud Patil.
 Methodology:
In order to do Unit Testing, developers will write a section of code to
test a specific function in a software application. Developers can also isolate
this function to test more rigorously which reveals unnecessary
dependencies between functions being tested and other units so the
dependencies can be eliminated.
Methodology is the study of research methods, or, more formally, "'a
contextual framework' for research, a coherent and logical scheme based on
views, beliefs, and values, that guides the choices researchers [or other
users] make".
It comprises the theoretical analysis of the body of methods and
principles associated with a branch of knowledge such that the
methodologies employed from differing disciplines vary depending on their
historical development. This creates a continuum of methodologies[5] that
stretch across competing understandings of how knowledge and reality are
best understood. This situates methodologies within overarching
philosophies and approaches.[6]

5.  System and Integration Testing Definition:
System Integration testing is defined as a type of software testing carried out
in an integrated hardware and software environment to verify the behavior of
the complete system. It is testing conducted on a complete, integrated system
to evaluate the system’s compliance with its specified requirement.
System Tests Integration Tests
Intention To guarantee that the total build fulfils
the business specifications.
To guarantee that joined units
can act together without
problems.
Type Non-functional and functional type of
test. It falls in the acceptance testing
class.
Functional type of test. It’s not in
the acceptance testing class.
Technique Black box testing White and black box testing or
Gray box testing
Level Three (3) Two (2)
Value Helps to identify system errors. Helps to identify interface errors.
Teams
involved
Developers and Testers QA
Participants: Kumud Patil
Methodology:
System testing is a black box testing method used to evaluate the completed
and integrated system, as a whole, to ensure it meets specified requirements.
Performance and Stress Testing
Definition:
Performing testing is conducted to detect issues related to:
 memory consumption
 power utilization
 network connectivity
 operating in the background
 switching between applications
 memory leakage
Participants: Kumud Patil

6. Methodology:
Performance testing, a non-functional testing technique performed to
determine the system parameters in terms of responsiveness and stability
under various workloads.
Automated Regression Testing
Definition:
Regression testing is the selective retesting of a system or component to verify
that modifications have not caused unintended effects and that the system or
component still works as specified in the requirements.
Participants: Kumud Patil
Methodology:
The first stage of regression testing we select test cases for is a Focused
Regression. It covers – or focuses on – the specific functionality around the new
or modified code. The regression testing of affected areas is done in tandem with
the functional testing of the new or modified pieces.
5.0 HARDWARE REQUIREMENTS
Hardware Minimum Requirement
Processor 4 core Processor
Memory 4 GB
Disk Space 40 GB
Bandwidth ( network connection ) 20 Mbps

7. 6.0 Environment Requirements:
6.1 Main Frame:
Lenovo Ideapad Slim 3
6.2 Workstation:
7.0 Test Schedule:
Sr
no.
Details of Activity Plan start
Date
Plan End
Date
Name of team
Member
1 Messaging Component 15-12-2021 14-12-2021 Kumud Patil
2 Send Video Component 15-12-2021 14-12-2021 Kumud Patil
3 Send Audio Component 15-12-2021 14-12-2021 Kumud Patil
4 Send Files Component 15-12-2021 14-12-2021 Kumud Patil
5 Create & Add Contact 15-12-2021 15-12-2021 Kumud Patil
6 Create & Add Group 15-12-2021 15-12-2021 Kumud Patil
7 Add People in Group 15-12-2021 15-12-2021 Kumud Patil
8 Add Status 15-12-2021 15-12-2021 Kumud Patil
9 Watch Status 15-12-2021 15-12-2021 Kumud Patil
10 Messaging Component 15-12-2021 15-12-2021 Kumud Patil
12 Send Video Component 15-12-2021 15-12-2021 Kumud Patil
13 Send Audio Component 15-12-2021 15-12-2021 Kumud Patil
14 Send Doc & Pdf Component 15-12-2021 15-12-2021 Kumud Patil

8.  Problem Reporting
Document the procedures to follow when an incident is encountered during the
testing process. If a standard form is going to be used, attach a blank copy as an
"Appendix" to the Test Plan. In the event you are using an automated incident
logging system, write those procedures in this section.
 Change Requests
Document the process of modifications to the software. Identify who will sign off on
the changes and what would be the criteria for including the changes to the current
product. If the changes will affect existing programs, these modules need to be
identified.

9. 9.0 FEATURES TO BE TESTED
Features Priority Description
Launch Application 1 To make sure that application executes
successfully.
Enter the number to be logged in
with
1 Make sure the number is 10 digit.
Enter your Profile name 1 Check the inputed text is not empty
Create or Add Contact 1 Add Contact from Phone or Create new
Contact
Message to the Added Contact 1 Send messages to contacts
Use Emojis from chat keyboard 1 Send Emojis to contacts from keyboard
Use gifs from chat keyboard 1 Send gifs to contacts from keyboard
Send Files Component 1 Sends files to selected contact
Create & Add Group 1 Creates Group and Adds People
Send Audio Component 1 Sends Audio file to selected contact
Send doc or pdf Flie 1 Send doc or pdf to selected contact

10. 10.0 FEATURES NOT TO BE TESTED
We will try to test every feature. But if we can't manage the schedule. Then we may
skip those features and attributes with low priority below :
Features Description
Auto updating What’s App gets refreshed in particular duration of time
Search Search Contact or messages
11.0 RESOURCES/ROLES & RESPONSIBILITIES
It defines the complete task which needs to be performed by the entire testing team. When
a large project comes, then the Test Manager is a person who writes the test plan. If there
are 3-4 small projects, then the test manager will assign each project to each Test Lead. And
then, the test lead writes the test plan for the project, which he/she is assigned.
Let see one example where we will understand the roles and responsibility of the Test
manager, test lead, and the test engineers.
Role: Test Manager
Name: Kumud Patil
Responsibility:
 Prepare( write and review) the test plan
 Conduct the meeting with the development team
 Conduct the meeting with the testing team
 Conduct the meeting with the customer
 Conduct one monthly stand up meeting

11.  Sign off release note
Role: Test Lead
Name: Kumud Patil
Responsibility:
 Prepare( write and review) the test plan
 Conduct daily stand up meeting
 Review and approve the test case
 Prepare the RTM and Reports
 Assign modules
 Handling schedule
Role: Test Engineer 1, Test Engineer 2 and Test Engineer 3
Name: Kumud, Sanchit , Swaraj
Assign modules: M1, M2, and M3
Responsibility:
 Write, Review, and Execute the test documents which consists of test case and test
scenarios
 Read, review, understand and analysis the requirement
 Write the flow of the application
 Execute the test case
 RTM for respective modules
 Defect tracking
 Prepare the test execution report and communicate it to the Test Lead.

12. 12.0 SCHEDULES
It is used to explain the timing to work, which needs to be done or this attribute covers
when exactly each testing activity should start and end? And the exact data is also
mentioned for every testing activity for the particular date.
Therefore as we can see in the below image that for the particular activity, there will be a
starting date and ending date; for each testing to a specific build, there will be the specified
date.
Major Deliverables
Identify the deliverable documents. You can list the following documents:
 Test Plan
 Test Cases
 Test Incident Reports
 Test Summary Reports
13.0 SIGNIFICANTLY IMPACTED DEPARTMENTS (SIDs)
Department/Business Area Bus. Manager Tester(s)
14.0 DEPENDENCIES
Dependencies in Test Plan depend on the part of the proof-of-concept cycle. Proof-of-
concept cycle consists of three cycles: first-build cycle, second-build cycle and final cycle. In
the first-build cycle, it's production of the system test plans. In the second-build cycle, it's
production of the subsystem test plans. In the final cycle, it's acceptance of the tests.

13. Dependencies in Test Plan is a list out the dependencies associated with phase and any risks
that may exist pertaining to these.
15.0 RISKS/ASSUMPTIONS
4.1 Risks
The following risks may occur during the WhatsApp application testing process:
 availability of devices
 new features and modification which have not been planned in advance
 changes in requirements
 delays in schedule
4.2 Assumptions
 each release is accompanied by a note with information about implemented
features and their impact on the system
 all blocker bugs receive the high priority status
 all the bugs found are fixed before the next software release
 all documents are up-to-date and delivered to the testing team in time
 all necessary equipment and tools are provided and ready for testing
 the test schedule is reviewed in case there are any obstacles for testing
16.0 TOOLS
1. Android Operating System,
2. Android Phone .
3. WhatsApp Application

14. 17.0 APPROVALS
Specify the names and titles of all persons who must approve this plan. Provide space for
the signatures and dates.
Name (In Capital Letters) Signature Date

15. Practical No.8
Prepare test plan for an identified Mobile Application.
SR.
NO
Test Steps Test Data Executed Result Actual Result Status
1 Check the
internet
connection
- Internet is working
fine
There is an
internet
connection
Pass
2 Check your
computer are
in working
condition
Plugin it to power
supply
Computer
should be
working
Computer
is working
Pass
3 Click on create
Account
- - Click on it Pass
4 Try to Enter
name
Name- Kumud “Enter your full
Name” message
must be display
Enter your
full Name
Pass
5 Enter your Full
Name
Name – Kumud
Kundan Patil
Name should be
accepted
Data
accepted
Pass
6 Enter mobile
number
93077730311 Phone number
Should be
Accept
Data
accepted
Pass
7 Enter more
than 10 digits
mobile
number
9193077730311 “Enter correct
phone no and try
again” message
must be display
Enter correct
phone
number
Pass

16. 8 Enter Email
Address
Email-
Kumud534@gmail.
com
Email should be
accepted
Data
Accepted
Pass
9 Try with blank
Email Address
Email-________ “Enter Email
address” message
should be display
Enter Email
address
Pass
10 Enter
Password and
then confirm
password
Password-******
Confirm password-
******
Password should
be accepted
Data
accepted
Pass
11 Enter
password and
not enter
confirm
password
Password-******
Confirm Password-
_______
“Please confirm
your
password”message
should be display
Date
Accepted
Pass
12 Enter
password and
enter wrong
confirm
password
Password-******
Confirm password-
********
“Password don’t
match” message
should be display
Password
don’t match
Pass
13 Click on Login
Account
- - Click on it Pass
14 Enter Valid
Email
Address/Usern
ame
Email id-
abc23@gmail.com
Username-
@_abc43_
Userbname/Email
id should be
accepted
Data
accepted
Pass
15 Enter Invalid
Email
Address/Usern
ame
Email id-
pqr43@gmail.com
Username-
@_pqr53_
“We can’t find an
account with
_pqr53_.try again”
message should be
display
Try again Pass
16 Enter
password
Password-****** Password should
be display
Data display Pass

17. 17 Enter wrong
password
Password-**** “Enter correct
Password and try
again”message
should be display
Enter correct
password
Pass