3.Points to be confirmed before considering the overall test plan

This chapter explains how to collect information before starting the overall test plan.
If you don’t have the information you need, you will need to set a time to check again and update the overall test plan based on how these factors will affect the overall test plan itself or other deliverables created according to the overall test plan.

Information in the project

The table below indicates the information that is needed, examples of elements of this information and examples of topics (chapters in this document) where this information provides input for considerations. In many cases, this information can be found in deliverables such as the requirement definitions or project plan.
Unless otherwise specified, this information is for the project rather than testing specifically.
This information may be considered concurrently with or reviewed after overall test planning.

Information Examples of elements of information Topics on which the information can be used to make considerations
QCD targets and constraints – Quality requirements
– Cost constraints
– Delivery time
Test policies, Position of test phases
Risk – Risks that need to be addressed during testing Test policies, Coverage policies
Scope of development* and testing – Scope of development and testing at each stage when releasing in stages Test policies, Scope of testing
Stakeholders – External parties involved (vendors, etc.) and parties with whom to coordinate testing using external connection Test policies, Team structure, Tasks and allocation of roles
Schedule – Period allocated for the overall test phase Test policies, Schedule
Transition plan – Timing and number of transition rehearsals
– Timing of creation of transition data
– Tests using transition data
Position of test phases, Test environments
Various management policies – Quality control
– Bug management
– Configuration management
– Change management
– Management of loaned property from other organizations if applicable
Management policies
List of deliverables – Parent documents that can be used as input for the overall test plan
– Deliverables to be delivered to the client
– Security levels (scope of disclosure)
Position of overall test plan

*”Scope of development” here indicates the scope of programming and configuration of settings for the current project within the total volume to be released.

Information outside the project

The table below indicates the information that is needed and examples of topics (chapters in this document) where this information provides input for considerations.

Information Examples of topics
Test Type & Viewpoint Catalog Test policies, Position of test phases, Coverage policies