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.
Importance of Test Plan
Making Test Plan has multiple benefits
• Test Plan helps us determine the effort needed to validate the
quality of the application under test
• Help people outside the test team such as developers, business
managers, 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 it 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
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 Test Criteria
4. Define the Test Objectives
5. Resource Planning
6. Plan Test Environment
7. Schedule & Estimation
8. Determine Test Deliverables
,Step 1) Analyze 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 Guru99 banking website. You should research
clients and the 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 analyze the site
, Now let’s apply above knowledge to a real product: Analyze the
banking website http://demo.guru99.com/V4.
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.
Importance of Test Plan
Making Test Plan has multiple benefits
• Test Plan helps us determine the effort needed to validate the
quality of the application under test
• Help people outside the test team such as developers, business
managers, 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 it 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
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 Test Criteria
4. Define the Test Objectives
5. Resource Planning
6. Plan Test Environment
7. Schedule & Estimation
8. Determine Test Deliverables
,Step 1) Analyze 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 Guru99 banking website. You should research
clients and the 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 analyze the site
, Now let’s apply above knowledge to a real product: Analyze the
banking website http://demo.guru99.com/V4.
