Action: FindMessage

Function: The action checks whether or not a specific message exists in the message memory.

Call: System test driver

Tab: Configuration

Search for message	Input field for the text which is searched for in the message texts The wildcards `*` and `?` are permitted here. The text is used as a regular expression. As a result, special characters such as periods `.` or parentheses `()` have to be escaped. If nothing is specified in this field, then all message texts apply.
Message key	String which is compared with the key of the message The message key consists of a prefix and 4 digits. Example: `Lint1234` If nothing is specified in this field, then all keys apply.
Severity	List box for the severity of the message which is searched for All Fatal Error Error Warning Information Text If nothing is selected, then the system searches for all degrees of severity.
Categories	: Opens a dialog where you can select a category
Matches	At least one: At least one match must be found in the message texts, otherwise the test action fails. None: If no match is found in the message texts, then the test action is successful.

Tip

. For this action, the test report displays additional information which is very useful for troubleshooting:

Filters: Output of search parameters defined on the Configuration tab
Example: At least one message must match
Matching message: Output of the message if one is found
Available messages: Output of all messages in the message memory if no message or an unexpected message is found

Tab: Parameters

The parameters defined on the Parameters tab are used to exchange values between test script variables and parameters of test actions. Parameters can be used as placeholders on the Configuration tab. For this, the name of the parameter is set in braces in the configuration dialog. Example: {name}.

Tip

Variables defined globally in the script (with the prefix $GLOBALS.) can be used directly in the test action. It is not necessary to use input parameters for passing. Using output parameters is necessary for writing global variables.

Input parameters: When executing the test action, the values of the test script variables are passed to the input parameters of the test action and can be used in the configuration of the test action.
Output parameters: When executing the test action, the values of the output parameters of the test action are passed to the test script variables and can be used (for example, in other test actions).
Name	Name of the input/output parameter This name is defined in addition to the variable name to identify the origin of the parameter when it is passed to another script. During the test run, this name is displayed as the Outer name on the Variables (scope #<n>) tab in the Test progress window. Background: When a script `A` calls another script `B`, and its variable `x` passes `y` as a parameter to the script `B`, then the parameter `y` is the variable `y` from the point of view of script `B`. To see that this variable is recognized as variable `x` "outside" of script `B`, there is the Name column ("Outer name"). The variable `y` has the name `x` in the scope pf script `B` because it has been passed as variable `x` to the parameter `y` in the scope of the calling script `A`.
Variable	Name of the test script variable Example: `TS_CaseA_Result`
Move Up	Moves the selected variable one line up
Move Down	Moves the selected variable one line down
Remove	Removes the selected variable from the list