Upgrade to 2024.2 LTS

This section of our manual is all about how to upgrade to Tricentis Tosca 2024.2. It explains all steps you need to take to perform the upgrade. If we don't mention a particular component, that means you don't have to do anything for it.

Please note that instructions only apply to upgrades from these versions:

  • Versions that are supported around the time of the 2024.2 release: 2024.1 and 2023.2

  • Versions that are in extended support around the time of the 2024.2 release: 2023.1, 16.0, 15.2, and 15.0.

For information on how to organize upgrades for end-of-life versions, check out "Upgrade end-of-life versions".

Prepare a staging environment

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

Setting up Tosca in staging is similar to the upgrade process. This helps you identify potential issues you might encounter during the actual upgrade. Plus, if you plan to change infrastructure as part of your upgrade, you can take this opportunity to test the new version of Tosca in your new infrastructure.

Use a dedicated test database as a test repository. Don't use your production repository, because different versions of Tosca shouldn't commit to the same repository.

Schedule downtime

If your tests in the staging environment went well, it's time to upgrade in production. To make this process as smooth and issue-free as possible, we recommend that you schedule some downtime. 

Ideally, avoid changes to the repository during the upgrade. For example:

  • Ask your testers to finish all open tasks, check in their changes, and close their workspaces.

  • Suspend scheduled test runs.

Perform your upgrade

Once everything's ready, let's upgrade Tricentis Tosca:

  1. Upgrade Tosca Commander.

  2. Upgrade other Tricentis Tosca features, if you use them: 

  3. Check out our change logs, which describe changes in functionality that you need to be aware of. You may need to perform additional steps after the upgrade.