Skip to main content

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

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

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

Table 40. 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.

_cds_icon_option_deactivated.png: 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. The name of the parameter is set in braces in the configuration dialog when doing this. Example: {name}.

Tip

Variables defined globally in the script (with the prefix $GLOBALS.) can be used directly in the test action. Passing them via input parameters is not necessary. Writing to global variables requires the use of output parameters.

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 passes its variable x to script B as parameter y, then from the point of view of script B, the parameter y is the variable y.

To see that, "outside" of script B, this variable is known as variable x, there is the Name column ("Outer Name"). In the scope of script B, the variable y has the name x because, in the scope of the calling script A, it was passed as variable x to the parameter y.

Variable

Name of the test script variable

Example: TS_CaseA_Result

Up

Moves the selected variable one line up

Down

Moves the selected variable one line down

Remove

Removes the selected variable from the list