Action: ResetApplication

Function: The action resets an application.

Call: Online test driver

Tab: Configuration

Tip

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

Application name

Name of the application to reset

: Copies the settings of a suitable object which are selected in the POUs tree or device tree to the input field

: Opens a list box with suitable objects which are configured in the open project

Table 30. Reset mode

Reset Warm	The application is reset, and retain variables are retained.
Reset Cold	The application including retain variables is reset, and only persistent variables retained.
Reset Origin	The application, including the all of its variables, is removed from the controller.

Force immediate kill

If the current application is halted at a breakpoint, then this option determines how the application is aborted.

standard icon : The application is reset immediately if the runtime system supports the aborting of a task during the execution cycle.

: The current cycle is ended before the application is aborted.

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