====== Test Procedure ====== [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] ===== Discussion ===== A Test Procedure specifies the ordered activities that implement part or all of a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]] during a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]. The Test Procedure translates the intent and conditions of the Test Definition into executable activities. These activities include preparing the [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]], establishing preconditions, supplying [[dido:99_annexes:annex-b-terms-and-definitions:t:test_input|Test Inputs]], interacting with the [[dido:99_annexes:annex-b-terms-and-definitions:c:candidate_solution|Candidate Solution]], collecting [[dido:99_annexes:annex-b-terms-and-definitions:o:observation|Observations]], and restoring or terminating the Test Environment. A Test Procedure differs from a test script. A Test Procedure specifies the activities and their order independently of the mechanism used to perform them. A test script represents an executable implementation that automates some or all of those activities. ===== Definition ===== //ordered set of activities that implements part or all of a test definition during a test execution// ===== Source ===== Adapted from the test-process and test-documentation concepts described by: * [[https://www.iso.org/standard/79428.html|ISO/IEC/IEEE 29119-2:2021, Software and systems engineering — Software testing — Part 2: Test processes]] * [[https://www.iso.org/standard/79429.html|ISO/IEC/IEEE 29119-3:2021, Software and systems engineering — Software testing — Part 3: Test documentation]] * [[https://glossary.istqb.org/en_US/term/test-procedure|ISTQB Glossary, “test procedure”]] ===== Note ===== A Test Procedure identifies or references: * The applicable Test Definition * Preconditions * Required Test Resources * Required Test Environment * Test Inputs * Ordered test activities * Expected Results * Observation and Evidence collection activities * Completion conditions * Cleanup or restoration activities * Applicable exception-handling activities A Test Procedure supports manual execution, automated execution, or a combination of manual and automated execution. ===== Example ===== A Test Procedure directs DIDO-TE to: - Prepare the designated Test Environment - Confirm the Candidate Solution version - Supply a Transfer Bundle with a known integrity defect - Direct the Candidate Solution to import the Transfer Bundle - Record the response and associated log entries - Confirm whether deployment activities began - Preserve the resulting Observations and Evidence - Restore the Test Environment to its required state ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.