3.4 Migrating to newer versions of Jubula

If a new version of Jubula uses a new Database scheme, you will be informed of this when attempting to connect to the Database .

If this is the case, please follow these instructions:

  1. From the old version of Jubula , export and backup all the Projects from the database.
    \includegraphics[height=2cm]{lightbulb} Make sure you also export and back up any library Projects used in your tests, e.g. the unbound modules Projects .
  2. Back up any extensions you have made to Jubula : any customized plugins and implementation classes you have written.
  3. Export your Database preferences from the workspace 3.22.9.
  4. Uninstall the old version of Jubula .
  5. Clear (empty) the Database schema for all necessary Jubula users. You can do this via a database administration tool which will let you carry out the action Drop Tables.
  6. Install the new version of Jubula .
    \includegraphics[height=2cm]{lightbulb} If you have AUT Agents running on other machines, be sure to install the new version of the AUT Agent there too.
  7. Add any extension plugins you backed up from the old version.
  8. Import your Database preferences into Jubula .
    \includegraphics[height=2cm]{lightbulb} If you are testing RCP AUT's , bear in mind that you will need to remove the old version of the RCP Remote Control plugin from your application and insert the new version in its place. We also recommend starting your application with "-clean" to ensure that the old RCP Remote Remote Control plugin is no longer used.
  9. Start Jubula .

\includegraphics[height=2cm]{lightbulb} You will also need to follow the instructions on updating the version of the unbound modules projects you use 3.5.3.1
.



Copyright BREDEX GmbH 2012. Made available under the Eclipse Public License v1.0.