Scribd
Upload
29 views9 pages

Test Plan

test plan

Uploaded by

kartikjaiswal1065
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
29 views9 pages

Test Plan

test plan

Uploaded by

kartikjaiswal1065
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

TEST PLAN

 It is a document which drives all the future testing activities.


 It is generally prepared by Test manager/Test lead/Sr TE
 It has got different sections like:
1. Objective
2. Effort Estimation
3. Scope
4. Approach
5. Assumption
6. Risk
7. Backup plan/ Mitigation plan
8. Testing methodology
9. Schedule
10.Test environment
11.Defect tracking
12.Test automation
13.Deliverables
14.Entry and exit criteria
15.Test stop criteria
16.Role and responsibilities
17.Templates

1) Objective: This section covers aim of preparing the test plan

2) Effort estimation: This section covers estimation of how long it will take to
complete the project & also we estimate how many engineers are needed & the
cost needed to complete the task and the cost of testing.

3) Scope: This section covers what are the features to be tested and what are the
features not to be tested.
4) Approach: This section covers how we are going to test the product in future.
5) Assumption: This section covers assumptions that we have made while planning.
6) Risk: This section covers if any assumptions fail that becomes risk.
7) Backup Plan/ Mitigation plan: This section covers how to overcome (or) how to
face the risk.

8) Test methodology: This section covers what are the types of testing that we are
planning to conduct.

9) Test Schedule: This section covers when exactly we should start and end and
activity.
10) Test Environment: This section covers how we go about setting up the test
environment in future (or) how we setup the environment in future.
Ex: 12.1 Procedure to install the build

12.2 Hardware
12.3 Software
11) Defect Tracking: This section covers in future when we find defects how it
should be tracked and also covers the procedure, status, severity and priority.
11.1) Procedure to track the defect
-----------------------
-----------------------
-----------------------

11.2) Severity
Blocker
Critical
Major
Minor

11.3) Priority
High
Medium
Low

11.4) Defect tracking tool that we are planning to


use
12) Test Automation: This section covers what are the features to be automated &
what are the features not to be automated & the complete automation strategy.
Ex: 6.1 Features to be Automated
---------------------------
---------------------------
6.2 Features not be automated
-----------------------
6.3 Automation framework you are planning to use
----------------------
----------------------
6.4 Automation tool that you are planning to use
Selenium
-------------------
-------------------

13) Deliverables: This section covers which all documents that has to be provided by
the testing team at the end of test cycle.
Ex: Test cases, Traceability matrix, test execution report, defect report, release
note, graphs & matrices.
Release Note: Last day along with the product, we release a note to the customer
called as release note.
Release note consists of:

1. List of open defects which are there in the product.

2. List of bugs that are found in the previous release production and fixed
in the current release.
3. List of pending bugs in previous release & fixed in current release 4.
List of features added, modified or removed in current release.
5. Procedure to install the software.
6. Version of the product.

Graphs & matrices:


Graphs:
a. Defect density (or) defect distribution graph

b. Build-wise defect distribution graph

c. Defect trend analysis graph

Metrices:
It is the past data collected between two parameters so that we can analyze and
take better decision to perform future activities.

14) Entry & Exit Criteria:


Entry criteria: This section covers list of criteria that should be met to start the
activity.
Exit criteria: This section covers list of criteria that should be met to say that activity
is over.
Ex:

System study:
Entry criteria for system study:
1. Should have got approved requirement from customer
2. Should have assigned engineers to do system study

Exit criteria for system study:

1. Should have completed reading the requirement.


2. Should have got answers for all the queries.

Prepare Test Plan:


Entry criteria for test plan:
1. Test plan template should be ready.
2. Should have assigned someone to prepare test plan & review the test plan.
3. Should have met the exit criteria of system study.

Exit criteria for test plan:


1. Should have got approval for test plan.

Write Test case:


Entry criteria for writing test case:
1. Test case template should be ready.
2. Should have met exit criteria of test plan.
3. Should have assigned the module to engineer.

Exit criteria for writing test case:


1. Test case should be reviewed, approved & stored in repository.

15) Test stop criteria: This section covers when exactly we should stop testing.
We stop testing when the product quality is very good or product quality is very
bad
• Product quality is very good means if all the end-to-end business scenarios
are working fine.
• If there are no blocker or critical defects.
• There are few bugs left out which are all minor or major but are less than the
acceptable limit set by the customer.
• If all the features requested by the customer are ready
• Product quality is bad means there are too many blocker & critical bugs.
• If it is crossing the budget.
• If it is crossing the schedule/deadline.

16) Roles & responsibility: This section covers what each engineer should do in
different stages of test life cycle.
Roles and responsibilities of Test manager:
 Write and review Test plan.

• Interact with testing team, development team, if needed with customer.


• Should handle all the issues and escalations.
• He should approve release note.
Roles and responsibilities of Test lead:
• Write and review Test Plan.
• Allocate work to each engineer and make sure that they are going to work
and complete the task within the schedule.
• Consolidate all the reports which are sent by every TE and communicate
with testing team, development team, project manager and customer.
• He conducts impact analysis meeting.

Roles and responsibilities of Test Engineer:

• Write Test case


• Review test case of another test engineer.
• Execute test case for his allocated features.

17) Templates: This section covers formats for all the documents that we are
planning to prepare in the entire test life cycle.

i. Test case template


ii. Traceability matrix template
iii. Defect report template
iv. Test case review template
v. Test execution report template
interview:
1. Who will write the test plan?
Test Lead/ Test Manager

2. Who will review the test plan?


Customer, development team or test engineers
3. Who will approve the test plan?
Customer/ Project Manager

You might also like