Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:t:test_execution [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:t:test_execution [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Test Execution ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | Test Execution is the performance of one or more [[public: | ||
| + | |||
| + | Test Execution can perform: | ||
| + | |||
| + | * A [[public: | ||
| + | * A [[public: | ||
| + | * A [[public: | ||
| + | * A [[public: | ||
| + | |||
| + | Test Execution can include: | ||
| + | |||
| + | * Selecting the applicable Sequenced Test Objects | ||
| + | * Establishing the applicable Test Environment | ||
| + | * Confirming applicable preconditions | ||
| + | * Selecting the applicable [[public: | ||
| + | * Selecting the applicable [[public: | ||
| + | * Selecting the applicable [[public: | ||
| + | * Resolving the applicable [[public: | ||
| + | * Supplying the applicable [[public: | ||
| + | * Selecting the applicable [[public: | ||
| + | * Retrieving the applicable [[public: | ||
| + | * Interpreting or performing the applicable [[public: | ||
| + | * Observing the behavior of the Test Items | ||
| + | * Measuring applicable conditions and outcomes | ||
| + | * Comparing observed outcomes with [[public: | ||
| + | * Assigning applicable [[public: | ||
| + | * Producing Test Results | ||
| + | * Collecting [[public: | ||
| + | * Preserving [[public: | ||
| + | * Maintaining [[public: | ||
| + | |||
| + | A [[public: | ||
| + | |||
| + | A [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Adapted from: | ||
| + | |||
| + | * [[https:// | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * DIDO Reference Implementation Conceptual Model | ||
| + | * DIDO-TE draft Requirements Register | ||
| + | |||
| + | OMG TestIF models the information used to define tests and the TestRuns and TestResults produced when those tests execute. | ||
| + | |||
| + | OMG TestIF does not define Test Execution as a separate TestIF model element. This definition introduces Test Execution as the activity that occurs between the applicable test definitions and the resulting Test Run and Test Results. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | Test Execution differs from a [[public: | ||
| + | |||
| + | * Test Execution is the activity of performing the applicable Sequenced Test Objects | ||
| + | * A Test Run identifies and records a particular occurrence of that activity | ||
| + | |||
| + | Test Execution differs from a [[public: | ||
| + | |||
| + | * Test Execution performs the applicable test activities | ||
| + | * A Test Result records an outcome produced by those activities | ||
| + | |||
| + | Test Execution differs from a [[public: | ||
| + | |||
| + | * A Test Sequence specifies the order and progression of Sequenced Test Objects | ||
| + | * Test Execution performs those objects according to the applicable Test Sequence | ||
| + | |||
| + | Test Execution differs from a [[public: | ||
| + | |||
| + | * A Test Environment identifies the conditions, resources, configurations, | ||
| + | * Test Execution is the activity conducted within those conditions and using those resources | ||
| + | |||
| + | Test Execution differs from a [[public: | ||
| + | |||
| + | * A Test Executable contains or references [[public: | ||
| + | * Test Execution causes the applicable Execution Facilities to interpret or perform those instructions | ||
| + | |||
| + | Test Execution can use automated, manual, or combined procedures. | ||
| + | |||
| + | Manual Test Execution can produce valid Test Results when the applicable test definition identifies: | ||
| + | |||
| + | * The required actions | ||
| + | * The responsible participant | ||
| + | * The required observations | ||
| + | * The applicable Expected Results | ||
| + | * The applicable Verdict criteria | ||
| + | * The required Evidence | ||
| + | |||
| + | Test Execution can perform Sequenced Test Objects: | ||
| + | |||
| + | * Sequentially | ||
| + | * Concurrently | ||
| + | * Conditionally | ||
| + | * Iteratively | ||
| + | * In response to an event | ||
| + | * According to another progression established by the applicable Test Sequence | ||
| + | |||
| + | Starting Test Execution does not establish successful completion. Test Execution can: | ||
| + | |||
| + | * Complete successfully | ||
| + | * Complete with one or more failed Test Results | ||
| + | * Terminate because of an error | ||
| + | * Terminate because of a timeout | ||
| + | * Stop because a precondition is not satisfied | ||
| + | * Stop because a required resource is unavailable | ||
| + | * Be interrupted | ||
| + | * Be canceled | ||
| + | * Remain incomplete | ||
| + | |||
| + | The applicable [[public: | ||
| + | |||
| + | Repeated Test Execution does not necessarily reproduce the same Test Results. Reproducibility depends on preserving or controlling the applicable: | ||
| + | |||
| + | * Sequenced Test Object Versions | ||
| + | * Test Item Versions and states | ||
| + | * Test Environment | ||
| + | * Test Argument Values | ||
| + | * Executable Artifact Versions and content digests | ||
| + | * Execution Facility Versions and configurations | ||
| + | * Dependencies | ||
| + | * Starting conditions | ||
| + | * Timing conditions | ||
| + | * External interactions | ||
| + | * Governance Policies | ||
| + | |||
| + | A reproducible Test Run should preserve sufficient Evidence, Provenance, and Traceability to identify these conditions. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A [[public: | ||
| + | |||
| + | Test Execution: | ||
| + | |||
| + | * Establishes the applicable [[public: | ||
| + | * Confirms the required Nodes and Execution Facilities are available | ||
| + | * Loads the applicable [[public: | ||
| + | * Supplies the applicable [[public: | ||
| + | * Performs the applicable [[private: | ||
| + | * Submits the proposed transaction through the applicable [[public: | ||
| + | * Observes the resulting state of each applicable [[public: | ||
| + | * Compares the observed states with the applicable [[public: | ||
| + | * Produces the applicable [[public: | ||
| + | * Preserves the supporting [[public: | ||
| + | |||
| + | The [[public: | ||
| + | |||
| + | * The Test Case | ||
| + | * The performed Test Steps | ||
| + | * The applicable Test Items | ||
| + | * The applicable Node Set | ||
| + | * The Test Environment | ||
| + | * The Test Argument Values | ||
| + | * The Executable Artifacts | ||
| + | * The Execution Facilities | ||
| + | * The Test Results | ||
| + | * The Evidence | ||
| + | * The resulting [[public: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||