public:99_annexes:annex-b-terms-and-definitions:t:test_plan

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:t:test_plan [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:t:test_plan [2026/09/13 17:06] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Test Plan ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +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 [[public:99_annexes:annex-b-terms-and-definitions:t:test_set|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.
 +
 +===== Definition =====
 +
 +//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.//
 +
 +===== Source =====
 +
 +  * [[private:07-dido-te:99-annexes:annex-b-references:dte-004|[DTE4] DIDO Reference Data Model]]
 +  * Object Management Group, Test Information Interchange Format (TestIF) 1.0, for related foundational testing concepts
 +  * DIDO-TE architectural normalization
 +
 +===== Note =====
 +
 +A Test Plan may identify or reference:
 +
 +  * testing objectives
 +  * the [[public:99_annexes:annex-b-terms-and-definitions:t:test_object|Test Objects]] or other subjects to be tested
 +  * applicable [[public:99_annexes:annex-b-terms-and-definitions:t:test|Tests]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:t:test_set|Test Sets]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:t:test_case|Test Cases]]
 +  * applicable [[public:99_annexes:annex-b-terms-and-definitions:r:requirement|Requirements]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environments]]
 +  * required [[public:99_annexes:annex-b-terms-and-definitions:r:resource|Resources]]
 +  * sequencing or scheduling constraints
 +  * responsibilities or participating roles
 +  * entry criteria
 +  * exit criteria
 +  * [[public:99_annexes:annex-b-terms-and-definitions:e:expected_result|Expected Results]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:v:validation|Validation]] criteria
 +  * required [[public:99_annexes:annex-b-terms-and-definitions:e:evidence|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 [[public:99_annexes:annex-b-terms-and-definitions:t:test_run|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.
 +
 +===== Example =====
 +
 +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.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>