DevOps Test Integrations and APIs upgrade information and requirements

Before you upgrade HCL DevOps Test Integrations and APIs (Test Integrations and APIs), review the upgrade considerations. To complete the upgrade process, you might also need to upgrade the schema of the Test Integrations and APIs project results database.

Upgrading the software

No direct upgrade paths to the latest version are supported. To upgrade Test Integrations and APIs, Test Virtualization Control Panel or Test Integrations and APIs Agent packages to the latest version, uninstall any previously installed version and install the latest version. For install instructions, see Installation of DevOps Test Integrations and APIs.

Before you upgrade the Test Integrations and APIs software

Before you upgrade an existing Test Integrations and APIs installation, read the release notes for the latest version of the software to learn about changes that might affect your use of Test Integrations and APIs, especially any new features.

Installation dependencies and considerations

The various components of the Test Integrations and APIs virtualization environment are designed to work together. In normal operation, all components (Test Integrations and APIs, Test Virtualization Control Panel, and Test Integrations and APIs Agent ) must all be at the same version. Otherwise, version-mismatch errors occur. An exception to this is Test Virtualization Control Panel, which supports older versions of agents and proxies registering with it. When you upgrade components, upgrade Test Virtualization Control Panel before you upgrade Test Integrations and APIs Agent and proxies.

Library Manager settings

Library Manager settings and most user preferences are preserved during the uninstallation or reinstallation process. During the installation of Test Integrations and APIs, run Library Manager at the end of the process and confirm that the settings are correct. Perspective and dialog layout preferences are reset.

Note: Library Manager writes some of its configuration details to a directory within the users home directory called .integrationtester, and to the Test Integrations and APIs installation directory. To ensure that Library Manager can write to the Test Integrations and APIs installation directory, the user ID that is used to install Test Integrations and APIs must be used when running Library Manager.

For information about Library Manager, see Working with Library Manager.

Verifying and upgrading the results database schema

After you upgrade Test Integrations and APIs, or uninstall an older version to move to a newer version (when the upgrade is not applicable), verify that the schema version of the Test Integrations and APIs project results database in use is correct for the new version of Test Integrations and APIs. Update the schema if required.

To know the required schema version, do either of the following actions:
  • See the release notes for the release.
  • On the menu bar, click Project > Project Settings. Open the Server Settings tab and select a database provider.
To verify and update the schema:
  • Verify the schema version in use:
    • On the menu bar, click Project > Project Settings. Select the Server Settings tab.
    • Click Test Connection
    The schema version in use must be compatible with the new version of the software as mentioned in the release notes.
  • To upgrade the schema, see Upgrading the project results database schema.
Before you roll the product out for general use, verify that the new version of Test Integrations and APIs runs your existing tests successfully.