The document outlines the steps to create a software test plan, including analyzing the product, developing a test strategy, defining objectives and criteria, planning resources and the test environment, creating a schedule and estimates, and determining deliverables. It emphasizes that a test plan is a blueprint that ensures testing activities are properly monitored and controlled. Key benefits of a test plan include preventing missed issues and ensuring quality and requirements compliance.

1. Software Test Planning

2. Group 6
• GROUP MEMBERS:
Muhammd Haris
Wajid Ali
Abdul Moiz
Sohaib Riaz

3. What is a Test Plan?
• A test plan is a detailed document that outlines the test
strategy, Testing objectives, resources (manpower, software,
hardware) required for testing, test schedule, Test
Estimation and test deliverables. 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.

4. Importance of Test Plan
• Making Test Plan has multiple benefits
It also ensures that test engineers are not
missing any issues.
It ensures the good quality of the product.
Test Plan ensures that software meets the
requirements.
Test Plan helps the customers to understand
the details of testing.

5. How to write a Test Plan
Making a Test Plan is the most important task of Test Management
Process. Following the steps to create a test plan
• Analyze the product
• Develop the Test Strategy
• Define the Test Objectives
• Define Test Criteria
• Resource Planning
• Plan Test Environment
• Schedule & Estimation
• Determine Test Deliverables

6.  Analyze the product
• This phase should focus on answering the following
questions:
 Who will use the product?
 What is the primary purpose of this product?
 How does the product work?
 What are the software and hardware specifications?
• In this stage, do the following:
 Interview clients, designers, and developers
 Review product and project documentation
 Perform a product walkthrough

7.  Develop Test Strategy
• The Test Strategy document is developed by the test manager
and defines the following:
 Project objectives and how to achieve them.
 The amount of effort and cost required for testing.
More specifically, the document must detail out:

8. • Scope of Testing: Contains the software components
(hardware, software, middleware) to be tested and those that
will not be tested.
• Type of Testing: Describes the tests to be used in the project.
This is necessary since each test identifies specific types of
bugs.
• Risks and Issues: Describes all possible risks that may occur
during testing – tight deadlines, poor management,
inadequate or erroneous budget estimate – and the effect of
these risks on the product or business.
• Test Logistics: Mentions the names of testers (or their skills)
and the tests to be run by them. This section also includes the
tools and the schedule laid out for testing.

9.  Define Test Objective
• Test Objective is the overall goal and achievement of the test
execution. The objective of the testing is finding as many
software defects as possible; ensure that the software under
test is bug free before release. To define the test objectives,
you should do 2 following steps :
 List all the software features (functionality, performance, GUI…) which
may need to test.
 Define the target or the goal of the test based on above features

10.  Define Test Criteria
• Test Criteria is a standard or rule on which a test
procedure or test judgment can be based.
There’re 2 types of test criteria as :
Suspension criteria
Exit criteria

11. • Suspension criteria: are met during testing, the active test cycle will
be suspended until the criteria are resolved. For Example: If your team
members report that there are 40% of test cases failed, you
should suspend testing until the development team fixes all the failed
cases.
Exit criteria: are criteria that need to be met before testing can finish. For
Example: the test case should finish once each objective has been met and
all bugs have been resolved.

12.  Resource Planning
• This phase creates a detailed breakdown of all resources
required for project completion. Resources include
human effort, equipment, and all infrastructure needed
for accurate and comprehensive testing.
• This part of test planning decides the project’s required
measure of resources (number of testers and
equipment).

13.  Plan Test Environment
• The test environment refers to the software and hardware
setup on which QAs run their tests.
 Ideally, test environments should be real devices so testers can
monitor software behavior in real user conditions.
 Whether it is manual testing or automation testing, nothing
beats real devices, installed with real browsers and operating
systems are non-negotiable as test environments.
 Do not compromise your test results with emulators or
simulators.

14.  Schedule & Estimation
• Break down the project into smaller tasks and
allocate the time and effort required for each.
• Develop a timeline or schedule for the testing
activities.
• Set deadlines for completing key testing tasks.

15.  Determine Test Deliverables
• Test deliverables usually show testing outcomes in a form of
list: the number of tests completed, bugs found, etc.
• We inform a client about the materials they will receive to
witness the results of the work.

16.  Conclusion:
• Test plan plays a crucial role in Software testing and
preparing it is more worth the time and effort as it
makes the entire testing process smooth and more
efficient. There is no standard procedure for writing
test plans and it varies from company to company.

17. THANK YOU!