Action: StopTimer

Function: The action ends the time measurement for a specified timer.

Call: System test driver

Tab: Configuration

Timer name

(required) Name of the timer which was previously created with StartTimer

Example: Timer_App1

Fail if value is greater than [ms]

standard icon : The test action fails if the specified time limit is exceeded.

Log to file

standard icon : One line with the timer data (name, start time, end time, duration) is included in the log file. If the log file does not exist yet, then it is created.

Table 70. Write the end time to output parameters

Variable	Output parameter where the end time is applied Specified without quotation marks Example: `{EndTimeTimer1}`
Format from Variable	.NET DateTime Example: `10/16/2017 09:30:05` IEC DateAndTime: Example: `DT#2017-10-16-9:30:5.283` IEC TimeOfDay: Example: `TOD#9:40:5-283` Own format: The Format field is active. An example of the selected format is displayed in the line below.
Format	List box with standard .NET format codes An example of the selected format code is displayed in the line below.
Display field	An example of the selected format is displayed here.

Table 71. Write the duration to output parameters

Variable	Output parameter where the duration is written Specified without quotation marks Example: `{EndTimeDuration}`
Possible formats for Variable	.NET DateTime Example: `10/16/2017 09:30:05` IEC DateAndTime: Example: `DT#2017-10-16-9:30:5.283` IEC TimeOfDay: Example: `TOD#9:40:5-283` Own format: The Format field is active. An example of the selected format is displayed in the line below.
Format	List box with standard .NET format codes An example of the selected format code is displayed in the line below.
Display field	An example of the selected format is displayed here.

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