Action: CheckApplicationState

Function: The action checks the state of an application.

Call: Category Online

Tab: Configuration

Tip

In order for the action to be executed successfully, a connection to the specified application has to exist.

Application

Application in the project whose state is tested

For the selection <active application>, the active application is determined at runtime.

Delay (ms)

Optional, additional waiting time before the state is checked for the first time

Timeout (ms)

When you define a value, the test is repeated until it is successful or the Timeout has elapsed. If this Timeout has elapsed, then the action fails.

If a value is not specified, then a timeout of 5000 ms is applied.

Table 29. Select the desired application state

Run
Stop
Halt on breakpoint
Debug step
Single cycle

If the actual state deviates from the selected state, then the action fails. When you check the Stopped state, you can query more whether or not an Exception occurred.

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