PCM 120 Day4 2023.pdf - AGENDA 2.5 Identify methodology for...

FOUNDATIONS OF SYSTEM
DEVELOPMENT LIFE CYCLE
PCM 120
AGENDA
2.5 Identify methodology for testing the project
plan.
2.6 Identify how to assess the project using risk
management.
2.7 Describe an effective approach to sell the
project plan to stakeholders.
Ruchika Aggarwal
Week 2, Day 2

Test Plans
Test planning is the practice of preparing for the testing phase of product
development to ensure that what is delivered to the client indeed satisfies
the requirements as agreed upon in the requirement and design
specification documents. The test plan helps prepares those with a stake
in the tests by setting stakeholder expectations and documenting the
agreed-upon testing approaches.
The project test plan is a document that outlines for project stakeholders
the product functions to be tested, what specific tests will be performed,
the approach to be taken for those tests, what to test and what not to test,
how the tests will be performed, who will be responsible for performing
each test, what results are expected, what is considered a successful test
and a failed test, and exit criteria for any series of tests as well as for the
testing phase as a whole. A well-defined test plan must also describe, in
explicit detail, the method, goals, approaches, etc to be used for each test.
What is the Importance of a Test Plan?
Making a Test Plan document has multiple benefits
•
Help people outside the test team such as developers, business
managers, and customers understand the details of testing.
•
Test Plan guides our thinking. It is like a rule book, which needs to
be followed.
•
Important aspects like test estimation, test scope, test
Strategy are documented in Test Plan, so they can be reviewed by
Management Team and re-used for other projects.
How to write a Test Plan
You already know that making a Test Plan is the most important task of
the Test Management Process. Follow the seven steps below to create a
test plan as per IEEE 829
1. Analyze the product
2. Design the Test Strategy
3. Define the Test Objectives

4. Define Test Criteria
5. Resource Planning
6. Plan Test Environment
7. Schedule & Estimation
8. Determine Test Deliverables
Step 1) Analyse the product
How can you test a product without any information about it? The answer
is Impossible. You must learn a product thoroughly before testing it.
The product under test is a banking website. You should research clients
and end users to know their needs and expectations from the application
•
Who will use the website?
•
What is it used for?
•
How will it work?
•
What are software/ hardware the product uses?
You can use the following approach to analyse the site

Step 2) Develop a Test Strategy
Test Strategy is a critical step in making a Test Plan in Software Testing.
A Test Strategy document is a high-level document, which is usually
developed by Test Manager. This document defines:
•
The project’s testing objectives and the means to achieve them
•
Determines testing effort and costs
Back to your project, you need to develop Test Strategy for testing that
banking website. You should follow steps below
Step 2.1) Define Scope of Testing
Before the start of any test activity, scope of the testing should be known.