Test Run

Go up to Terms and Definitions

A Test Run is a Test Object that identifies and records a particular occurrence of Test Execution, its execution context, and its Test Results.

A Test Run can identify:

• Its identity
• Its name
• Its description
• Its status
• Its start time
• Its completion time
• Its initiating actor
• Its applicable Test Sequence
• Its starting Sequenced Test Object
• Its performed Sequence Steps
• Its applicable Test Items
• Its applicable Node Sets
• Its applicable Test Environment
• Its applicable Test Argument Values
• Its applicable Executable Artifacts
• Its applicable Execution Facilities
• Its Test Results
• Its supporting Evidence
• Its applicable Governance Policies
• Its Provenance
• Its Traceability

A Test Run can record a completed, failed, interrupted, canceled, timed-out, or incomplete occurrence of Test Execution.

Test Object that identifies and records a particular occurrence of Test Execution, its execution context, and its Test Results

Adapted from:

• OMG Test Information Interchange Format (TestIF), Version 1.0 Beta 3, Section 7.3.12, TestRun
• Test Object
• Test Execution
• Test Result
• DIDO Reference Implementation Conceptual Model
• DIDO-TE draft Requirements Register

OMG TestIF defines TestRun as a TestObject that contains contextual information about an executed test and the results of that run.

This definition preserves the TestIF role and explicitly distinguishes the recorded Test Run from the Test Execution activity it records.

Every Test Run is a Test Object.

A Test Run differs from Test Execution:

• Test Execution is the activity of performing the applicable Sequenced Test Objects
• A Test Run identifies and records a particular occurrence of that activity

A Test Run differs from a Test Result:

• A Test Run records the execution context and collects the applicable Test Results
• A Test Result records an outcome associated with a performed Sequenced Test Object or Sequence Step

A Test Run differs from a Test Sequence:

• A Test Sequence defines the planned progression
• A Test Run records the actual occurrence and progression

A Test Run can exist without successful completion. The absence of a completion time or complete set of Test Results can indicate an incomplete Test Run.

A repeated execution creates a separate Test Run, even when it uses the same:

• Test Sequence
• Sequenced Test Objects
• Test Items
• Test Environment
• Test Argument Values
• Executable Artifacts
• Execution Facilities

A Test Run does not automatically constitute a Baseline. An applicable authority must select and govern the Test Run or its Test Results as a Baseline.

A reproducible Test Run should identify the exact Versions, configurations, content digests, inputs, dependencies, and operating conditions used during Test Execution.

Test Run TR-2026-0042 records an occurrence of Test Execution that evaluates a selected Node Set.

The Test Run identifies:

• Test Sequence Version 1.4
• The selected Test Items
• The applicable Test Environment
• The applicable Test Argument Values
• The performed Sequence Steps
• The Executable Artifact Versions and content digests
• The Execution Facility Versions and configurations
• The start time and completion time
• The resulting Test Results
• The supporting Evidence

A later repetition creates a separate Test Run, even when it uses the same test definitions and produces the same Test Results.