XEngine migrations
An XEngine migration updates existing Modules of the Standard subset and their connected TestCases to version 2024.2.
Please note that a migration doesn't automatically import any new Modules that we've added to the 2024.2 Standard subset. To get the new Modules, you need to import the 2024.2 Standard subset.
Important considerations
A Tosca version may have changed Modules, but still not need a migration. Not every change to a Module in the Standard subset requires an XEngine migration.
Check out the version table to find out which Tosca versions have changes that do require a migration.
However, even if a version has these changes, you still may not need an XEngine migration:
-
If you don't use any of the changed Modules in your tests.
-
If you only use one or two changed Modules in your tests. In this case, we recommend a faster alternative approach: import the new Standard subset and merge the affected Modules.
Keep in mind that 2024.2 includes all changes from previous versions. As a result, you also need to consider the versions between 2024.2 and the one you upgrade from.
Let's say you upgrade from Tosca 14.2. While 2024.2 doesn't have any changes that require an XEngine migration, 14.3 does. These changes are also in 2024.2. Consequently, if you use the 1:1 File Compare Module extensively in your tests, you need a migration.
Migration process
You can migrate manually or, if you use the Tosca Administration Console, directly in the console.
Please choose your use case:

If you use the Tosca Administration Console, you can trigger the migration directly in the console.
Prepare for the migration
Since the console is part of Tosca Server, you need to perform these preparatory steps:
-
Install Tosca2024.2 on the server machine.
Perform the migration
For detailed instructions, check out "Migrate projects with the Tosca Administration Console".

If you don't use the console, you have to migrate manually:
-
Open any workspace that's connected to the common repository.
-
If you're in a multi-user environment, check out the project root element.
-
Right-click the project root element and select XEngines Migration->Update project to current version from the context menu.
-
In the Backup dialog, choose whether to create a backup. We recommend that you do, just to be on the safe side. In this case, Tosca creates one of the following objects in %TRICENTIS_ALLUSERS_APPDATA%\Automation\MigrationBackup:
-
A .tde backup for multi-user repositories.
-
A .tsu backup for single-user repositories.
-
Once the migration is done, Tosca displays a migration report that indicates whether or not the migration was successful. If you accidentally close the report, you can find it again at %APPDATA%\TRICENTIS\TOSCA TestSuite\7.0.0\logs\Automation\ToscaDIMigration.
List of Tosca versions
This table lists Tosca Commander versions and any changes that require an XEngine migration:
Tosca version |
Changes that require an XEngine migration |
---|---|
2024.2 |
None. |
2024.1 |
|
2023.2 |
None. |
2023.1 |
None. |
16.0 LTS |
None. |
15.2 LTS |
None. |
15.1 STS |
None. |
15.0 LTS |
None. |
14.3 STS |
|
14.2 LTS |
None. |
14.0 |
None. |
13.4 |
None. |
13.3 |
|
13.2 |
|
13.1 |
|