Table of Contents

Test Run Termination Reason

Go up to Terms and Definitions

Discussion

A Test Run Termination Reason identifies why a Test Run entered the Terminated Test Run State.

A Test Run enters the Terminated Test Run State when it stops without satisfying its defined completion condition.

The standard Test Run Termination Reasons are:

Failed identifies termination caused by an error or failure that prevents continued Test Execution.

Interrupted identifies termination caused by an unplanned event external to the normal Test Execution progression.

Timed Out identifies termination caused by expiration of an applicable Timeout before the applicable completion condition was satisfied.

Canceled identifies termination caused by an authorized cancellation request or applicable Governance Policy.

A Test Run Termination Reason can identify:

A Test Run Termination Reason does not determine the Verdict assigned to a Test Result.

Definition

reason a Test Run entered the Terminated Test Run State

Source

Adapted from:

OMG TestIF provides Test Run, Test Result, and Verdict concepts but does not prescribe the DIDO-TE Test Run termination-reason classification defined on this page.

This definition introduces Test Run Termination Reason to distinguish why Test Execution stopped from the lifecycle state of the Test Run and from the evaluation of its Test Results.

Note

A Test Run Termination Reason applies when a Test Run enters the Terminated Test Run State.

A Test Run that enters the Completed Test Run State does not require a Test Run Termination Reason because it satisfied its defined completion condition.

A Test Run Termination Reason differs from a Test Run State:

A Test Run Termination Reason differs from a Verdict:

The termination reason Failed does not mean a Test Result received a failing Verdict.

A Test Run can:

The termination reason Interrupted applies to an unplanned event that stops Test Execution. Examples can include:

The termination reason Canceled applies when an authorized Actor or Governance Policy intentionally stops the Test Run.

The applicable Governance Policies or Acceptance Criteria should determine how to classify a termination when more than one reason appears applicable.

The Test Run record should preserve the immediate termination reason and can also preserve contributing events, errors, failures, and conditions.

Example

A Test Run performs a Test Sequence requiring a Node to return a response within 30 seconds.

The Node does not return the response before the applicable Timeout expires.

DIDO-TE:

The Test Run is also an Incomplete Test Run because it terminated without satisfying its defined completion condition.


© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.