public:99_annexes:annex-b-terms-and-definitions:t:test_event

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:t:test_event [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:t:test_event [2026/09/13 17:06] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Test Event ======
 +
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A **Test Event** is an observable occurrence during a [[public:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] that is relevant to the behavior, state, or result of the [[public:99_annexes:annex-b-terms-and-definitions:t:test|Test]]. A Test Event may correspond to an action, interaction, state change, condition, message, external occurrence, or point in time.
 +
 +A Test Event may be planned by a [[public:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]] or observed only during Test Execution. Its occurrence may be associated with a [[public:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]], an [[public:99_annexes:annex-b-terms-and-definitions:e:executed_sequence_step|Executed Sequence Step]], a [[public:99_annexes:annex-b-terms-and-definitions:n:node|Node]], a [[public:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]], or an external dependency.
 +
 +A Test Event remains distinct from an Executed Sequence Step. An Executed Sequence Step records the performance of a definition-side Sequence Step. A Test Event may occur within, between, or independently of Executed Sequence Steps.
 +
 +===== Definition =====
 +
 +observable occurrence during a [[public:99_annexes:annex-b-terms-and-definitions:t:test_execution|test execution]] that is relevant to the behavior, state, or result of the [[public:99_annexes:annex-b-terms-and-definitions:t:test|test]]
 +
 +===== Source =====
 +
 +Derived for DIDO-TE from [[private:07-dido-te:99-annexes:annex-b-references:dte-001|[DTE1] U.S. Patent Application US20220237111A1]], recorded points in time and recording and playback of test activity; and [[https://www.omg.org/spec/TestIF/1.0/PDF|OMG Test Information Interchange Format (TestIF), Version 1.0]], test-execution concepts
 +
 +===== Note =====
 +
 +A Test Event is not required to be selected for recording or playback. Selection for inclusion in a [[public:99_annexes:annex-b-terms-and-definitions:t:test_activity_record|Test Activity Record]] is a separate governed decision.
 +
 +The occurrence time, order, source, associated Test Run, and other contextual information are attributes or relationships of a recorded Test Event. They are not part of the definition of the term.
 +
 +===== Example =====
 +
 +A Node publishing a message, a communication link becoming unavailable, a Sequence Step beginning, and a configured timeout expiring are Test Events when those occurrences are relevant to the behavior, state, or result of the Test.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>