Task Descriptor: Refine Test Plan |
This task focuses on planning the test for the iteration.
Based on Method Task: Plan Test Effort
Relationships
Inputs | Mandatory: Test Motivator | Optional: [Project Definition and Scope] [Project Risk] [Project Work] Test Plan | External: None
Outputs | Test Plan
Main Description
Special consideration should be given to: Capture the Changes in the Test Cycle Capture all of the changes agreed upon with the main development stakeholders in the iteration-related test plans. Ensure that the test plans correctly reflect the iteration test planning. For example, keep the list of test cases associated with a test plan up to date, as they implicitly define the scope covered by the plan. Make sure that all of the test cases are prioritized in the context of the test plan. Address the Level(s) and Type(s) of Testing Based on the agreed upon test process, create and maintain a number of test plans that should cover all of the testing levels and types addressed by the current iteration. For example, you can have a one-to-one mapping between a test level or a test type and a test plan within one iteration. Each test plan has to be assigned to a test team, so that in the more complex case a test team will be responsible for multiple test plans. If the initial scope covered by one specific test plan needs to be managed at a finer granularity level, create a new test plan. Review Refined Test Plans with the Test Team For each test team, identify the test plans that they are responsible for, and review their content. Pay special attention to the items that add more risks to the current test cycle, and keep track of them during testing. Focus on the scope of each test plan and agree on the priorities for the test cases included. Find a balance between the main constraints: testing resources, time, and scope, by using the priorities and the risks as the main drivers.
Steps
Align Test Approach with Test Mission and Objectives
Discuss the test mission with the development team. After gaining initial agreement on the test mission, goals, and specific objectives, define the test approach by outlining this information in the test plan.
Define Test Scope and Goals
Based on the agreed upon mission and test motivators, define the test scope for a particular test iteration. Test scoping on the iteration level should address both test type(s) and test level(s), and the technical boundaries. The goals must be measurable and clearly defined.
Define Testing Risks and Contingencies
Document testing risks and contingencies for risk mitigation in the test plan. If your risk planning is part of a larger risk management effort, coordinate testing risks with the risk analysis, design, and mitigation processes of the project manager. Ensure that test-related risk items are accurately traced to requirements and testing assets.
Outline Test Cases and Define Priorities and Dependencies
Define an outline of all test cases and test activities to be executed, in line with the goal and scope. Prioritize them based on the identified motivators, and the risks driving the current test effort.
Define Test Configurations
Using previously identified test configurations, define the test configurations needed for this iteration given the scope constraints and priorities. If no existent configuration matches your needs, start with a description of the software architecture, and focus on the deployment aspects for defining a new test environment.
Define Schedule and Entry and Exit Criteria
Develop a schedule for the test effort. Include specific entry and exit criteria for the development cycle. You may also find it useful to begin detailing work breakdown structures for the testing approach, and capture this in your test plan.
Create and Integrate Plans
Create iteration test plans as needed. Ensure that your test plan reflects the test planning approach captured on a detailed level in the iteration test plans. As the test planning progresses, capture your planning decisions in a test asset registry or repository that is capable of maintaining test asset dependencies among different test plans (master, iteration, level, and type).
Review Test Plan with Stakeholders
Review the test plan with all of the stakeholders, and get agreement on all of its elements. Focus on finding a balance between the testing resources and the scope of the current testing effort, based on the identified risks and priorities.
Properties
Multiple Occurrences |
Event Driven |
Ongoing |
Optional |
Planned |
Repeatable |
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.