Aim 
Formulating a cohesive and broadly supported approach with which the test assignment can be successfully executed. An important part of the planning phase is the creation of the test plan, for the purpose of informing the client and other stakeholders concerning the approach, schedule, budget, activities and the (end) products to be delivered in relation to the test process. If an overall master test plan exists, the test plan should be derived from it. 

Method of operation
The test manager, as a rule, is the originator of the test plan. Ideally, a master test plan will be available. On this basis and in consultation with the client, he will formulate the assignment, making an allowance for the four BDTM [Business Driven Test Management] aspects of Result, Risks, Time and Costs. Subsequently, the test manager will prepare himself for the forthcoming phase by holding various discussions with stakeholders and consulting other sources of information, such as documentation. At the same time, he defines the assignment further in close co-operation with the client, and determines the scope of the test level. 

In the event that, for the master test plan, a product risk analysis has not been executed, or if it is too general, a detailed analysis is carried out with the client and other stakeholders. This is done in order to establish the required results of the testing for the client (the test goals) and evaluate the risk level of the parts (object parts) and characteristics of the system or package to be tested. This analysis forms the basis of the test strategy and the process advances to an iterative stage. As part of the strategy based on the product risk analysis the tester determines the characteristics/object parts that should be tested, and with which test type and to which depth (the greater the risk, the greater the depth). Then the test costs are estimated in outline form and the test activities are planned (covering the biggest risks as early as possible). This is to be agreed on by the client and other stakeholders and, depending on their views, possibly revised. In that case, the steps are then gone through again. In accordance with BDTM, the client therefore has a clear understanding of the test process and can manage the balance of Time and Money versus Result and Risk. Subsequent to this, the test manager refines the strategy further by determining test units and translating the decisions about depth of testing into firm statements on which coverage is being aimed for. He then allocates test techniques  to the characteristic/object part combinations, making allowance for the available test basis, resources and infrastructural provisions. Using these techniques, the test cases (and, for example, the checklists) are designed and executed at a later stage. 

Further steps in the plan formulation are that the test manager establishes the test basis, defines the test products and builds up the test organisation. The test manager also defines the required infrastructure. Test management is furnished with procedures and standards, supported as far as possible with tools. As a rule the elements available in the master test plan, Generic Test Agreements, the test policy or the Testing line organisation are used.

The most important risks that threaten the test process are cited, and possible measures are proposed for managing these risks. As a last step, the test manager has the test plan approved by the client. While the activities in this subprocess are described in sequence, in practice, certain activities will be done several times and/or in a different order. If, for example, certain infrastructure parts are required for a test and cannot be supplied, then the strategy may have to be adjusted.

Activities  
The creation of the test plan involves the following activities:

1. Establishing the assignment
2. Understanding the assignment 
3. Determining the test basis
4. Analysing the product risks
5. Determining the test strategy
6. Estimating the effort
7. Determining the planning
8. Allocating test units and test techniques
9. Defining the test products
10. Defining the organisation
11. Defining the infrastructure
12. Organising the management
13. Determining the test project risks and countermeasures
14. Feedback and consolidation of the plan    

For more information on the activities in the Planning phase please check the TMap Next book.

Products 
The test plan:

• Formulation of the assignment
• Test strategy 
• Approach (test units, with the test types and techniques to be used per test unit)
• Organisation
• Infrastructure
• Management
• Threats, (project) risks and measures
• Budget and planning
• Appendix: Product risk analysis     

Techniques

• Checklist of preconditions and assumptions.
• ‘Understanding the assignment’ checklist.
• Product risk analysis (Chapter 9).
• Explanation of quality characteristics (Chapter 10).
• Strategy determination (as described in this section).
• Various estimation techniques (Chapter 11).
• Step-by-step plan for creating an estimate (Chapter 11).
• “Test environments” checklist.
• “Office setup” checklist.
• “Test process risks” checklist.     

Tools

• Testware management tool
• Defect management tool
• Planning and progress monitoring tool 
• Workflow tool