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

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_input [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:t:test_input [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Test Input ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Test Input supplies data, a value, a signal, a command, an event, or another stimulus to a [[public:99_annexes:annex-b-terms-and-definitions:c:candidate_solution|Candidate Solution]] during a [[public:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]].
 +
 +The applicable [[public:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]] identifies each Test Input and establishes its value, form, source, sequence, timing, or delivery condition.
 +
 +A Test Input differs from a configuration. A configuration establishes the arrangement or settings under which the Candidate Solution operates. A Test Input supplies content or a stimulus to the Candidate Solution as part of the test.
 +
 +DIDO-TE records the Test Inputs used during each Test Execution to preserve [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] between the Test Definition, Test Execution, [[public:99_annexes:annex-b-terms-and-definitions:o:observation|Observations]], and [[public:99_annexes:annex-b-terms-and-definitions:t:test_outcome|Test Outcome]].
 +
 +===== Definition =====
 +
 +//data, value, signal, command, event, or other stimulus supplied to a test item during test execution//
 +
 +===== Source =====
 +
 +Adapted from the testing concepts defined by:
 +
 +  * [[https://www.iso.org/standard/79428.html|ISO/IEC/IEEE 29119-2:2021, Software and systems engineering — Software testing — Part 2: Test processes]]
 +  * [[https://glossary.istqb.org/en/term/test-input|ISTQB Glossary, “test input”]]
 +
 +===== Note =====
 +
 +A Test Input identifies what the test applies to the Candidate Solution. It does not represent the Candidate Solution’s response.
 +
 +A Test Input record includes the information needed to reproduce or interpret the input, such as:
 +
 +  * Input identifier
 +  * Value or content
 +  * Format
 +  * Source
 +  * Sequence
 +  * Time of application
 +  * Delivery mechanism
 +  * Applicable Test Execution
 +
 +===== Example =====
 +
 +A DIDO-TE Test Definition instructs the Candidate Solution to process a digitally signed Transfer Bundle. The Transfer Bundle and the command that initiates its processing constitute Test Inputs. The resulting log entries, state changes, and returned status constitute Observations.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>