Changed functionality

Changes in Tosca Distribution Server and Tosca Distributed Execution Monitor

Tosca Distribution Server and Tosca Distributed Execution Monitor are now standalone Microsoft Windows service applications and independent of IIS.

Additionally, the following files and paths have changed:

• Tosca Distribution Server configuration file name changed from web.config to Tricentis.DistributionServerService.exe.config. This file is located at C:\Program Files (x86)\TRICENTIS\Tosca Server\DEXServer.

• Tosca Distribution Server parameter configuration file path changed from C:\Program Files (x86)\TRICENTIS\Tosca Server\DEXServer\bin\ConfigurationParameters.xml to C:\Program Files (x86)\TRICENTIS\Tosca Server\DEXServer\ConfigurationParameters.xml.

• Tosca Distributed Execution Monitor configuration file path changed from C:\Program Files (x86)\TRICENTIS\Tosca Server\DEXAdmin\wwwroot\assets\appConfig.json to C:\Program Files (x86)\Tricentis\Tosca Server\DexAdmin\Frontend\assets\appConfig.json.

Tosca Distributed Execution with AOS: no more results folders

This change applies if you upgrade from Tricentis Tosca 14.1 STS or older.

If you use Tosca Distributed Execution with AOS, you no longer have to create results folders for your TestEvents. As of Tricentis Tosca 14.2 LTS, Tosca saves results directly to the ExecutionLists.

Tosca doesn't delete existing results folders or results. But after the upgrade, every run saves the results to the ExecutionLists.

If you want to continue using your existing results folders for now, you can configure the Automation Object Service to do so.

The ability to keep results folders is a transitional solution. Tricentis will deprecate this functionality within the next releases.

To configure the Automation Object Service for results folders, follow the steps below:

1. After the upgrade, access the machine that holds Tosca Server.

2. Open the appsettings.json file. By default, this file is located at C:\Program Files (x86)\TRICENTIS\Tosca Server\AutomationObjectService.

3. In the setting ImportResultsMode, change the value from ExecutionLog to TestMandate.

{
  "AutomationObjectServiceConfig": {
    "ImportResultsMode": "TestMandate",
    "DexBaseUrl": "http://localhost:12345",
    "DexCallTimeout": 30000,
    "MaxWorkspaceConnections": 10,
    "SendRequestRetryAttempts": 1,
    "SendRequestRetryInterval": 5000,
    "TaskCallTimeout": 3600000,
    "TcApiWorkspaceFolder": "%TRICENTIS_PROJECTS%\\Tosca_Workspaces",
    "Workspaces": [
      {
        ...
      }
    ]
  },

DotNet Engine 3.0: Menu controls

You must re-scan any Menu controls from your DotNet Engine 3.0 Modules after you upgrade to Tricentis Tosca 14.3 STS.

Mobile Engine 3.0: Appium Server and Tosca Mobile Assistant installation

As of Tricentis Tosca 14.2 LTS Patch 1 and Tricentis Tosca 14.3 STS, the Appium Server and Tosca Mobile Assistant are no longer part of the Tricentis Tosca installation. Not having these components can affect the way you work with the Mobile Engine 3.0:

• Appium Server is a mandatory component if you want to run a local Appium Server and automate locally connected devices.

• Tosca Mobile Assistant is an optional component that allows the Mobile Scan to automatically display locally connected devices and applications installed on them.

The upgrade procedure depends on your previous Tricentis Tosca installation:

Tosca Data Integrity: changes in handling double quotes for CSV

If you use CSV files for Row by Row Comparison or File Load into Caching Database, you must now escape cell values with double quotes.

To ensure that Tosca Data Integrity can handle your CSV files properly, use the format recommended in RFC 4180.