When and Why Test Planning Is Performed

The testing scope and activities are outlined in a test plan document, as well as in separate document for test levels, such as system or acceptance testing.

The structure of the test plan is to be tailored by the organization’s needs. A testing process is influenced by many aspects such as test policy, testing scope, testing tools, risks, restrictions, criticality, testability and availability of resources. As the project and test planning progress through each phase, it is possible to add more information and more details to the plan. Test planning is a continuous process that is carried out throughout the life cycle. Test results are reviewed to assess the probability and severity of software risks, so that to make adjustments to the test plan.

Test planning activities may include

• defining testing scope, project’s risks and testing objectives;
• choosing a relevant testing approach, including different test levels and entry criteria;
• integrating and coordinating testing activities with the software life cycle (acquisition, supply, development, operation and maintenance);
• deciding what to test, who should test, when and how to run a test, and how to evaluate the results;
• scheduling test case design & execution;
• assigning resources to the tasks defined earlier;
• determining the size, level of detail, structure and templates for the test documentation;
• selecting test monitoring and control metrics during test planning and test execution, defect correction methods, problem and risk management techniques;
• setting the right level of detail of test data to provide sufficient information for repeating test planning and test execution procedures.

Thee worthy goal is to evaluate performance parameters of a given software product. By using the services of load testing companies one can measure the response of one or another digital program under real-world workload conditions.

Entry criterion

Entry criterion determines the start of testing, for example, at what level of software should testing start or when a test suite is ready to be run.

Usually entry criteria can access:

• readiness and availability of the test environment;
• availability of the test environment management tools;
• availability of the code under test;
• availability of test data.

Exit criterion

The exit criterion determines the end of testing, for example, at completion of the test level or when the test suite has reached a specific goal.

Usually exit criteria can:

• cover program code, functionality or risks;
• estimate defect density or reliability measures;
• assess cost;
• evaluate residual risks, such as uncorrected defects or insufficient test coverage of any area;
• analyze plan based on the release time of the software.