| |
| dido:99_annexes:annex-b-terms-and-definitions:e:executable_instruction [2026/08/04 13:15] – created nick_dido | dido:99_annexes:annex-b-terms-and-definitions:e:executable_instruction [2026/08/04 13:18] (current) – nick_dido |
|---|
| ===== Discussion ===== | ===== Discussion ===== |
| |
| An Executable Instruction specifies an operation that an [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facility]] can interpret or perform. | An Executable Instruction specifies an operation in a form that an [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facility]] can interpret or perform. |
| |
| An Executable Instruction can implement an action, calculation, validation, communication, state transition, measurement, observation, or control. | An Executable Instruction can implement: |
| |
| Executable Instructions can take the form of: | * An action |
| | * A calculation |
| | * A [[dido:99_annexes:annex-b-terms-and-definitions:v:validation|Validation]] |
| | * A communication |
| | * A state transition |
| | * A measurement |
| | * An observation |
| | * A decision |
| | * A control |
| | |
| | An Executable Instruction can occur within: |
| |
| * Source code | * Source code |
| * Compiled code | * Compiled code |
| * Scripts | * A script |
| * Commands | * A command |
| * Declarative automation | * Declarative automation |
| * Tool-specific procedures | * A tool-specific procedure |
| * Test-framework instructions | * A test-framework procedure |
| * Executable models | * An executable model |
| * Service requests | * A service request |
| * Hardware-control instructions | * A hardware-control procedure |
| | * Another form that an Execution Facility can interpret or perform |
| |
| An Executable Instruction can identify: | An Executable Instruction can identify or reference: |
| |
| * Its identity | * Its identity |
| * Its instruction type | * Its instruction type |
| * Its language or format | * Its language or format |
| * Its entry point | * Its operation |
| * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument|Test Arguments]] | * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument|Test Arguments]] |
| * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument_value|Test Argument Values]] | * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument_value|Test Argument Values]] |
| * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_item|Test Items]] | * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_item|Test Items]] |
| * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environments]] | * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environments]] |
| | * Its preconditions |
| * Its completion condition | * Its completion condition |
| * Its failure condition | * Its failure condition |
| * Its [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] | * Its [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] |
| |
| A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]] contains or references one or more Executable Instructions that implement a test action or validation. | A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]] contains or references one or more Executable Instructions that implement a test action or [[dido:99_annexes:annex-b-terms-and-definitions:v:validation|Validation]]. |
| |
| The Test Executable can contain the Executable Instructions directly or reference an independently maintained [[dido:99_annexes:annex-b-terms-and-definitions:e:executable_artifact|Executable Artifact]] that contains them. | A Test Executable can contain the Executable Instructions directly or reference an independently maintained [[dido:99_annexes:annex-b-terms-and-definitions:e:executable_artifact|Executable Artifact]] that contains them. |
| |
| An [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facility]] interprets or performs the Executable Instructions during [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]. | An [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facility]] interprets or performs the Executable Instructions during [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]. |
| ===== Definition ===== | ===== Definition ===== |
| |
| //instruction that an [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facility]] can interpret or perform to implement an action, calculation, validation, or control// | //instruction expressed in a form that an [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facility]] can interpret or perform// |
| |
| ===== Source ===== | ===== Source ===== |
| * DIDO-TE draft Requirements Register | * DIDO-TE draft Requirements Register |
| |
| OMG TestIF describes a TestExecutable as a low-level procedural definition that can contain code or scripts for test automation. | OMG TestIF describes a TestExecutable as a low-level procedural definition that supports automated testing through code, scripts, or other executable information. |
| |
| OMG TestIF does not define Executable Instruction as a separate TestIF model element. This definition introduces the term to distinguish the individual instructions from the Test Executable that contains or references them and from the artifact in which they can reside. | OMG TestIF does not define Executable Instruction as a separate TestIF model element. This definition introduces Executable Instruction to distinguish an instruction from: |
| | |
| | * The [[dido:99_annexes:annex-b-terms-and-definitions:t:test_step|Test Step]] that specifies the required test action or Validation |
| | * The [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]] that contains or references the instruction |
| | * The [[dido:99_annexes:annex-b-terms-and-definitions:e:executable_artifact|Executable Artifact]] that stores or packages the instruction |
| | * The [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facility]] that interprets or performs the instruction |
| |
| ===== Note ===== | ===== Note ===== |
| | |
| | Every Executable Instruction expresses an operation in a form that an identified Execution Facility can interpret or perform. |
| |
| An Executable Instruction differs from a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_step|Test Step]]: | An Executable Instruction differs from a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_step|Test Step]]: |
| |
| * A Test Step specifies an action or validation independently of a particular execution mechanism | * A Test Step specifies a test action or Validation independently of a particular execution mechanism |
| * An Executable Instruction provides part or all of the machine-interpretable or tool-interpretable realization of that action or validation | * An Executable Instruction provides part or all of the executable realization of that action or Validation |
| |
| An Executable Instruction differs from a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]]: | An Executable Instruction differs from a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]]: |
| |
| * An Executable Instruction specifies an individual executable operation | * An Executable Instruction specifies an operation |
| * A Test Executable organizes, contains, or references one or more Executable Instructions | * A Test Executable contains, organizes, or references one or more Executable Instructions |
| |
| An Executable Instruction differs from an [[dido:99_annexes:annex-b-terms-and-definitions:e:executable_artifact|Executable Artifact]]: | An Executable Instruction differs from an [[dido:99_annexes:annex-b-terms-and-definitions:e:executable_artifact|Executable Artifact]]: |
| |
| * An Executable Instruction specifies an operation | * An Executable Instruction specifies an operation |
| * An Executable Artifact stores, packages, or otherwise provides one or more Executable Instructions | * An Executable Artifact stores, packages, or provides one or more Executable Instructions |
| | |
| | An Executable Instruction differs from an [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facility]]: |
| | |
| | * An Executable Instruction specifies the operation |
| | * An Execution Facility interprets or performs the operation |
| |
| A Test Executable can reference an Executable Artifact without copying the Executable Instructions into the Test Executable. | An Executable Instruction does not require direct execution by a processor. An Execution Facility can include: |
| |
| An Executable Instruction does not require direct execution by a processor. An interpreter, command processor, automation engine, test framework, model-execution engine, service, device controller, or other Execution Facility can interpret or perform the instruction. | * An interpreter |
| | * A command processor |
| | * An automation engine |
| | * A test framework |
| | * A model-execution engine |
| | * A service |
| | * A device controller |
| | * Another facility capable of interpreting or performing the instruction |
| |
| A natural-language direction intended only for human interpretation is not necessarily an Executable Instruction. The direction qualifies as an Executable Instruction when an identified Execution Facility can interpret or perform it according to defined execution rules. | A natural-language direction intended only for human interpretation is not an Executable Instruction under this definition. A direction qualifies as an Executable Instruction when an identified Execution Facility can interpret or perform it according to defined execution rules. |
| |
| An Executable Instruction is not necessarily: | An Executable Instruction is not necessarily: |
| * Independently reusable | * Independently reusable |
| * Specific to testing | * Specific to testing |
| * Contained within the Test Executable | * Contained within a Test Executable |
| * Stored in a particular file | * Stored in a particular file |
| * Associated with a particular programming language | * Associated with a particular programming language |
| |
| A change to the operation, parameters, control flow, dependencies, expected behavior, or execution requirements can create a new [[dido:99_annexes:annex-b-terms-and-definitions:v:version|Version]] of an Executable Instruction under the applicable versioning policy. | A change to an Executable Instruction’s operation, inputs, outputs, parameters, control flow, dependencies, expected behavior, or execution requirements can create a new [[dido:99_annexes:annex-b-terms-and-definitions:v:version|Version]] under the applicable versioning policy. |
| |
| A reproducible [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]] should identify the exact Versions of the Executable Instructions or referenced Executable Artifacts used during Test Execution. | A reproducible [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]] should identify the exact Versions of the Executable Instructions and referenced Executable Artifacts used during [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]. |
| |
| ===== Example ===== | ===== Example ===== |
| |
| A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_step|Test Step]] requires a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] to submit a proposed transaction to a specified [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]]. | A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_step|Test Step]] requires a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] to submit a proposed transaction through a specified [[dido:99_annexes:annex-b-terms-and-definitions:e:endpoint|Endpoint]]. |
| |
| A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]] references a versioned script containing Executable Instructions that: | A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]] references a versioned script containing Executable Instructions that: |
| |
| * Read the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument_value|Test Argument Values]] | * Read the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument_value|Test Argument Values]] |
| * Establish a connection to the Communication Endpoint | * Establish a connection to the Endpoint |
| * Submit the proposed transaction | * Submit the proposed transaction |
| * Capture the response | * Capture the response |
| * Preserve the resulting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | * Preserve the resulting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] |
| |
| During [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]], the applicable Execution Facility interprets or performs the Executable Instructions. | During Test Execution, the applicable [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facility]] interprets or performs the Executable Instructions. |
| |
| The [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]] records: | The [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]] records: |