Action: UninstallAndCheckMessageHandler

Function: The action uninstalls the message defined by the action InstallMessageHandler and checks the messages which have occurred in the meantime using the filter configuration in InstallMessageHandler.

Call: System test driver

The action fails in the following cases:

If messages are missing that were not marked as Optional
If there were multiple messages which were not selected with the Multiple option
If the Report as error option was selected in All other messages, and messages occur which were not captured by the filters

Tab: Configuration

Identifier

Key from the InstallMessageHandler action for identifying the message handler

Timeout [ms]

Optional

Maximum time span (in milliseconds) for waiting if there are still pending messages which have not been marked as Optional (meaning that the corresponding filters have not yet been applied)

If dialogs are slowed down due to background processes (for example, Lazy Loading) after the action which actually triggers them, then they are captured.

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