Various aspects of test structure and database structure may change between versions. For this reason, it is always important to follow these migration steps.
Please be aware that we highly recommend updating each version sequentially, and not skipping versions in-between.
Before installing the new version:
Follow the instructions in the installation manual and the graphical installer to install the new version. We recommend installing each new version in a new folder, whose name includes the version number. In this way, you can keep the older version until the migration is complete.
Install the update into your current Eclipse. If you use tools from the standalone version in your environment (the AUT Agent, for example), ensure that you update (install) these as well.
Once you have connected to the database, import all of the projects you exported from the older version, including the unbound modules projects (your projects still reference them, and the version can be switched in the next steps). You can use the import dialog to import multiple projects at once - we recommend ordering the projects so that any library projects (unbound modules, your own reused projects) are listed first.
Perform these steps for all projects in your database - including any projects that you yourself have defined as reused projects for your main project. It is important that all reused projects (including projects indirecty reused by directly reused projects) use the same version of their necessary projects.
As the name of the database and the workspace have changed, you should update any scripts for your continuous integration that use these properties. These can include, but not be limited to, testexec and dbtool, as well as scripts within your build management tool.
Each new version contains a new RCP Accessor. If you test RCP AUTs, ensure that the old version of these is replaced with the new version in your AUT. To do this, please follow the information in the user manual on setting up your RCP AUT for each migration. You may need to start the application with -clean to ensure that the new RCP Accessor is used.
If you have installed the AUT Agent on other machines in the network in order to run distributed tests, then you will also need to update the AUT Agent on those machines as well. You can install the AUT Agent separately as an option during installation. Bear in mind that if you use scripts to start the AUT Agent that contain the version number in them, these may also have to be updated.
Once you have successfully performed all migration steps, and have checked that your continuous integration is running smoothly, you can uninstall the old version.
If you require test results from older versions (which are not migrated with projects), then you may wish to keep the older versions and their relevant databases and dashboards.