Practical No.

Aim: Prepare test plan for an identified Mobile application.

Theory:
Introduction:
A test plan is a document which describes a scope of testing, test strategy,
objectives, effort, schedule and resources required. Its main purpose is to guide
the whole testing process and used mostly by Project Managers or Test
Engineers. The scope of work is defined at the beginning of the testing process.
A project team should clearly understand what features and functions to be
tested and which ones are out of scope.
The test plan serves as a blueprint to conduct software testing activities as
a defined process which is minutely monitored and controlled by the test
manager. To determine the scope of testing a Manager must take into
consideration the project specification, budget and customer’s requirements.
The given document will cover the planning details for Whatsapp mobile
application to be carried out.

Objectives:
• To ensure that all requirements are met and verify whether every unit
operates as intended.
• Another objective of testing is to test the processing time for all user
operations is in acceptable limits.

Scope:
The primary purpose of these tests is to uncover the limitations of the
systems. To determine the scope of testing, the project specification, budget,
customer’s requirements should be taken into account.
Test Plan and Strategy:
➢ Unit Testing:
The main objective of unit testing is to verify whether every unit operates
as intended. Every unit works as intended.
Entry Criteria:
• the planning phase has been finished
• testable units are available
• all functional requirements have been defined
• the unit testing environment has been set up

Exit Criteria:
• all planned test cases have been covered
• all the bugs found have been reviewed
• the performance of key modules has been tested

➢ System Testing:
System testing is generally conducted after Unit Testing. The objective
of System Testing is to evaluate compliance of an integrated application with its
requirements. Ensures that the modules in Whatsapp application work in
tandem. Data flow among the units involved and the performance are tested.
Check for the correct navigation order. Ensure the modules within the system
function according to the user requirements.

Types of System Testing :

➢ Performance Testing :
Checks the overall performance of the system and response time for
loading screens, creating a record, updating the record and deleting the
record. Ensures the response time of the system in multi-user environment.
Performing testing is conducted to detect issues related to:
• memory consumption
• power utilization
• network connectivity
• operating in the background
• switching between applications
• memory leakage
➢ Interrupt Testing :
Examines how Whatsapp application reacts to interruption and resumes
to its previous state. There are numerous reasons that can potentially
interrupt the operation of app, such as getting a phone call, messages,
notifications, battery low, etc.

➢ Usability Testing :
Checks whether the application is easy to use and understand for the end-
user.

➢ Installation and Launch Testing :

Detect whether there are any issues during the installation, uninstallation,
and updating process. Once the application has been installed, a QA engineer
also checks the launching process.

➢ Functional Testing :
All the functions and features of the application are tested to verify
whether they operate according to the specification.

➢ Security Testing :
Ensures that only authorized users can access the system. This check
ensures that the user doesn’t have access to any modules, which they are not
supposed to have. Security testing is conducted to find the application
vulnerabilities and prevent data breaches.

➢ Regression Testing :
Re-execution of tests in whatsapp application that had been done before
the code changes.

➢ Pass/Fail Criteria :
Each and every screen is checked against the Technical Review checklist
and Test Cases. All the conditions when tests pass or fail are defined and
described.

Testing Procedure:
• test cases preparation
• test executions
• bug reporting
Test Scenarios of Whatsapp mobile application :-
Procedure:
1. Analyze the mobile application.
2. Define the Test Objectives.
3. Define the Test Criteria.
4. Resource Planning.
5. Plan Test Environment.
6. Schedule & Estimation.
7. Determine Test Deliverables.

Chat settings test scenario –

1. Verify that user can set chat wallpaper.
2. Verify that user set privacy settings like turning on/off last seen,
offline status, read receipts etc.
3. Verify that user can update notification settings.
4. Verify that user can take the complete chat backup of his chats.
5. Verify that user update his phone number that is used by
application.
6. Verify that user can disable/delete his whatsapp account.

No. of test cases executed:

Upto 6 test cases has been executed and the actual output matches the
expected output. The Pass Criteria is marked.

Approach :

1. Specifications are thoroughly reviewed for correctness, coverage and

completeness.
2. Reviewing the design of system components and their integration to give
business solution.
3. Identification of units of application for testing
4. Creation and maintenance of test environment
5. Preparation of checklists and test case specifications for units subject to
testing.
Risks and Assumptions :
Risks:
The following risks may occur during the mobile app testing process:
• availability of devices
• new features and modification which have not been planned in advance
• changes in requirements
• delays in schedule

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.

Entry and Exit Criteria :

Entry Criteria :
1) the development phase has been finished
2) requirements have been defined and approved
3) test design and tests plan have been created
4) the test environment has been set up
5) all necessary resources are available

Exit Criteria :
• tests cases are executed
• the rate of tests cases passed is satisfactory
• failed test cases are not related to crucial functionality
• tests results have been accepted
• critical defects have been fixed.
Resources Required : Hardware(Computer System/Mobile), Operating
System, Whatsapp Mobile Application.
Exercise:
1) On which basis the Test Approach is decided for any application?
A test approach is the test strategy implementation of a project, defines how
testing would be carried out. Test approach has two techniques:
a) Proactive - An approach in which the test design process is initiated as
early as possible in order to find and fix the defects before the build is
created.
b) Reactive - An approach in which the testing is not started until after
design and coding are completed.

Factors to be considered:

a) Risks of product or risk of failure or the environment and the company.

b) Expertise and experience of the people in the proposed tools and
techniques.
c) Regulatory and legal aspects, such as external and internal regulations of
the development process.
d) The nature of the product and the domain.

2) Define the Test Management.

Test Management refers to the activity of managing the software testing
process. It is the process of testing and validating the software. Test
management most commonly refers to the activity of managing a testing
process.

3) State the use of Test Case Specification. Enlist the Test Case
Specification Identifiers.
Use of Test Case Specification:
1. It specifies the purpose of a specific test, identifies the required inputs
and expected results, provides step-by-step procedures for executing the
test, and outlines the pass/fail criteria for determining acceptance.
2. It defines a test case identified by a test design specification.
 3. It describes a set of test cases, the purpose, inputs, test actions, expected
results and execution preconditions for the object under testing.
Test Case Specification Identifiers are as follows:
1. Some type of unique company generated number to identify the test case
specification, its level and the level of software that it is related to.
2. Unique “short” name for the case.
3. Version date and version number of the case.
4. Version Author and contact information.
5. Revision history.

4) Enlist the parameters that should be considered while preparing Test

Summary Report.
Parameters that should be considered while preparing Test Summary Report:
1. Purpose of the document.
2. Overview of an Application.
3. Testing Scope.
4. Metrics.
5. Types of testing performed.
6. Information of Test Environment and Tools.
7. Lessons Learned.
8. Recommendations.
9. Best Practices.
10. Exit Criteria.
11. Conclusion/Sign Off.
12. Definitions, Acronyms and Abbreviations.

Conclusion: Hence, from this practical we learnt how to prepare a test plan for
an identified Mobile application.