Settings - Engine

The following settings can be found under Settings->Engine:

Accept unknown dynamic expressions
Description	If set to Yes, unknown dynamic expressions are transferred to the corresponding operator. If set to No, an error message is displayed for the unknown dynamic expression.
Example	No

Application’s current version
Description	Use this setting to enter the version number of the application under test. You can also use dynamic expressions, which Tricentis Tosca translates at the time of execution and enters into the test result. For more information on dynamic expressions, see the following chapters: "Specify values" if you use Engines 3.0. "Dynamic expressions" if you use Classic Engines.
Example	V0.3 {DATE}

Application’s current version

Description

Use this setting to enter the version number of the application under test. You can also use dynamic expressions, which Tricentis Tosca translates at the time of execution and enters into the test result. For more information on dynamic expressions, see the following chapters:

"Specify values" if you use Engines 3.0.
"Dynamic expressions" if you use Classic Engines.

Example

V0.3 {DATE}

Buffer
Description	This node contains the buffer variables and the corresponding values from the current project. This node is only visible if buffer values are defined (see chapter "ActionMode Buffer").
Example	Buffer name = Stock. The respective value of the buffer Stock is shown on the right hand side.

Class Mapping Path
Description	This is the path where the ObjectMappings.dat file is stored. This file is used for assigning business-based automation classes to technical representations. Multiple ObjectMappings.dat files can be specified, separated by semicolons. The order of the files is determined by their priority, i.e. the first file entry has the highest priority, whereas the last entry has the lowest priority. The files are searched from left to right, starting with the highest priority. The first occurrence is always used. If multiple files are used, specific changes become more transparent, which in turn makes upgrading to newer Tosca versions more easily.
Example	${TRICENTIS_HOME}\dll\dat\ObjectMappings.dat

Class Mapping Path

Description

This is the path where the ObjectMappings.dat file is stored. This file is used for assigning business-based automation classes to technical representations.

Multiple ObjectMappings.dat files can be specified, separated by semicolons. The order of the files is determined by their priority, i.e. the first file entry has the highest priority, whereas the last entry has the lowest priority. The files are searched from left to right, starting with the highest priority. The first occurrence is always used.

If multiple files are used, specific changes become more transparent, which in turn makes upgrading to newer Tosca versions more easily.

Example

${TRICENTIS_HOME}\dll\dat\ObjectMappings.dat

Current Test User
Description	The user information to be used in the test result can be specified here. This information is shown in the User column of an ExecutionList, in the Execution section. <Windows Logon>: the user name of the currently logged on Windows user is used. <Tosca Logon>: the user name of the currently logged on Tosca user is used. It is also possible to specify both Logon options combined with each other, separated by a space. Any other text entered here is directly used as user information. Exception: In case of manual test execution and manual setting of test results, the Tosca user is always used, independent of the value entered here.
Example	<Tosca Logon>

Current Test User

Description

The user information to be used in the test result can be specified here. This information is shown in the User column of an ExecutionList, in the Execution section.
<Windows Logon>: the user name of the currently logged on Windows user is used.
<Tosca Logon>: the user name of the currently logged on Tosca user is used.

It is also possible to specify both Logon options combined with each other, separated by a space.

Any other text entered here is directly used as user information.

Exception:

In case of manual test execution and manual setting of test results, the Tosca user is always used, independent of the value entered here.

Example

Display start settings
Description	Regulates whether the execution settings dialog is shown before the test starts.
Example	Do not show

Executable to start
Description	Describes the program to be used for the test execution and its current path.
Example	${TRICENTIS_HOME}\dll\TOSCAExecutor.exe

Execution Timeout
Description	Time in milliseconds to wait, before the desired window is opened.
Example	5000

Key Delay
Description	The delay between two keyboard inputs performed by the engine in milliseconds. The engine-specific settings may affect this behavior.
Example	100

Report Successful Execution of
Description	Specifies on which level execution results (TestState) should be displayed in the ExecutionLists section (see chapter "Change the view of your execution results "). You can choose from the following values: TestCases: The test result is written on the TestCase level if the test result is either failed or halted. TestSteps: The test result is written on the TestStep level if the test result is either OK, failed or halted. TestStepValues - All: This is the default setting. The test result is written on the TestStepValue level if the test result is either OK, failed or halted. Modifications are written all at once to the TestResult.xml file at the end of the execution which leads to shorter wait times during test execution. TestStepValues - Verify only: The test result is written on the TestStepValue level if the test result is either OK, failed or halted, and if the ActionMode of the TestStepValue is set to Verify. Debugmode: This mode is mainly used for debugging. Each modification is written immediately to the TestResult.xml file. This leads to longer wait times during test execution.
Example	TestStepValues - All

Report Successful Execution of

Description

Specifies on which level execution results (TestState) should be displayed in the ExecutionLists section (see chapter "Change the view of your execution results "). You can choose from the following values:

TestCases: The test result is written on the TestCase level if the test result is either failed or halted.
TestSteps: The test result is written on the TestStep level if the test result is either OK, failed or halted.
TestStepValues - All: This is the default setting. The test result is written on the TestStepValue level if the test result is either OK, failed or halted. Modifications are written all at once to the TestResult.xml file at the end of the execution which leads to shorter wait times during test execution.
TestStepValues - Verify only: The test result is written on the TestStepValue level if the test result is either OK, failed or halted, and if the ActionMode of the TestStepValue is set to Verify.
Debugmode: This mode is mainly used for debugging. Each modification is written immediately to the TestResult.xml file. This leads to longer wait times during test execution.

Example

TestStepValues - All

If Report Successful Execution of is set to TestCases and the setting Log buffer values is set to Test data or All, TestSteps with buffer operations appear in the log.

Use Buffer Caching
Description	If this setting is enabled, the buffer values will be loaded once from the Settings dialog when accessed for the first time and cached for the execution. If this setting is disabled, the buffer values will be read during every access from the Settings dialog .
Example	No

Use ObjectMap caching
Description	By default, ObjectMaps are managed in the server database. ObjectMaps can be cached for local Tosca use to compensate for slow or unstable network connections.
Example	No

Wait Intermediate
Description	Interval of time in milliseconds between the processing of two TestStepValues.
Example	0

Windows Class Mapping Path
Description	The path to the WinClassMappings.dat file
Example	${TRICENTIS_HOME}\dll\dat\WinClassMappings.dat