Upgrade Tosca Commander

We recommend that you install and test the new Tosca version in a test environment before you perform the upgrade in production.

The basic workflow of a Tosca Commander upgrade from version 2023.1 LTS to 2023.2 LTS is as follows:

1. Perform the necessary preparatory steps: create backups and clean up %COMMANDER_HOME%.

   You need to perform these steps on every machine that has Tosca Commander installed.

   When you upgrade to a new version of Tricentis Tosca, the system installs new versions of configuration files, which might overwrite hidden settings that you applied to the previous version.

   For information on how to avoid losing certain settings when upgrading, see this Tricentis Knowledge Base article.

   If you upgrade to 2023.2.1 or newer, you don't need to create backups of your Tosca Commander configuration files. Tosca automatically creates backups of all exe.config files in the %COMMANDER_HOME% directory. You can find these backups in %TRICENTIS_ALLUSERS_APPDATA%\ConfigBackup<timestamp>\ToscaCommander.

2. Upgrade Tosca Commander as described below.

   We strongly recommend that you upgrade with a clean uninstall/reinstall.

3. Perform the necessary final steps of your Tosca Commander upgrade.

   You need to perform these steps on every machine that has Tosca Commander installed.

Preparatory steps

Before you perform the actual upgrade, follow the preparatory steps listed below:

1. If you have multi-user workspaces in your 2023.1 LTS project, check in all objects you want to include in your backup:

   • Find all checked out objects with the following TQL search query on the project root element:

     ->AllOwnedSubItems[CheckOutState == "CheckedOut"]

   • Right-click the search elements and select Revoke Checkout from the context menu.

2. Back up your repositories. This step is only necessary if you intend to perform your migration manually. If you migrate via Tosca Administration Console, you create your backup during the migration.

3. Back up any customizations, such as settings, engines, controls, keywords, recovery scripts, etc.

   Any settings you adjusted in %TRICENTIS_ALLUSERS_APPDATA%\Settings are maintained.

   If you upgrade to 2023.2.1 or newer, you don't need to create backups of your Tosca Commander configuration files. Tosca automatically creates backups of all exe.config files in the %COMMANDER_HOME% directory. You can find these backups in %TRICENTIS_ALLUSERS_APPDATA%\ConfigBackup<timestamp>\ToscaCommander.

4. Uninstall your customizations.

5. Remove all remaining files from the directory %COMMANDER_HOME%.

   The default path for Tricentis Tosca installations is C:\Program Files (x86)\TRICENTIS\Tosca Testsuite.

6. To avoid conflicts, Tricentis recommends that you disable specific runtime environments, such as Java and PowerBuilder.

Upgrade Tosca Commander

Tricentis strongly recommends that you upgrade through a clean uninstall/reinstall.

To do so, follow the steps below:

1. Uninstall in one of the following ways:

   • Via setup file or Windows Programs and Features.

   • In unattended mode as described in chapter "Uninstall in unattended mode".

2. Install the new version in one of the following ways:

   • Via setup file as described in chapter "Install Tricentis Tosca via setup dialog".

   • In unattended mode as described in chapter "Install Tricentis Tosca in unattended mode".

Final steps of the Tosca Commander upgrade

To finalize your upgrade, follow the steps below:

1. Install the latest versions of any existing custom AddIns. You need to do this before starting Tosca Commander for the first time.

2. Recompile customized extensions (customizations, AddIns, and AddOns) and save them to the respective directories: %TBOX_HOME% for TBox customizations and %COMMANDER_HOME% for AddOns or AddIns.

   Recompile customizations based on the Tosca Commander API with each new version (API programs, AddOns).

3. Install Firefox and Chrome plugins for XBrowser, if necessary.