Dependencies

Introduction: You can find a description of this phase in section Phase 6 (Introduction). See especially sections States of Response Routes and Dependencies Between Response Routes.

(1) The execution of the Response Route can be made dependent on the successful or erroneous execution of a previous Response Route. The number to be entered corresponds to the position in (2). Note: If on success is selected, multiple response numbers can be specified comma separated. Note: If on error is selected and a variable that evaluates to * at runtime is specified as response number, the dependency is considered fulfilled.

(3) Executing a Response Route can be made dependent on a condition. On the one hand, string comparisons can be performed by comparing the value of a variable or system constant (selectable via the button) with an entered value or the value of a variable or system constant. On the other hand, you can perform Boolean comparisons if you select true or false on at least one side. In both cases an implicit type conversion takes place if one of the values is not of type String or Boolean. Regular expressions are also allowed with the prefix regex:, e.g. regex:^[ABC|XYZ].*$

Note: The string comparison is not case-sensitive. Note: A condition is displayed in the name of a Response Route with [Variable: ...].Note: Although only one variable can be used here in the condition in the Response Route, you can of course use a logic of any complexity with several variables and functions in the mapping. Whatever this logic produces as a result, you then store in a single variable and use this variable as a condition in the Response Route.

(4) The Response Route is either only executed in a test or not in a test or always.