Why Upgrade Matters
Tricentis releases one Short Term Support (STS) and one Long Term Support (LTS) version of Tosca Commander updates annually. While upgrading every time is not mandatory, organizations eventually face critical triggers: end of life support, new features, bug fixes, and performance improvements. Staying on outdated versions increases operational risk and limits automation capabilities.
Enterprises view upgrades as a governance exercise that ensure business continuity to mitigate risk, ensure seamless test execution and repository integrity, all within the planned delivery timelines.
Pre-Upgrade Essentials
Before starting, confirm these steps:
- Staging Environment: Validate the new version in a controlled setup with a dedicated test repository. Mixing versions in one repository can corrupt data because Tosca 2025.1 uses different unique ID logic.
- Downtime Planning: Freeze repository activity, check in all changes, and suspend automated runs.
- Migration Assessment: Determine if schema or XEngine migrations are required. For upgrades from 2024.1 or later, these steps are unnecessary. Older versions require intermediate upgrades.
Three-Phase Upgrade Framework
1. Backup
Configuration and workspace files e.g. %COMMANDER_HOME%
Custom engines, controls, keywords, and AddOns (SETS)
Test repositories and integration settings
2. Upgrade Execution
Uninstall the old Tosca Server and Commander via setup or unattended mode
Clean remaining directories in program files, program data e.g. %COMMANDER_HOME%
Install Tosca 2025.1 Commander and Server using installer or silent deployment