Changed functionality
This chapter lists changed functionalities of Tricentis Tosca 14.2 LTS, compared to version 14.1 STS.
Federal Information Processing Standard (FIPS) compliance
As of Tricentis Tosca 14.2 LTS, the communication between Tosca components and the license server uses FIPS-compliant encryption algorithms.
Before and after the upgrade, you need to consider the following:
-
Before you upgrade, return checked-out licenses. Alternatively, if you use on-premise licensing, you can also revoke floating licenses in the Tosca License Administration application.
-
After you upgrade, reactivate node-locked licenses, as Tosca Commander cannot return them before the upgrade. To reactivate the licenses, contact the Tricentis License Team.
-
After you upgrade, re-login to the Cloud license server, if you use Cloud licensing.
Mobile Engine 3.0: disabled XPath
The XPath feature is now disabled by default. If you have mobile tests that identify the controls in your mobile application by the technical property XPath, these tests won't work with Tricentis Tosca 14.2.
You can enable the XPath feature manually as described in this Knowledge Base article.
However, Tricentis recommends that you only do so if you cannot use any other property for unique identification. Identification via XPath property decreases the performance of mobile tests.
Removed IIS dependency of Tosca License Administration
Tosca License Administration is now a standalone Microsoft Windows service application and independent of IIS.
Tricentis Tosca 14.2 LTS identifies Salesforce controls by the property ApiKey whenever this property is available.
This means that you can create your Salesforce Modules in one language and use them to test your Salesforce application in another language.
However, if you want to use this feature with Modules that you created with a previous Tricentis Tosca version, you have to rescan these Modules:
-
If you created the Modules with the Salesforce Scanner, rescan them with the Salesforce Scanner.
-
If you created the Modules with XScan, rescan them with XScan.
TBox Window Operations Module: changed behavior of the BringToFront operation
The BringToFront operation of the TBox Window Operations Module runs faster now. However, depending on the complexity of the window UI and your machine's performance, loading controls on the window that was brought forward by the operation might take varying amounts of time.
To ensure that your next TestStep runs, add a TestStep after the BringToFront operation that waits until a control on the window is visible before executing the next TestStep.
TC-Shell: task name change
With the introduction of the new PuTTY Engine 3.0 in Tricentis Tosca 14.2 LTS, the task Scan Host was renamed to Scan Remote Terminal. This change affects any TC-Shell scripts that contain the previous task name.
If you use TC-Shell to execute this task, you have to rename it accordingly in your TC-Shell scripts.
Tosca Distributed Execution with AOS: no more results folders
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:
-
After the upgrade, access the machine that holds Tosca Server.
-
Open the appsettings.json file. By default, this file is located at C:\Program Files (x86)\TRICENTIS\Tosca Server\AutomationObjectService.
-
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": [
{
...
}
]
},
-
Save and close the file.
-
Restart the Automation Object Service via IIS Manager.
For more information on results folders, see the Tricentis Tosca 14.1 STS manual.
Tosca Orchestrated Service Virtualization: using external libraries
As of Tricentis Tosca 14.2 LTS, the folder <Tosca OSV program files>\Environment has been renamed to <Tosca OSV program files>\Simulator.
If you are using external libraries, for example Tibco or Weblogic, you have to move these files to the new simulator folder.
Tricentis Tosca Rescan: Module properties
As of Tricentis Tosca 14.2
Deprecation announcements
Tricentis announces the deprecation of the following products:
-
Classic Engines will be completely discontinued with the release of Tricentis Tosca 15.1. For detailed information on the deprecation timeline, see this Tricentis Knowledge Base article.
-
TDM Studio versions 13.1 and earlier will be completely discontinued by 31 December, 2023. For detailed information about the deprecation timeline, see this Tricenis Knowledge Base article.