Action: CheckDeviceMessage
Function: The action checks the log messages on the on the controller.
Call: Devices test driver
Tab: Basis
Device | Device whose log messages are tested
Hint: You can also drag the settings of a selected object to the input field (Drag&Drop). |
Pattern | Expression to be searched for |
Compare type | Exact: The log message has to match the specified string exactly. |
Substring: The log message has to contain the specified string. | |
Message glob: The specified pattern has to match the message text by means of placeholders (* and ?). | |
Regular expression: The log message has to match the regular expression. | |
Raw message including parameters | ![]() |
Message ID | The specified message IDs have to match instead of the message text. |
Severity | All |
Exceptions | |
Error | |
Warnings | |
About | |
Hits | One or more: At least one log message has to be found. |
None: There must not be any log messages found. |
Tab: Extended
All | All components are searched. |
By name | The evaluation is restricted to a specific component by its name. |
By ID | The evaluation is restricted to a specific component by its ID. |
Logger |
|
All messages | All log messages are searched. |
Since message (text) | All log messages are searched by the time since a specific message text. |
Since message (ID) | All log messages are searched by the time since a specific message ID. |
Within time space of <...> seconds before newest message | Only the log messages within the specified time period are taken into consideration. |
Parameters | Output parameter where the found messages are saved Specified without quotation marks Example: {DeviceMessage} |
Choice | Newest: Save the newest log message |
Oldest: Save the oldest log message | |
All: Save all log messages | |
As STRING array | Requirement: The Selection parameter is All.
|
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 To see that this variable is recognized as variable |
Variable | Name of the test script variable Example: |
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 |