During test planning various activities for an entire system or a part of a system have to be undertaken by those working on the plan. These activities are:
1) Working with the project manager and subject matter experts' to determine the scope and the risks that need to be tested. As well identifying and agreeing the objectives of the testing, be they time, quality or cost focussed, or in fact maybe a mixture of all three. The objectives will enable the test project to know when it has finished.
2) Putting together the overall approach of testing (sometimes called the test strategy), ensuring that the test levels and entry and exit criteria are defined.
3) Liaison with the project manager and making sure that the testing activities have been included within the software life-cycle activities such as:
a) Design - The development of the software design;
b) Development – The building of the code;
c) Implementation - The activities surrounding implementation into a live environment.
4) Working with the project to decide what needs to be tested, what roles are involved and who will perform the test activities, planning when and how the test activities should be done, deciding how the test results will be evaluated, and defining when to stop testing (exit criteria).
5) Building a plan that identifies when and who will undertake the test analysis and design activities. In addition to the analysis and design activities test planning should also document the schedule for test implementation, execution and evaluation.
6) Finding and assigning resources for the different activities that have been defined.
7) Deciding what the documentation for the test project will be, e.g. which plans, how the test cases will be documented, etc.
8) Defining the management information, including the metrics required and putting in place the processes to monitor and control test preparation and execution, defect resolution and risk issues.
9) Ensuring that the test documentation generates repeatable test assets, e.g. test cases.