As we all are
aware documentation is one of the most important and integral parts of any QA
process. There are a lot of QA specific documents that are being created and maintained
during project execution.
In this blog we
are going to see some of the common documents that are being created during the course of the project.
Test
Policy
This is the high
level document that defines the overall objectives for testing that organization
want to achieve and describes the organization basic philosophy towards the
testing it also describe the overall business value and all short and long
terms goals towards quality management.
It also defines the organization
overall objective towards testing how to implement and measure those processes
and how these processes can be improved over a period of time.
There could be
multiple Test policy for an organization based on nature of work as New
Development and maintenance.
Test Strategy
This defines the way
in which testing is used to manage different types of projects and product risks. It
also defines how to divide the testing cycle into different testing levels and all
the high-level activities associated with it.
Test Strategy
should be consistent and in line with the Test policy as it defines the organization
general test process.
Typical test strategy contains:
Ø Introduction
Ø Testing Scope
Ø Testing environment
Ø Testing Tools (Manual and automation)
Ø Resources
Ø Testing approach and Technique
Ø Release/configuration Process
Ø Risk assessment, analysis, and mitigation
Ø Test Control and reporting
Ø Testing metrics
Ø Roles and Responsibilities
Ø Defect Management.
Master
Test Plan
It describes the
way to implement the test strategy for the project. This document should be
inline with Test policy and strategy and should also intimate about any
deviation and exception in specific areas.
This describes all
the testing related activities need to be done on a specific project and also
all the testing level (Component, Integration, System, UAT, etc) that will be
carried out.
Typical Master Test Plan contains:
Ø Testing Schedule and budget
Ø Testing Cycles
Ø Items In Scope/Out Scope
Ø Entry and exit criteria for each testing level
Ø Testing project risk
Ø Roles and responsibilities for each test level
Ø Test Reporting
Level
Test Plan
Level test plans
describe the particular activities to be carried out within each test level or,
in some cases, test type. Level test plans expand, where necessary, on the
master test plan for the specific level or test type being documented. They
provide schedule, task, and milestone details not necessarily covered in the
master test plan.
