In order to meet the overall system quality targets of a project, a test plan needs to be considered from an overall perspective that acrossencompasses each test phase.
For the purposes of this document, this is called an “overall test plan”.
The overall test plan is used to consider test plans for each phase or test type (e.g. performance testing), ensuring that consistency is maintained throughout the project and the test plans are sufficientenough to achieve the quality objectives.
The following issues may occur during a project.
In order to prevent such issues and perform effective and efficient testing within the limits of the project’s resources (personnel, items, money), an overall plan for testing that covers each test phase needs to be created to define the quality that needs to be confirmed in each test phase and improve that quality determine specific methods to verify that quality. For example, Performance testing needs to be carried out in stages, with integration testing in phase units and system testing in system units.
Overall test planning needs to begin at the time the requirements are defined, as the points considered during overall test planning affect the cost, schedule and quality of the project and whether the requirements can be achieved.
However, there may be cases where some information is not confirmed at the time the requirements are defined, or cases where the prerequisites change. We therefore recommend reviewing the overall test plan and expanding on the details later, such as at the time of each development phase.
Refer to the following sections for details on specific points to be considered in overall test planning.
|4.1||Test policies||Considering the basic principles, policies and premises for the creation of an overall test plan.|
|4.2||Position of test phases||Selecting the test types required for a project and considering on the phases in which the selected types of tests will be executed.|
|4.3||Coverage policies||Considering the balance between quality and cost and considering on the test targets (requirements, program structure, etc.) through comprehensive deliberation.|
|4.4||Scope of testing||Considering which features will and will not be tested and the system boundaries that will indicate the scope of testing.|
|4.5||Test environments||Considering on the environment for testing.|
|4.6||Team structure||Considering on systems for carrying out testing and role.|
|4.7||Tasks and allocation of roles||Considering on tasks for the testing phase as a whole.|
|4.8||Schedule||Considering on the schedule of the testing phase as a whole.|
|4.9||Management policies||Considering on policies for project management such as bug management and quality control throughout the testing phase as a whole.|
|5||Position of overall test plan||Considering on the position of the overall test plan in the project as a whole and the scope of disclosure.|
Copyright 2021 TIS Inc.keyboard_arrow_up