This page describes how to go through the update process.
Before upgrade review all Release Notes. Learn about new features, improvements and bug fixes.
All Release Notes are available on the Version history page.
Determine your upgrade path with information from the table:
| TestFLO Version | Recommended upgrade path |
|---|---|
| 4.2.4 and earlier | Upgrade to 4.3.1 and use the path listed below |
| 4.3.1 to 4.4.1 | Upgrade to 4.4.2 and use the path listed below |
| 4.4.2 to 8.x.x | Upgrade to the latest version of TestFLO |
Older versions of TestFLO are available on the Version history page.
In TestFLO 5.1.0 version, the Steps field has been replaced with a new field type. Before migrating from a version lower than 5.1.0, make sure that the Steps field that appears on issue types such as Test Case Template and Test Case is the same field configured in the Global Configuration in the Steps CF option. If these fields do not match, data loss may occur.
Prior to upgrading your production environment, the best practice is to first test the upgrade using a copy of the production environment. Prepare an environment that will be a copy of the production environment and perform the upgrade according to the table from the Upgrade path.
If the upgrade in the test environment has passed positively, you can proceed with performing the upgrade on the production environment. Please determine upgrade path from table.
Learn more about migration statuses at the Upgrade reports page.
If you upgraded and the status of migration didn’t complete successfully, please contact with the support team at Customer Portal.
Have in mind that uninstalling the version and installing the previous will cause inconsistency in the TestFLO configuration. Rollback to the previous version requires a special path.
If you can’t find the answer you need in our documentation, raise a support request*.
