Settings - Engines

The following setting is located at Settings -> TBox -> Engines:

Setting

Description

Remote server connection timeout

Time in milliseconds that Tosca waits for XEngine server processes to establish an initial connection.

For example, the SAP Engine 3.0 components may use server processes such as Tricentis.Automation.ApiServer.exe. Establishing the initial connection may take longer than the default time, which is 20000 milliseconds.

For example: 45000

Remote server response timeout

Time in milliseconds that Tosca waits for a response from XEngine server processes. The default value is 120000.

For example: 150500

Key Vault path

The path to your key vault executable. For information about configuration for your specific key vault provider, check out "Specify a different path to the key vault executable".

For example: C:\Users\my\OnePwd

Database

Setting

Description

SQLite Enable Extension loading

If you enable this setting, you can load SQLite extensions, for instance to perform searches. You can load either external DLL files or the SQLite.Interop.dll library that is already installed with Tricentis Tosca.

To enable the setting, set it to True.

If you enable this setting, you also need to populate the setting SQLite Extension(s) to load.

For example: True

SQLite Extension(s) to load

Enter the full path of the extension(s) that you want to load as follows: \path\to\library\library.dll=extension_name. If you want to use multiple extensions, separate them with a semicolon.

If you want to load the SQLite.Interop.dll library, you do not need to enter the full path.

For example: SQLite.Interop.dll=sqlite3_json_init

Java

Setting

Description

DisableSecurityManager

This setting enables or disables the Java Security Manager used. The following options are available for selection:

  • True: the Java Security Manager is disabled.

  • False: the Java Security Manager is enabled.

  • Webstart Only: The Java Security Manager is disabled for Webstart applications only.

For example: False

Mobile 3.0

Setting

Description

Auto checkout/checkin configuration

Set to False if you don't want the Mobile Scan to automatically check out and check in the Mobile configuration node.

The default value is True.

For example: False

Default iOS Simulator Version

Default iOS simulator version.

For example: 11.3

Desired capabilities path

Path to a directory that contains the configuration files with Desired Capabilities.

For example: C:\YourFolder

Enable Native scan

Enables or disables scanning of native applications on Android in the Mobile Engine 3.0.

For example: False

Engine for mobile web scans

The engine you want to use to scan your mobile web applications. By default, this is set to Mobile Web Engine 3.0. We recommend keeping this setting for optimal performance and compatibility.

For example: XBrowser Engine 3.0

EncodeJavaScript

Encodes JavaScript resources for execution and scanning on mobile web applications.

The default value is False.

For example: True

PDF

Setting

Description

Compare failed pages directory

Path to the directory where you want to save the comparison report.

For example: @{Environment.ProjectDir}\PdfCompareFailedPages

Ignore whitespaces in text-only comparison

Specify whether you want to ignore whitespaces during a text-only comparison of two PDF files with the PDF 1:1 Compare Module. By default, the setting is False, which means that Tosca takes whitespaces into account.

For example: True

SAP

Setting

Description

Automatic TestCase creation and start Automation Recording Assistant (Tricentis ARA)

Enables Tricentis Tosca to automatically perform the following actions:

  1. Create the TestSteps SAP Logon, SAP Login, and SAP Toolbar.

  2. Run these TestSteps.

  3. Start Tricentis ARA.

The default value is False.

For example: True

Combobox items selectable by its Key

Enables Tricentis Tosca to identify ComboBox items by keys and values.

For example: False

Log level for Solution Documentation Synchronization

Enables Tricentis Tosca to save log messages that are exchanged between Tricentis Tosca and SAP Solution Manger.

The following options are available:

  • Off: no messages are logged.

  • Basic: the most important messages are logged.

  • Comprehensive: all messages are logged.

The default value is Off.

For example: Basic

Log path for Solution Documentation Synchronization

Specify the directory where you want to save the log messages that are exchanged between Tricentis Tosca and SAP Solution Manager.

For example: False

TableCompare

Setting

Description

EnableAutoCreateBaseline

Determines if automatic generation of baselines is enabled. The default value is False.

For example: True

UIA

Setting

Description

StopAtThumb

Defines if steering should stop at Thumbs with no name while looking for child elements.

If you set this setting to True, the scan will stop when a control with type Thumb is found. If you set the setting to False, the scan will not stop when a control with type Thumb is found and continues searching for the next child item of the control.

For example: True

Window Class Names

Enter one or more class names, separated by semicolon (;).Tosca treats elements with these class names as windows.

For example: Chrome_WidgetWin_1

Web service

These settings control API Engine 3.0 configuration.

Setting

Description

Auto pretty print

This setting specifies to use automatic pretty printing for API messages in your test case. This ensures that Tosca formats request and response payloads consistently during verification, which prevents false test failures that might occur when Tosca compares pretty-printed and non-pretty-printed JSONs.

For example: False

Request/Response log directory

This setting specifies the directory for log files. Tosca creates log files when you define the test configuration parameter WebserviceEngineLogRequestResponse.

For example: %APPDATA%\Tricentis\TOSCA Testsuite\7.0.0\logs\Automation\WSE

Response timeout

This setting specifies how many milliseconds the system waits for a web service to respond.

For example: 60000

Web service->Ports

Setting

Description

Server

Defines which port is used for the Webservice server.

For example: 17006

Web service->WebsphereMQ

Setting

Description

Enable JMS

If this setting is enabled, the message sent via WebsphereMQ receives a MQRFH2 header.

For example: True

Win32->Ports

Setting

Description

Server

Defines which port is used for the Win32 server.

For example: 17002

XBrowser

Setting

Description

Show alternative treegrid controls

Allows you to steer treegrids with table controls instead of TableTree controls. This simplifies tests for treegrids without nested elements. Note that for treegrids with nested elements, you must use table tree controls.

The default value is False, which means you won't see the table control option after you scan a treegrid with of Tosca XScan until you enable this setting.

Browser pipe connection timeout

Defines the time limit in milliseconds for establishing a connection between TBox and HtmlEngineExtensionHelpers. Its default value is 5000 milliseconds, which means TBox waits up to 5 seconds to establish a connection before timing out.

If your browser responds slowly, we recommend you try increasing this timeout value.

Note that if you don't set a TCP Browser, TBox waits up to three times the specified timeout value.

For example: 6000

Enable slot content handling

Specify whether to display controls as children of their assigned slot element. This setting works as follows:

  • If True, the controls appear as children of their assigned slot. During scanning, Tosca automatically adds the steering parameter EnableSlotContentHandling with the value True to XBrowser controls.

  • If False (default), the controls appear as they are in the DOM structure. During scanning, Tosca automatically adds the steering parameter EnableSlotContentHandling with the value False to XBrowser controls.

For example: False

Enable XPath identification

Allows you to use XPath expressions to identify HTML elements in your application during test automation. This is a more precise way to locate elements and lets you specify complex queries to target specific elements based on their attributes, hierarchy, or other characteristics. The default value is True.

For example: True

Hide Soft Hyphens

By default, XBrowser Engine 3.0 ignores soft hyphens for all HTML elements. If you want to see soft hyphens in controls' properties, change the value of this setting to False.

The properties InnerHtml and OuterHtml include soft hyphen in their values even if this setting is set to True.

For example: True

Ignore Aria controls

Specify whether to ignore the role of all or only specific ARIA controls during the scan. This setting works as follows:

  • If set to False (default), XBrowser Engine 3.0 automatically adds the steering parameter IgnoriaAriaControls to XBrowser controls during the scan and sets it to False. This option lets you use ARIA attributes to identify and steer these controls, if available.

  • If set to True, XBrowser Engine 3.0 doesn't automatically add the steering parameter IgnoriaAriaControls to XBrowser controls during the scan. This option maximizes compatibility. If you encounter issues with XBrowser customizations, set to True.

  • If set to a specific control name, XBrowser Engine 3.0 automatically adds the steering parameter IgnoreAriaControls to XBrowser controls during the scan and sets it to the specific control. This option lets you specify the specific ARIA roles you want to ignore. To ignore multiple controls, configure the setting using the control names, separated by commas (,) or semicolons (;). For example, if you want to ignore the ARIA controls ComboBoxes, Links, and ListBoxes at the same time, use the value combobox,link,listbox.

Note that changing the value of this setting doesn't automatically update previously scanned controls and their respective IgnoriaAriaControls steering parameter.

For example: False

Ignore invisible HTML elements

If you activate this setting, XScan for HTML pages adds the SteeringParameter "IgnoreInvisibleHtmlElements" to created Modules. The scan result will only contain the visible elements of the page. This improves scan and execution times if the tested HTML page contains a lot of invisible elements.

For example: False

Scrolling Behavior

Defines the default scrolling behavior for the XBrowser Engine 3.0 and for HTML controls to be steered with the Mobile Engine 3.0.

The following options are available:

  • No Scrolling

  • Scroll to top

  • Scroll to center

  • Scroll to bottom

For example: Scroll to center

XBrowser->Browser Settings

Setting

Description

Ajax tracer injection delay

Controls how long Tosca delays the injection of the AjaxTracer into the webpage. The default value is 0. Increase the value if you encounter problems on your webpage while running tests.

The time value is in milliseconds.

For example: 500

Close browser delay

Specifies how long the browser extension waits before it closes the browser. If you run into trouble with your webpage during tests, increase the value. The default value is 100.

The time value is in milliseconds.

For example: 100

Frame id retrieval timeout

Specifies the maximum time (in milliseconds) that Tosca waits to retrieve a CrossDomainFrame ID before timing out. The default value is 100 ms.

On slower machines or pages that use many resources, scanning or steering content inside CrossDomainFrames may fail. As a result, the XScan might show an empty frame. If this happens, we recommend increasing the value of this setting to allow more time for the frame retrieval process.

For example: 100

Handle asynchronous loading

Defines Tosca's wait behavior for busy pages that load content asynchronously:

  • If set to Strict, Tosca always waits for the page to fully load, before steering it.

  • If set to Loose, Tosca only waits for the initial loading time, before steering the page.

For example: Strict

Disable Ajax Tracer injection on pages

Disables the AjaxTracer scripts on the specified webpage URLs. To specify the URLs, you need to add them as CollectionEntries.

To add a CollectionEntry, right-click on Disable Ajax Tracer injection, click on Create... and select CollectionEntry. Use regular expressions to specify the URLs.

For example: .*example-page\.com.*

Disable Shadow Dom Unlocker injection on pages

Disables ShadowDomUnlocker scripts on the specified webpage URLs. To specify the URLs, you need to add them as CollectionEntries.

To add a CollectionEntry, right-click on Disable Shadow Dom Unlocker injection on pages, click on Create... and select CollectionEntry. Use regular expressions to specify the URLs.

Note that this setting only applies to WebDriver.

For example: .*example-page\.com.*

Minimum control dimensions

Defines the minimum dimensions for a visible control in pixels. Tosca considers a control visible only when both its height and width meet the pixel value you specify.

The default value is 0.5 pixels, and the lowest possible value is 0.0 pixels.

XBrowser->Internet Explorer->Ports

Setting

Description

Server

Defines which port is used for the Internet Explorer server.

For example: 17009

XBrowser->Salesforce

Setting

Description

Associated Labels Identification

Enables the Salesforce Scan to use the AssociatedLabel property instead of ApiKey to identify Salesforce controls.

By default, the setting is disabled. If set to True, you need to rescan existing Modules that don't have the AssociatedLabel property value.

For example: True

Custom Domain

URL of the custom domain production or sandbox environment in Salesforce.

For example: login.example-page.com

Exclude frames

Excludes the <frame> HTML elements when loading the HTML DOM structure in the Salesforce Engine.

For example: True

Exclude ShadowDoms

Excludes the <shadowRoot> HTML elements when loading the HTML DOM structure in the Salesforce Engine.

For example: True

SFDCQuickSearch

Enables Salesforce Engine to find controls more quickly during scanning and test execution. The default value is True. However, if you encounter issues with control recognition, we recommend setting the value to False.

For example: True

Scanner include classic objects

Displays objects defined in Salesforce Classic as tabs in the Salesforce Module.

For example: True

Scanner include lightning objects

Displays objects defined in Salesforce Lightning Experience as tabs in the Salesforce Module if they're not defined in Salesforce Classic.

For example: True

SFDC CPQ

Enables Tricentis Tosca to use adapters for CPQ automation. The following options are available for selection:

  • True: Loading of CPQ dlls is enabled.

  • False: Loading of CPQ dlls is disabled.

  • Auto (default): Tricentis Tosca automatically identifies objects as CPQ or not.

For example: Auto

Skip ApiKey

Skips the use of the ApiKey property to uniquely identify Salesforce controls.

By default, this setting is disabled. If you enable this setting and don't find Salesforce controls during execution, we recommend that you enable the Associated Labels Identification setting to uniquely identify Salesforce controls.

For example: True

URL based UI type identification

Enables Salesforce Engine to identify the Salesforce interface (Classic, Lightning) of the Salesforce application that you scanned based on URL.

For example: True

XBrowser->Salesforce->Api

Setting

Description

Consumer Key

Client ID of the application trying to connect to Salesforce APIs.

For example: 9578290mxur0ihf98c3n4y8mhfeuif

Consumer Secret

Client secret for authentication.

For example: jxr843oum5t9xe4rc

Password

Password to sign in to Salesforce.

For example: pass123

Username

Username to sign in to Salesforce.

For example: mylogin@salesforce.uk

KeyVaultPath

Path to the secret that you store in one of the supported key vaults.

To define the path, use the standard key vault path syntax, but without curly brackets.

For example: SECRET[cyberark][kv/database/production/pw][MyPassword][MyCyberarkAppID]

XBrowser->WebDriver

Setting

Description

Chrome path to use

Defines the path to the Chrome executable, which should be used by the WebDriver part of the XBrowser Engine 3.0. This setting is only available for local browser instances.

For example: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

Chrome WebDriver Path to use

Specify a path to the WebDriver executable for Chrome. XScan uses this path if the parameter WebDriver Path in the Select Application window is empty.

For example: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

Chrome WebDriver Port for embedded application to use

Specify a port of the WebDriver for Chrome. XScan uses this port if the parameter Debug Port in the Select Application window is empty.

For example: 9222

Edge path to use

Defines the path to the Edge Chromium executable, which should be used by the WebDriver part of the XBrowser Engine 3.0. This setting is only available for local browser instances.

For example: C:\Program Files (x86)\Google\Edge\Application\edge.exe

Edge WebDriver Path to use

Specify a path to the WebDriver executable for Edge. XScan uses this path if the parameter WebDriver Path in the Select Application window is empty.

For example: C:\Program Files (x86)\Google\Edge\Application\edge.exe

Edge WebDriver Port for embedded application to use

Specify a port of the WebDriver for Edge. XScan uses this port if the parameter Debug Port in the Select Application window is empty.

For example: 9222

Firefox path to use

Defines the path to the Firefox executable, which should be used by the WebDriver part of the XBrowser Engine 3.0. This setting is only available for local browser instances.

For example: C:\Program Files (x86)\Mozilla Firefox\firefox.exe

XBrowser->WebDriver->Cloud services->Browser Stack

Setting

Description

Access Key

Defines the access key of the BrowserStack account.

For example: CFkuSpEWajK2LM216Jmu

Hub Address

Defines the hub address, which should be used for BrowserStack.

For example: http://hub.browserstack.com/wd/hub/

Username

Defines the username of the Browser Stack account.

For example: myuser

XML->Ports

Setting

Description

XSD server

Defines which port is used for the XSD server.

For example: 17005