dido:99_annexes:annex-b-terms-and-definitions:o:observation

Observation

An Observation records information detected, measured, received, or otherwise obtained while examining an object, activity, event, or condition.

During a Test Execution, an Observation records an aspect of the behavior, state, output, performance, or operating conditions of a Candidate Solution or its Test Environment.

An Observation records what occurred without determining whether the observed information satisfies an expected result or acceptance criterion. Evaluation of one or more Observations produces a Test Outcome.

An Observation may contribute to Evidence after DIDO-TE preserves the information, its source, its context, and its provenance.

information obtained by detecting, measuring, receiving, or otherwise examining a property, state, behavior, event, or condition

An Observation remains distinct from its interpretation.

For example:

  • “The service returned status code 503” records an Observation.
  • “The service failed the availability criterion” records a Test Outcome.

An Observation record identifies the applicable:

  • Test Execution
  • Source
  • Observed property, state, behavior, event, or condition
  • Observed value or description
  • Time of observation
  • Collection or measurement method
  • Measurement unit, when applicable
  • Relevant operating conditions

During a Test Execution, DIDO-TE records that the Candidate Solution rejected a Transfer Bundle and returned status code 403 at 14:32:18 UTC. This record constitutes an Observation. Comparison of the Observation with the expected behavior determines the Test Outcome.


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

  • dido/99_annexes/annex-b-terms-and-definitions/o/observation.txt
  • Last modified: 2026/08/06 12:36
  • by nick_dido