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:i:incomplete_test_run [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:i:incomplete_test_run [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Incomplete Test Run ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An Incomplete Test Run is a [[public: | ||
| + | |||
| + | An Incomplete Test Run has: | ||
| + | |||
| + | * A Terminated [[public: | ||
| + | * A [[public: | ||
| + | * An unsatisfied completion condition | ||
| + | |||
| + | An Incomplete Test Run can have the following Test Run Termination Reason: | ||
| + | |||
| + | * Failed | ||
| + | * Interrupted | ||
| + | * Timed Out | ||
| + | * Canceled | ||
| + | |||
| + | An Incomplete Test Run can preserve valid information produced before termination, | ||
| + | |||
| + | * Completed [[public: | ||
| + | * Completed [[public: | ||
| + | * Performed [[public: | ||
| + | * Applied [[public: | ||
| + | * Observations | ||
| + | * Measurements | ||
| + | * Events | ||
| + | * Outputs | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | |||
| + | The applicable [[public: | ||
| + | |||
| + | * Analysis | ||
| + | * Diagnosis | ||
| + | * Comparison | ||
| + | * Regression analysis | ||
| + | * Baseline establishment | ||
| + | * [[public: | ||
| + | * A [[public: | ||
| + | * Another defined purpose | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Adapted from: | ||
| + | |||
| + | * [[https:// | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * DIDO Reference Implementation Conceptual Model | ||
| + | * DIDO-TE draft Requirements Register | ||
| + | |||
| + | OMG TestIF provides Test Run, Test Result, and Verdict concepts but does not define Incomplete Test Run as a separate TestIF model element. | ||
| + | |||
| + | This definition introduces Incomplete Test Run to distinguish a Test Run that failed to satisfy its completion condition from a completed Test Run producing a Test Result assigned a failing Verdict. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | An Incomplete Test Run is a Test Run in the Terminated Test Run State. | ||
| + | |||
| + | A Test Run that is Not Started, Ready, Running, or Paused has not yet completed, but it is not classified as an Incomplete Test Run because its [[public: | ||
| + | |||
| + | A Test Run becomes an Incomplete Test Run when: | ||
| + | |||
| + | * Test Execution stops | ||
| + | * The Test Run enters the Terminated Test Run State | ||
| + | * The defined completion condition remains unsatisfied | ||
| + | |||
| + | An Incomplete Test Run differs from a completed Test Run assigned a failing Verdict: | ||
| + | |||
| + | * An Incomplete Test Run did not satisfy its completion condition | ||
| + | * A completed Test Run assigned a failing Verdict satisfied its completion condition and produced a Test Result that did not satisfy the applicable [[public: | ||
| + | |||
| + | An Incomplete Test Run does not imply that every Test Result produced before termination is invalid. | ||
| + | |||
| + | The applicable Acceptance Criteria determine: | ||
| + | |||
| + | * Which partial Test Results remain valid | ||
| + | * Which Evidence remains usable | ||
| + | * Whether the Test Run can resume | ||
| + | * Whether DIDO-TE must create a new Test Run | ||
| + | * Whether the Test Run can participate in a comparison | ||
| + | * Whether the Test Run can contribute to a [[public: | ||
| + | * Whether the Test Run can support a Validation Decision | ||
| + | * Whether the Test Run must be repeated | ||
| + | |||
| + | A paused Test Run is not an Incomplete Test Run because it remains eligible to resume. | ||
| + | |||
| + | A canceled Test Run is an Incomplete Test Run when cancellation causes it to enter the Terminated state before satisfying its completion condition. | ||
| + | |||
| + | A timed-out Test Run is an Incomplete Test Run when expiration of an applicable [[public: | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A Test Run contains ten [[public: | ||
| + | |||
| + | The Test Run successfully completes the first six Sequence Steps. During the seventh Sequence Step, an [[public: | ||
| + | |||
| + | DIDO-TE: | ||
| + | |||
| + | * Stops Test Execution | ||
| + | * Changes the Test Run State from **Running** to **Terminated** | ||
| + | * Assigns **Interrupted** as the Test Run Termination Reason | ||
| + | * Classifies the Test Run as an Incomplete Test Run | ||
| + | * Preserves the Test Results produced by the first six Sequence Steps | ||
| + | * Records the affected Sequence Step | ||
| + | * Records the unavailable Execution Facility | ||
| + | * Preserves the supporting Evidence | ||
| + | * Maintains Provenance and Traceability | ||
| + | |||
| + | The applicable Acceptance Criteria determine whether the preserved Test Results can be used and whether DIDO-TE must repeat the entire Test Run or resume from an approved Sequence Step. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||