Test Input

Go up to Terms and Definitions

A Test Input supplies data, a value, a signal, a command, an event, or another stimulus to a Candidate Solution during a Test Execution.

The applicable 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 Traceability between the Test Definition, Test Execution, Observations, and Test Outcome.

data, value, signal, command, event, or other stimulus supplied to a test item during test execution

Adapted from the testing concepts defined by:

• ISO/IEC/IEEE 29119-2:2021, Software and systems engineering — Software testing — Part 2: Test processes
• ISTQB Glossary, “test input”

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

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.