Changes and deprecations

Mobile Modules: folder structure update for capabilities

We've updated the folder structure to improve organization for mobile Modules within the Standard subset. To make actions related to capabilities easier to find, we've added a new subfolder called Capabilities and moved the Set Desired Capabilities Module into it.

Tricentis File Service: changed auto-removal behavior

Tricentis File Service is a web-based application that stores your Tosca files in a separate file system, which keeps your workspaces slim and improves their performance. By default, the service auto-removes execution log data after 90 days.

• Before 2024.2, Tosca started the timer when the data landed in Tricentis File Service.

• As of 2024.2, Tosca bases the removal on the creation date of a log.

In a normal workflow, this change doesn't cause much of a difference. You run your tests, Tosca creates execution log data and adds it to Tricentis File Service. After 90 days, Tosca auto-removes the data.

You'll only see a difference when you migrate data to Tricentis File Service.

Let's say you run your tests 30 days before migrating to Tricentis File Service.

• Before 2024.2, Tosca deleted these logs 90 days after migrating to Tricentis File Service.

• As of 2024.2, Tosca deletes these logs 60 days after migrating to Tricentis File Service, which is 90 days after their creation.

Tosca OSV: config files folder structure update

We've moved the Tosca OSV program files to the config folder.

Tosca CI with Remote Service: changed hashing algorithms

The setting HashingAlgorithm in the Tosca CI Client configuration file defines which algorithm Tosca uses to hash username and password before passing it on to the service.

Effective 2024.2, Tosca doesn't support SHA-1 and MD5 hashes. If you have defined either in your configuration file, Tosca ignores the setting value and automatically uses SHA-256. So, while you don't have to change the setting value after the upgrade, we recommend that you do, to avoid confusion later on.

By the way, if SHA-256 isn't enough, you can switch to SHA-384 or SHA-512. Note that if you change the HashingAlgorithm setting in the Tosca CI Client configuration file, you also have to change it in the Remote Service configuration file.

Mobile web test automation

We've upgraded to Mobile Web Engine 3.0 as the new default for mobile web scanning and execution. This change ensures you get more comprehensive functionality and better performance when compared to the old engine, which we've renamed Legacy Mobile Web. But no worries—your existing tests are safe! If your old TestCases run into any issue, you can easily switch back:

• For scanning issues, configure the setting Engine for mobile web scans to XBrowser Engine 3.0.

• For issues related to execution, add the test configuration parameter (TCP) UseLegacyMobileWeb and set it to True.

For TestCases where you've configured the TCP UseXBrowserForMobile, we recommend that you remove it to improve performance. In rare cases where Mobile Web Engine 3.0 doesn't boost performance, re-add the TCP.

Reporting: change of supported List & Label version

Report Designer is based on the third-party software List & Label^®. With the release of 2024.1, Tosca moves to List & Label version 29. Here's what that means for you:

• If you have custom reports that you created with Report Designer, you need to upgrade these reports.

  After the upgrade to Tosca 2024.1, you can't edit or print reports that you created with older List & Label versions. Any new reports you create automatically use the supported version.

• If you use the sample reports from the Standard subset, your best approach depends on the level of customization:

  If you're working with heavily customized standard reports, we recommend that you upgrade these.

  If you use more-or-less unchanged standard reports, we recommend that you import the 2024.1 subset and just use the new versions.

Reporting: TCShell

Printing reports with TCShell, Tosca's command line tool, just got easier.

Now, you don't have to modify the TCShell.dll.config file to get ready to print. You only need to make sure that your Report Definition has the right property values before you start printing. For detailed information, check out "Print reports with TCShell".

REST API: triggering test runs

Triggering test runs via REST API (opens in new tab) is now disabled by default.

To enable the ability to trigger test runs via REST API, follow these steps:

1. Open the REST API appsettings.json file. After a default installation, this file is at C:\Program Files (x86)\TRICENTIS\Tosca Server\RestApiService.

2. Change the setting DisableExecutionTasks to false.

3. Save and close the file, and then restart the service.

REST API: retrieving files

The REST API allows you to print a report and fetch the output file directly (opens in new tab).

As of 2024.1, you need to add a new parameter to your GET request: filename. This parameter specifies the desired name and type of the output file:

GET http|https://hostname:port/rest/toscacommander/resource?source=report&UniqueId={id}&reportname={reportname}&filename={filename}

For example:

GET https://mycompany.com:1234/rest/toscacommander/resource?source=report&UniqueId={111abc222}&reportname={UltimateReport}&filename={Ultimate_Q1_2024.pdf}

Tosca CI with Remote Service or Tosca Distributed Execution: changes in client settings

This section applies to legacy Tosca CI with Remote Service and Tosca Distributed Execution (DEX), if you run your tests on Windows operating systems.

The ToscaCIClient.exe.config file is now the ToscaCIClient.dll.config file. Additionally, we removed the system service model section from the file.

This results in the following changes after the upgrade:

• For Remote Execution Service, you need to define the service endpoint in the client configuration in a new setting: CIRemoteExecutionRestEndpoint.

• For Tosca DEX, you don't need to define the endpoint of the DEX Server in the client configuration anymore. Instead, specify the endpoint in call parameter -e when you trigger your test runs. This means that after the upgrade, you don't need to repopulate any endpoint setting, but you have to adapt your test launch commands.

Tosca CI with Remote Service: changes in service settings

This section only applies to legacy Tosca CI with Remote Service.

All Remote Service settings are now in the new appsettings.json file at %COMMANDER_HOME%\ToscaCI. Additionally, we've removed the system service model section from the file.

This means that after the upgrade, you need to re-configure settings differently:

• Make your changes in the new appsettings.json file. The old file still exists as ToscaCIRemoteExecutionService.dll.config, but Tosca ignores custom settings in the old file.

• If you want to define an HTTPS binding for the Remote Service, follow the steps in "Set up HTTPS communication with the Remote Service".

Tosca Copilot: part of the Tosca setup

Tosca Copilot is now part of the Tosca setup.

• If you install via setup dialog, Tosca Copilot is part of the standard installation. If you absolutely don't need it, perform a custom installation and deselect it from the feature set.

• If you install in unattended mode, Tosca Copilot isn't part of the standard installation. If you want to install it together with Tosca, define this with the ADDLOCAL argument.

Web accessibility testing: RunAccessibilityAnalysis TCP values

With version 2024.1, we've renamed a value of the RunAccessibilityAnalysis test configuration parameter (TCP). The value All Inputs is now called After Inputs.

Don't worry: your existing accessibility tests on All Inputs are safe. Tosca will continue to run your tests after every TestStep with ActionMode Input unless you choose a different behavior and modify the TCP value.

WinX Engine 3.0

The WinX Engine 3.0 no longer uses the x-axis coordinate to order columns in DataWindow controls with a single row. This can be a breaking change if you used Tricentis Tosca to steer single-row controls of this type, such as individual form fields that are tables.

If that's your case, make sure you re-scan your affected Modules so Tricentis Tosca can properly identify these controls.

Mobile Engine 3.0: config file name and location change

We've renamed the mobile config file %TBOX_HOME%/Tricentis.Automation.Mobile30Server.exe.config to Tricentis.Automation.Mobile30Server.dll.config and moved it to %PROGRAMFILES(x86)%\TRICENTIS\Tosca Testsuite\TBox\MobileServer.

PowerShell scripts

To use PowerShell scripts in your tests, you must add these files to %TBOX_HOME% :

• Microsoft.PowerShell.MarkdownRender.dll

• Microsoft.Management.Infrastructure.dll

• Microsoft.Management.Infrastructure.CimCmdlets.dll

• Microsoft.PowerShell.Commands.Diagnostics.dll

• Microsoft.PowerShell.Commands.Management.dll

• Microsoft.PowerShell.Commands.Utility.dll

• Microsoft.PowerShell.ConsoleHost.dll

• Microsoft.PowerShell.CoreCLR.Eventing.dll

• Microsoft.PowerShell.Security.dll

• Microsoft.PowerShell.MarkdownRender.dll

• Microsoft.WSMan.Management.dll

• Microsoft.WSMan.Runtime.dll System.Management.Automation.dll

• System.ServiceProcess.ServiceController.dll

qTest integration setup

The qTest integration settings are now in a separate tab in the Tricentis Service Configuration. If you've integrated Tosca and qTest, make sure to fill out the settings in the qTest Integration tab after the upgrade.

Standard subset

We made some changes to the Standard subset Module TBox Read/Create Files:

• The default encoding changed from active system encoding (e.g. ANSI, ISO-8859-1) to UTF-8. We recommend you adapt your tests or environment to use another supported encoding instead.

• The Module now supports ISO-8859-1 encoding.

• The Module doesn't support ISO-8859-15 encoding anymore. If you use this encoding in your tests, adapt your tests or environment to use different encoding.

SpecialExecutionTasks

We've updated some of our components to use the newer .NET 8.0 Framework. As a result, note the following for SpecialExecutionTasks (SETs):

• You need to adapt your tests if the libraries you have in your SETs use a different .NET version. Your current tests may not be fully compatible with .NET 8.0 Framework.

• You may need to add new dependencies to the ReferencedLibraries property of embedded SETs.

• You can no longer use TCAPI libraries in your embedded SETs. We recommend you use TCShell instead.

TextStream Engine 3.0

Due to a version upgrade of our internal libraries and components, the list of supported encoding for TextStream TestCases has changed. With 2023.2, we support the following encoding:

• Unicode

• Unicode (UTF-8)

• Unicode (UTF-32)

• Unicode (UTF-32 Big Endian)

• Western European (ISO)

We recommend that you review your TextStream TestCases and make necessary adjustments if the TextStream content is based on a different encoding.

Tosca Baseline Comparison 3.0: instantiate TestCases with TestCase-Design

If you work with TestCase templates with baselines, baselines are now maintained intact every time you create TemplateInstances or reinstantiate Instances.

Tosca Distributed Execution with AOS: changed encryption of Agent credentials for Unattended Execution

When you configure Agents for Unattended Execution, you specify each Agent's user name and password, either by entering the credentials themselves or by referencing the key vault that stores the credentials.

If you enter credentials, Tosca encrypts them. We've changed this encryption, which means that you need to re-enter the credentials after upgrading your Agents. That way, Tosca can save them in the new encryption.

The fastest way to re-enter those credentials is centrally, with the DEX Monitor:

1. Open the DEX Monitor and go to the Agent View.

2. Go through your list of Agents:

   • Select to open an Agent's Configuration window.

   • Go to the Unattended Execution tab and overwrite Username and Password. Then save and close the window.

If you're using a key vault for Agent user name or password, you don't need to do anything.

Tosca Distributed Execution with AOS: connection string to self-hosted AOS tasks database

If you use a self-hosted MS SQL database for AOS tasks instead of the default SQLite, you need to modify your connection string after the Tosca Server upgrade. We updated the underlying store to improve performance, which affects the syntax that the system accepts.

The connection string you have in the appsettings.json file or store in the key vault must now include TrustServerCertificate=true. For example:

Server=myserver.com;Database=myDataBase;User Id=myUsername;Password=myPassword;TrustServerCertificate=true

Tosca Options - View: new docked windows

To improve accessibility and usability, Tosca now docks new windows, such as Search, Scratchbook, and My Area by default. To switch back to the old behavior and let the windows float, go to Options->View and enable the setting Open new window floating.

Tricentis Data Integrity (DI): parallel execution

If you use Tosca Distributed Execution, you can run your DI tests in parallel on your Tosca Distribution Agents. We recommend this option if you're working with large test sets.

With Tosca 2023.2, it's no longer necessary to set an environment variable to enable this feature. Instead, you only configure the parallel blocks in Tosca.

If you already use parallel execution of your DI tests with Tosca Distributed Execution and you prefer a clean environment, you can remove the variable ENABLE_DEX_PARALLEL_EXECUTIONS from all machines.

You can also leave it. As of 2023.2, Tosca simply ignores the variable.

Standard subset

We've changed the behavior of some of our Standard subset Modules:

• If a Verify Window Exists operation with the TBox Window Operation Module fails, it now fails with verification failure instead of dialog failure. If you use Recovery, you need to adapt your settings, so Tosca triggers Recovery on the right error type.

• Tests associated to the Module TBox Delete Resource don't fail if the specified resource is already deleted or doesn't exist.

• The Module Run Selenium Scripts no longer generates a time-stamped HTML result file for JUnit tests.

Mail Engine 3.0: email body text

We made some changes to the Mail Modules in the Standard subset:

• In the Receive Mail Module, you can specify HTML or PLAIN text for the body of the mail. If you don't select an option, the mail default format is plain text.

• In the Send Mail Module, you can specify HTML or PLAIN text for the body of the mail. If you don't select an option, the system sends the mail in HTML format by default.

Tricentis Data Integrity: JDBC connections

As of version 2023.1, we support JDBC connections in the Row by Row Comparison and the Load Data into Database Module. Consequently, we've updated the Modules in the Data Integrity subset.

If you have existing tests that you want to switch to JDBC, follow these steps after the upgrade:

1. Right-click the old Module and select Tosca DI Migration->Update module to current version from the context menu. If you have multiple Modules, you need to migrate each Module separately.

2. In the subsequent dialog, choose whether to create a backup or not. We recommend that you do.

3. In the next dialog, select Yes to start the migration.

4. Adapt your TestCases.

Tricentis File Service: switch the database type

By default, Tricentis File Service creates an SQLite database to store metadata. As of this Tosca version, you can also use a self-hosted MS SQL database for it. If you want to switch from your old SQLite database to an MS SQL database, follow these steps:

1. Prepare your MS SQL database. Check out this section for a list of important considerations.

2. Upgrade Tosca Commander and Tosca Server.

3. Configure Tricentis File Service in the Tosca Service Configuration. Make sure to enter the connection details to your MS SQL database.

4. Restart Tricentis.File Service in the Windows Services app, so Tosca creates the necessary tables in your MS SQL database.

5. Ask your database administrator to export the data from the SQLite database, either as a CSV or SQL file. Then import the data into the MS SQL database.

XBrowser Engine 3.0: Selenium 4 Hub support

Tosca now supports Selenium 4 Hub. Consequently, the XBrowser Engine 3.0 doesn't steer embedded Chrome or Chromium applications version 82 or older. To verify the supported versions, check out our system requirements.

Mobile Engine 3.0: Desired Capabilities

As of Tosca 16.0, you can no longer use your Desired Capabilities configuration files for Mobile Scan. You need to add the Desired Capabilities directly in the Mobile Scan window.

TBox Define Excel Range Module

The Data Range ModuleAttribute in the TBox Define Excel Range Module now influences how the Excel Engine 3.0 calculates the values for the properties ColumnCount, RowCount, ColumnNumber, RowNumber, and ResultCount. The calculated result is now related to the specified Data Range, instead of the first cell of the specified workbook. You may need to adapt your table verification tests to consider the specified range.

Tricentis Data Integrity

We've updated the Tricentis Data Integrity libraries to .NET 6.

.NET 6 handles the data type Double differently. This causes a slightly lower precision in tolerances for reconciliation tests where you compare Avro files: 14 decimal places instead of 16.

Tricentis File Service and DokuSnapper

As of Tosca 16.0, you have specify where you want to save the DokuSnapper document. By default, Tosca saves the document locally, even if you have Tricentis File Service turned on. If you want to save the document to Tricentis File Service, change the Storage Location Type setting.

UIA Engine 3.0

The UIA Engine 3.0 has updated libraries. This may cause issues with property verification and control identification in your tests due to new property prefixes:

• If Tosca can't find your control because one or more identifying properties have changed, rescan the control. This updates all properties.

• If Tosca finds your control, but can't verify a specific property, you need to update the verification clause to match the new prefix. For instance, the property Orientation now contains a new prefix: OrientationType_. Consequently, you need to update your verification clause to .Orientation==OrientationType_<Value>.

Tosca Continuous Integration with Tosca Distributed Execution

The behavior of the Tosca CI Client setting CiClientTimeout has changed.

If the Tosca CI Client doesn't get a response within the specified time frame, it doesn't abort the execution anymore. Instead, the Tosca CI Client leaves the TestEvent in the queue until you cancel it in the Tosca Distributed Execution Monitor.

Tosca Commander: update of environment variable

The environment variable %TRICENTIS_HOME% now points to C:\Program Files (x86)\TRICENTIS\Tosca Testsuite\Settings. If you use this variable in your tests, you need to update them.

Tosca Distributed Execution

If you use Tosca Server with an HTTPS binding, Tosca Server now only allows authenticated requests. This means that users need to authenticate with Tricentis User Administration credentials whenever they perform an action that involves Tosca Server. Tosca Server checks whether a user with these credentials exists; if that's true, it proceeds with the task.

In a Tosca Distributed Execution context, authentication means the following:

• After the upgrade, users need to authenticate whenever they, for instance, trigger the execution of a TestEvent or want to access the DEX Monitor.

• Your Tosca Distribution Agents also need to authenticate. You have to create at least one user in Tricentis User Administration for your Agents; you can use the same account for multiple Agents. This user has to have a personal access token in Tricentis User Administration. You need the token's client ID and client secret when you start and connect your Agents after the upgrade.

Last, but not least: Tosca Distributed Execution with AOS is now the default setup. If you want to use Tosca Distributed Execution without AOS, you need to deactivate AOS after the upgrade.

Tricentis Data Integrity: new environment variable

The Data Integrity environment variable has changed from $ToscaDataIntegrity_Home to the new variable %TRICENTIS_DI_HOME%. If you use this variable in your tests, you need to update them.

Tricentis Data Integrity: blob storage in reconciliation tests

Reconciliation tests now also support data sets in blob storage. Consequently, we reworked the Complete Row by Row Comparison Module.

If you want to use the updated functionality in your existing reconciliation tests, you need to migrate the Complete Row by Row Comparison Module that's in your workspace and then modify your tests:

1. After the Tosca Commander upgrade, import the latest version of the Data Integrity subset.

2. Right-click the old Row by Row Comparison Module and select Tosca DI Migration->Update module to current version from the context menu. If you have multiple Row by Row Comparison Modules, you need to migrate each Module separately.

3. In the subsequent dialog, choose whether to create a backup or not. We recommend that you do.

4. In the next dialog, select Yes to start the migration.

5. Go through your tests and adapt your reconciliation TestStepValues.

Tricentis File Service

Tricentis Tosca 15.2 makes it easier to use Tricentis File Service. It's now automatically enabled for every new project that you add to the Tosca Administration Console. Additionally, it includes auto-removal functionality that removes execution log data from the Tricentis File Service file system after a certain period of time. This helps you to manage your file system size without any manual intervention.

• If you add a new project to the Tosca Administration Console, Tricentis File Service and auto-removal are turned on. This means that Tosca automatically saves your files to Tricentis File Service and removes all execution log data that's older than 90 days. If you don't want this, you can change the auto-removal behavior or turn off auto-removal.

• If you have an existing Tosca Administration Console project where you haven't enabled Tricentis File Service, Tricentis File Service and auto-removal are turned off. Click here for information on how to enable and set up Tricentis File Service.

• If you have an existing Tosca Administration Console project where you have enabled Tricentis File Service, Tricentis File Service is turned on, but auto-removal is turned off. Click here for information on how to turn on auto-removal. This is optional; you can still use Tricentis File Service without auto-removal.

Tricentis Tosca 15.2 includes new auto-removal settings in the File Service tab of the Tricentis Service Configuration. By default, these settings are active. However, this doesn't necessarily mean that auto-removal is turned on for a specific project. To verify that auto-removal is off, check the project in the Tosca Administration Console. If the File Service column says Auto-removal disabled, auto-removal is turned off.

You don't want to use Tricentis File Service at all? As of Tosca 15.2, you can also disable it.

Host Engine 3.0: changed way of cursor positioning

As of Tricentis Tosca 15.0 LTS, the Host Engine 3.0 uses the information in a TestStep to position the cursor. This means that it takes into account, for example, the row number in a TestStep instead of the current position of the cursor in your HOST emulator. Due to this change, consider the following scenarios:

• If you used one TestStep to enter values into multiple fields, you might need to adjust your tests so that there's a separate TestStep for each HOST control.

• If you used keyboard commands in your TestSteps to move the cursor, you might need to adjust your tests after you upgrade to Tricentis Tosca 15.0 LTS. If you want to steer HOST controls in relation to the current position of the cursor or move the cursor, use the Module TBox Host Send Keys instead of keyboard commands.

ToscaDistributed Execution Monitor

As of Tricentis Tosca 15.0, DEX Monitor components are in a different directory: C:\Program Files (x86)\TRICENTIS\Tosca Server\DexMonitor.

qTosca integration

Tricentis Tosca 15.0 introduces a new and improved integration with qTest.

If you have TestEvents that you linked to qTest with a previous Tosca version, note the following:

• The links between the TestEvents and qTest are still active.

• You can still update or remove links.

The new integration only transfers execution results from one Tosca project to one qTest instance. You define this qTest instance during the 15.0 integration setup. If the instance that you originally linked to your TestEvent is different from the defined 15.0 instance, the results transfer to qTest no longer works. So if you execute your old linked TestEvent, you don't see results in qTest.

Tricentis strongly recommends that you retire your linked TestEvents and create new qTest TestEvents instead. This gives you the following advantages:

• Enhanced results reporting and mapping. It doesn't matter if you trigger the execution in Tosca or in qTest; you see the results in both. Moreover, you can directly link your automated tests to qTestReleases and Test Cycles.

• You don't have to run the entire TestEvent every time. Instead, you can just run individual tests in Tosca and transfer results to qTest.

To switch to qTest TestEvents, follow the steps below:

1. Unlink your linked TestEvents. You don't have to delete the old objects from Tosca or from qTest; keep them if you want to keep a record of previous test results.

2. Create qTest TestEvents out of the existing TestEvents as described in chapter "Migrate existing Tosca TestEvents".

SelfHealingData steering param

The steering param SelfHealingData stores technical healing data. As of version 15.0 LTS, Tricentis Tosca no longer shows it in the Properties pane of the ModuleAttribute when you use Tosca XScan, Tosca Rescan, or the Recorder.

Tricentis Tosca now displays all self-healing properties in a separate Self-Healing Properties view of the ModuleAttribute.

WPF Engine 3.0

You might need to re-scan some ListBox controls from your WPF Engine 3.0 Modules after you upgrade.

Tosca Server components

As of Tricentis Tosca 15.0 LTS, all Tosca Server components use JQuery version 3.5.1.

SAP SNC configuration

Starting with 2024.2.6, the SAP SNC configuration is removed as this configuration is not supported with SAP technical users and, we noticed it wasn't used. This signifies that the SAP Solution Manager wizard does no longer include the SNC configuration screen and the SNC-related settings are no longer part of the configuration file. All SAP Solution Manager scenarios continue to work as expected.

Reporting: Crystal Reports for design definitions

As of 2024.1, you can no longer generate reports with Crystal Reports®.

Reporting: export parameters for Report Designer

Report Designer is based on the third-party software List & Label^®. With the release of 2024.1, Tosca moves to List & Label version 29.

In this version, List & Label no longer supports a number of parameters. As a result, we've also removed these export format parameters from Tosca:

• HTML_Charset

• HTML_FormHeader

• HTML_FormFooter

• Picture_JpegEncoding

• PDF_FontMode

• PDF_CompressStreamMethod

• PDF_JpegQuality

• PDF_PdfAMode

• XLS_Title

If you have a report that uses any of the listed parameters, Tosca marks the parameters as invalid. You can still print the report after the upgrade, but the output won't show any behavior you defined in invalid parameters. For detailed information on how to customize reports in the Report Designer user interface, check out the List & Label manual (opens in new tab).

Not sure if you're using one of these parameters? Just run this TQL search on the Reporting folder: 

=>SUBPARTS:ExportFormatParam[(Name=="HTML_Charset")OR(Name=="HTML_FormHeader")OR(Name=="HTML_FormFooter")OR(Name=="Picture_JpegEncoding")OR(Name=="PDF_FontMode")OR(Name=="PDF_CompressStreamMethod")OR(Name=="PDF_JpegQuality")OR(Name=="PDF_PdfAMode")OR(Name=="XLS_Title")]

TestCase Templates from Excel: .xls file support

Our latest version only supports .xlsx files as data sources for TestCase Templates. This is true for both Microsoft Excel options: files as templates and embedded or referenced Excel files as schema definitions.

If you use .xls files in your TestCase Templates, you need to exchange these files for .xlsx files after the upgrade.

Not sure if and where you use .xls data sources? Run these TQL searches:

• To find files as templates, run ->SUBPARTS:TestCase[(IsTemplate=i="true")AND(SchemaPath=i?"xls$")].

• To find embedded or referenced Excel files as schema definitions, run ->SUBPARTS:TestCase[(IsTemplate=i="true")AND(SchemaName=i?"xls$")].

Tosca Cloud integration via AddIn

Previously, you could integrate with Tosca Cloud via AOS or via AddIn. We're deprecating the AddIn, but we still offer test execution integration via AOS. Plus, we added an exciting new option: upload TestCases from Tosca on-premises to Tosca Cloud.

For detailed information, check out "Tosca Cloud integration".

Data Integrity Agent

We are deprecating the Data Integrity Agent with our latest version. Instead you should use the Complete Row By Row Comparison Module, which now also contains JDBC connections.

API Engine 3.0

The API Engine 3.0 no longer supports SAP RFC connections.

TBox Start Selenium Server Module

With the deprecation of Selenium Server by Selenium, we've removed the Module TBox Start Selenium Server from the Standard subset. Tosca also doesn't support it in tests, so if you use this Module in your TestCases, you must adapt them. We recommend the Module TBox Start Program for similar functionality.

Note that you can still use the Module TBox Run Selenium Scripts for supported unit testing frameworks.

As of this version, Tricentis discontinues the following components:

• AnyUI Engine 3.0

• PDF Vector Engine

• RDP Server for Distributed Execution

• Tosca Jenkins Plugin

• Tricentis User Administration Cloud authentication for Vision AI

• Webservice Engine 3.0

For more information, see this Tricentis Knowledge Base article.

Mobile Engine 3.0

For the Mobile Engine 3.0, we've discontinued the following functionality:

• Tosca Mobile Assistant

• Appium Server

• TestProject

We recommend that you use the Tricentis Mobile Agent, which supports these functionalities.

Tricentis Data Integrity: Web Hadoop File Systems (WebHDFS) support

We discontinued Web Hadoop File Systems (WebHDFS) support. This means you can't use WebHDFS as a source or target in reconciliation tests. If you have reconciliation tests where you use WebHDFS as a source or target, you need to update these tests.

To migrate your Row by Row Comparison Module and update your tests, follow these steps:

1. After the Tosca Commander upgrade, import the latest version of the Data Integrity subset.

2. Right-click the old Row by Row Comparison Module and select Tosca DI Migration->Update module to current version from the context menu. If you have multiple Row by Row Comparison Modules, you need to migrate each Module separately.

3. In the subsequent dialog, choose whether to create a backup or not. We recommend that you do.

4. In the next dialog, select Yes to start the migration. Tosca then performs the following actions:

   • It creates a copy of your Row by Row Comparison Module. This copy is the 2024.2 version, without WebHDFS. The copy keeps all other changes that you made to your old Module, for instance modified default values for non-WebHDFS ModuleAttributes.

   • It creates a copy of all TestSteps that you created from the old Module and links them to the copy of the Module. Tosca removes the WebHDFS TestStepValues from the TestStep copies, but keeps all other values intact.

   • It deactivates all original TestSteps that you created from the old Row by Row Comparison Module.

   • It adds (WebHDFS deprecated) to the name of the old Module and its connected TestSteps.

5. Go through all TestStep copies and define a new source and/or target for each of them. We recommend that you use Rclone instead of WebHDFS.

6. Remove the deactivated TestSteps and the old Module.

Mobile Engine 3.0: supported online clouds

Tricentis Tosca 15.2 LTS doesn't support the clouds Experitest and GigaFox. If you access your device, emulator, or simulator by using one of them, you need to adjust your configurations.

Tosca Distributed Execution with AOS: no more results folders

Tosca Distributed Execution with AOS no longer supports results folders at all. Instead, Tosca now saves the results of your test runs directly to the ExecutionLists.

Tosca doesn't delete existing results folders, so you still have access to your old results. However, any test that you run after the upgrade ignores existing results folders and writes the results to your ExecutionLists.

For earlier versions, Tosca offered a workaround, where you could modify settings to bring back the old behavior, but this workaround no longer works.

Tosca Wizard (Legacy Scan)

As of Tricentis Tosca 15.0 LTS, you can't use Tosca Wizard (Legacy Scan) to create Classic TestCases anymore. This effort is part of the Classic Engines discontinuation.

For the deprecation announcement, see this Tricentis Knowledge Base article (opens in new tab).