Expected Result

Go up to Terms and Definitions

Discussion

An Expected Result specifies an anticipated value, state, state transition, event, condition, behavior, response, side effect, or outcome associated with the performance of a Sequenced Test Object or Sequence Step.

An Expected Result provides the basis for evaluating an observed or derived Test Result. The Expected Result states what the test anticipates. The Test Result records what occurred.

An Expected Result expresses one or more objectively evaluable conditions, including:

An anticipated value or permitted set of valuesAn anticipated state or state transitionAn anticipated event, response, or behaviorAn anticipated side effectThe absence of an event, response, behavior, or side effectA required range, threshold, tolerance, or precisionA required ordering or temporal relationshipA required completion or error conditionA permitted or prohibited outcomeAn Expected Result applies to a:

During or after Test Execution, an evaluator or automated mechanism compares the applicable Test Result with the Expected Result. The evaluator or mechanism then applies the governing Evaluation Criteria to assign a Verdict.

Definition

anticipated value, state, state transition, event, condition, behavior, response, side effect, or outcome used as a basis for evaluating a Test Result

Source

Adapted from:

DIDO Reference Implementation Conceptual ModelDIDO-TE draft Requirements RegisterOMG TestIF defines the expectedResult attribute for representing expected-result values associated with a SequencedTestObject or SequenceStep.

OMG TestIF permits the expectedResult attribute to contain multiple values when the anticipated result requires more than one value.

This definition generalizes the TestIF concept beyond a single value while preserving its role as the anticipated result used to evaluate a Test Result.

Note

Use Expected Result as the singular glossary term. Link plural occurrences to this page:

[[dido:99_annexes:annex-b-terms-and-definitions:e:expected_result|Expected Results]]

An Expected Result differs from a Test Result:

An Expected Result specifies an anticipated resultA Test Result records an observed or derived resultAn Expected Result differs from a Verdict:

An Expected Result states what the test anticipatesA Verdict classifies a Test Result according to the governing Evaluation CriteriaAn Expected Result differs from Acceptance Criteria:

An Expected Result specifies an anticipated result associated with a testAcceptance Criteria establish the conditions governing acceptance of an evaluated subject or outcomeAcceptance Criteria reference applicable Expected Results when acceptance depends upon the results of testing.

An Expected Result identifies or references the information required for repeatable evaluation, including:

The applicable Sequenced Test Object or Sequence StepThe applicable Test ItemThe applicable Test Argument ValuesThe anticipated value, state, event, condition, behavior, response, side effect, or outcomeAny applicable unit of measureAny applicable range, threshold, tolerance, or precisionAny applicable ordering or timing conditionThe comparison methodThe governing Evaluation CriteriaThe applicable Acceptance CriteriaThe applicable Governance PoliciesIts ProvenanceIts TraceabilityAn Expected Result containing multiple related values preserves the relationship among those values.

A Sequenced Test Object defines a reusable Expected Result. A Sequence Step refines or supplies an occurrence-specific Expected Result when the anticipated result depends upon:

Test Argument ValuesThe position of the Sequence StepA preceding stateThe execution pathThe applicable Test ItemThe Test EnvironmentOther occurrence-specific conditionsAn Expected Result provides sufficient information for objective and repeatable evaluation. Expressions such as “works correctly,” “responds quickly,” “performs adequately,” or “produces an appropriate result” do not establish an objectively evaluable Expected Result without additional criteria.

A difference between an Expected Result and a Test Result does not establish the cause of the difference. The Test Result and supporting Evidence preserve the observed or derived result.

An Expected Result does not establish a Validation Decision. The Validation Decision applies the governing decision criteria to the applicable Test Results, Verdicts, and Evidence.

Example

A Test Step directs a selected Node to process a valid transaction.

The Expected Result specifies that:

The Node accepts the transactionThe Node returns a nonempty transaction identifierThe Node records the committed transaction stateThe committed state references the preceding stateThe response occurs within five secondsThe Node produces no duplicate committed stateDuring Test Execution, the applicable Test Result records:

The observed responseThe returned transaction identifierThe resulting transaction stateThe predecessor-state referenceThe measured response timeAny duplicate committed stateThe supporting EvidenceThe evaluator compares the Test Result with the Expected Result and applies the governing Evaluation Criteria to assign the applicable Verdict.

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