Test Plan

Go up to Terms and Definitions

A Test Plan organizes and governs a defined testing effort.

It identifies the testing scope, applicable tests, sequencing, resources, responsibilities, environments, constraints, expected outcomes, and other information needed to plan and coordinate testing.

A Test Plan is distinct from a Test Set.

A Test Set groups related tests or test cases for execution or organization.

A Test Plan has broader planning and governance semantics. It may identify one or more Test Sets, Test Cases, Test Environments, Resources, schedules, responsibilities, entry criteria, exit criteria, and other planning information.

The Test Information Interchange Format (TestIF) provides foundational testing concepts such as Test Set, Test Case, Test Step, Test Run, and related test information. Test Plan is not treated here as a direct TestIF model element. DIDO-TE defines Test Plan as a higher-level planning concept that remains compatible with the TestIF testing structure.

A governed specification that identifies and organizes the scope, objectives, tests, resources, environments, sequencing, responsibilities, constraints, and other information required to conduct a defined testing effort.

• [DTE4] DIDO Reference Data Model
• Object Management Group, Test Information Interchange Format (TestIF) 1.0, for related foundational testing concepts
• DIDO-TE architectural normalization

A Test Plan may identify or reference:

• testing objectives
• the Test Objects or other subjects to be tested
• applicable Tests
• Test Sets
• Test Cases
• applicable Requirements
• Test Environments
• required Resources
• sequencing or scheduling constraints
• responsibilities or participating roles
• entry criteria
• exit criteria
• Expected Results
• Validation criteria
• required Evidence
• reporting and Traceability requirements

A Test Plan does not itself represent a particular execution of the planned testing effort.

Actual execution is represented by applicable Test Runs and related execution information.

A Test Plan may govern multiple Test Runs and may be reused where the governed testing scope and conditions remain applicable.

A Test Plan for evaluating a candidate distributed Node implementation may identify:

• the protocol capabilities to be tested
• applicable conformance Requirements
• the Test Sets and Test Cases to be executed
• the required Test Environment
• participating Nodes and Resources
• required network conditions
• execution sequencing
• Expected Results
• Validation criteria
• Evidence to be retained
• criteria for determining completion of the testing effort

Individual Test Runs then execute applicable portions of the Test Plan.