Project Test Plan
The
Project Test Plan is the
test work product that formally
documents the plans for performing all testing on a
project.
The typical objectives of the Project Test Plan are to
formally document the project's plans for:
- Test philosophy
- Test work products
- Test teams
- Test tasks and techniques
- Test tools
- Performing the following kinds of tests:
The typical benefits of a project test plan include:
- It enables the stakeholders to understand how the
application will be tested.
- It enables the management team to properly schedule and
staff the testing activity.
- It enables various test teams to understand what is
expected of them.
The Project Test Plan typically documents the following
information about each kind of test:
- Definition
- Objectives
- Completion criteria
- Responsibilities including teams and associated
roles
- Tasks and associated techniques
- Tools
- Timing by phase and milestone
- Producer:
- Evaluator:
- Approvers:
- Maintainer:
- Users:
- The
Project Managment Team uses the Project Test Plan to
guide the scheduling and staffing of the testing
activity.
- The
Architecture Team uses the Project Test Plan to
standardize their approach to the testing of architecture
models.
- The
Software Development Team uses the Project Test Plan
to standardize their approach to model testing and unit
testing.
- The
Integration Team uses the Project Test Plan to
standardize their approach to integration testing.
- The
Independent Test Team uses the Project Test Plan to
standardize their approach to system testing.
- The
User Experience Team uses the Project Test Plan to
document their approach to usability testing.
- The
Environments Team uses the Project Test Plan to
determine the number of test environments to develop and
maintain.
A project test plan typically can be started if the
following preconditions hold:
- Work Products:
- Stakeholders:
- This is a living document that is developed incrementally
and iteratively in parallel with other work products.
- Different parts of this document are due at different
times (i.e., during different phases).
- Some parts of this document are mandatory and some parts
are optional.
- Not every kind of testing needs to be performed on every
project.
A project test plan is typically constrained by the
following conventions:
-
Content and Format Standard
-
Template
-
Inspection Checklist
-
Example Project Test Plan