Você está na página 1de 12

TEST PLANNING

TEST PLAN
It is a record of the test planning process.
A document describing the scope, approach, resources and schedule of
intended test activities.
It identifies other test items

the features to be tested


the testing tasks
who will do each task
degree of tester independence
the test environment
the test design techniques
entry and exit criteria to be used
the rationale for their choice
any risks requiring contingency planning

TYPES
master test plan
A test plan that typically addresses multiple test levels.

phase test plan


A test plan that typically addresses one test phase

Testing Level Specific Test Plans


Plans for each level of testing

Unit Test Plan


Integration Test Plan
System Test Plan
Acceptance Test Plan

Testing Type Specific Test Plans


Plans for major types of testing like Performance Test and Security Test.

TEST PLAN TEMPLATE


Items in a Test Plan Template

What do they contain

Scope

Test scenarios/Test objectives that will be


validated.

Out of scope

Enhanced clarity on what we are not


going to cover

Assumptions

All the conditions that need to hold true


for us to be able to proceed successfully

Schedules

Test scenario prep


Test documentation- test cases/test
data/setting up environment
Test execution
Test cycle- how many cycle
Start and end date for cycles

Roles and Responsibilities

Team members are listed


Who is to do what

TEST PLAN TEMPLATE


Items in a Test Plan Template

What do they contain

Deliverables

What documents are going to produce


at what time frames
What can be expected from each
document

Environment

What kind of environment requirements


exist
Who is going to be in charge
What to do in case of problems

Tools

For Example: Login

Defect Management

Who are we going to report the defects


to
How are we going to report

Risks and Risk Management

Risks are listed


Risks are analyzed- likelihood and
impact is documented

Exit criteria

When to stop testing

DELIVERABLES

Test Plan
Test Cases
Test Scripts
Defect/Enhancement Logs
Test Reports

IMPORTANT POINTS
Test Plan is a document that is the point of reference
based on which testing is carried out within the QA
team.
It is also a document we share with the Business
Analysts, Project Managers, Dev team and the other
teams.
This is to enhance the level of transparency into the QA
teams working to the external teams.
It is documented by the QA manager/QA lead based on
the inputs from the QA team members.

IMPORTANT POINTS
Test Planning is typically allocated 1/3rd of the time it
takes for the entire QA engagement.
The other 1/3rd is for Test Designing and rest is for
Test Execution.
Test plan is not static and is updated on an on demand
basis.
The more detailed and comprehensive the Test plan,
the more successful the testing activity.

IEEE 829 TEST PLAN STRUCTURE


Test plan identifier
Provide a unique identifier for the document.

Introduction
Provide an overview of the test plan.
Specify the goals/objectives.
Specify any constraints.

Test items
List the test items (software/products) and their versions.

Features to be tested
List the features of the software/product to be tested.
Provide references to the Requirements and/or Design specifications
of the features to be tested

IEEE 829 TEST PLAN STRUCTURE


Features not to be tested
List the features of the software/product which will not be tested.
Specify the reasons these features wont be tested.

Approach
Mention the overall approach to testing.
Specify the testing levels [if its a Master Test Plan], the testing
types, and the testing methods [Manual/Automated; White
Box/Black Box/Gray Box]

Item pass/fail criteria


Specify the criteria that will be used to determine whether each
test item (software/product) has passed or failed testing.

IEEE 829 TEST PLAN STRUCTURE


Suspension criteria and resumption requirements
Specify criteria to be used to suspend the testing activity.
Specify testing activities which must be redone when
testing is resumed.

Environmental needs
Specify the properties of test environment: hardware,
software, network etc.
List any testing or related tools.

Responsibilities
List the responsibilities of each team/role/individual.

TTH
A
N
K
Y
O
U
H AN K YO U

Você também pode gostar