Action: Login

Function: The action logs in to the active application on the controller.

Call: Online test driver

Tab: Configuration

Table 26. Authentication

User name

standard icon : The login takes place by means of authentication. User name and Password are required.

Note: The password is saved unencrypted in the test script.

Password

Table 27. Online change

No online change, perform download	A download is always performed. This option is enabled by default.
Try online change if possible, fall back to download	If an online change is possible, then it is performed. Otherwise a download is performed.
Always use online change (fails if not possible)	If an online change is possible, then it is performed. Otherwise the action fails.

Table 28. Application state

Start the application	The application is started after the download or online change if it was previously in "Stop" mode. This option is enabled by default.
Keep current state	The application remains in the current state. This option is available only for Always execute online change.
Stop application	The application remains in "Stop" mode after the download, or it is halted for online change if it was in "Run” mode.

Delete unknown applications	: At login, detected applications which do not exist in the current project below the same device are deleted from the controller.
Allow reinitialization of persistent variables	: Persistent variables which have inconsistencies are reinitialized automatically.

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