Project Management Framework
Planning - Test Plan
Definition
The Test Plan describes the approach to all development, unit, integration, system, qualification and acceptance testing needed to complete a project properly.
Why is this important?
Establishing a test plan based on business requirements and design specifications is essential for the successful acceptance of a project's deliverables. It is important to note that the higher risk a project has, the greater the need for a commensurate amount of testing. The project Schedule & Task Plan and the project Staffing Plan need to account for testing requirements during the planning and execution phases of the project.
Testing validates the requirements defined for the projects objectives and deliverables. Though IT project practices require testing throughout the execution phase of a project, undoubtedly the most important testing occurs at the end of development and prior to deployment. Orderly test plans that specify the criteria for test passage or failure are critical to a project's success.
Instructions
Prepare a Test Plan describing the scope, processes and criteria for testing particular deliverables of the project. The plan should describe the following elements:
- Provide an overview:
- Describe project objectives and background (providing some context for the testers).
- Give a short system description.
- Define the Test Plan objectives.
- Provide testing references as required.
- Note any outstanding issues, assumptions, known risks and contingencies.
- Define test scope, (features to be tested; Features not to be tested).
- Describe test methodologies.
- Describe testing approach.
- Describe test data (test cases, system and user interface test cases, user acceptance test plans, status reports of testing, and test outcome report at the end of testing detailing the overall results of testing progress).
- Provide all test documents.
- Validate test requirements.
- Define test control procedures, (for example, classification code and prioritization scheme for error tracking and resolution; tracking mechanisms for test results such as a test case validation log or test error log).
- Define and describe test phases. For each test phase such as unit, integration, system, etc., identify definition, participants, data sources, entrance and exit criteria, requirements and work products.
- Define the test environment, (description of hardware, software, location, staffing and training).
- Schedule testing tasks and make resource assignments.
- Define test approvals process and result distributions.
How to Scale
The size and nature of the project requirements should determine the scale of the test plan. The actual test methods and techniques must be adapted to the type of project being developed and the testing environment and tools that are available. Project managers need to think about the purpose of the testing, keeping in mind the process and stages for testing. Best practices dictate that testing be done early and often.
Related Links:
Test Plan Examples
Test Plan Template
Test Plan Execution
Checklists