- Getting Started
- Demo backup
- User's guide
- Projects' organization
- Test design
- Organizing tests
- Test planning
- Test execution
- Reporting and tracking
- Import/Export TCT
- Export test issues
- Issue search dialog
- TestFLO menu
- Admin's guide
- Project configuration
- TestFLO settings
- Test Automation configuration
- TestFLO Permissions
- Custom fields
- Advanced workflow configuration
- Panel Filter Result
- Upgrade reports
- Upgrade guide
- REST API
- Configuration Manager for Jira
This page describes how to go through the update process.
Preparing to upgrade
1. Release Notes
Before upgrade review all Release Notes. Learn about new features, improvements and bug fixes. Below you can find Release Notes for:
- TestFLO 7.x.x
- TestFLO 6.x.x
- TestFLO 5.4.x
- TestFLO 5.3.x
- TestFLO 5.2.x
- TestFLO 5.1.x
- TestFLO up to 5.0.5
2. Upgrade path
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.
3. Upgrade in a test environment
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*.
*Include as much information as possible to help our support team resolve your issue faster.