Licensing

Working with OpenText Functional Testing requires a license. This topic describes the different types of OpenText Functional Testing licenses, where to view your license information, and how to install licenses.

License types

When you install OpenText Functional Testing, you select one of the following license types:

  • A permanent seat license that is specific to the computer on which it is installed.

    Note: The trial installation of OpenText Functional Testing includes a 30-day demo seat license.

  • A network-based concurrent license that can be used by multiple OpenText Functional Testing users, taken from and returned to a licensing server pool.

    If you need a demo concurrent license, contact your OpenText Functional Testing sales representative or partner.

As long as you are logged in with administrator permissions, you can change your license type at any time. For example, if you are currently working with a seat license, you can choose to connect to a concurrent license server, if one is available on your network.

Note: You can also open OpenText Functional Testing using a legacy QuickTest Professional license, but the functionality will be limited to GUI testing functionality.

For more details, see Seat vs. concurrent licenses and License editions.

For details about installing and configuring licenses, see:

Back to top

View license information

To view details about your current license:

  1. In OpenText Functional Testing, select Help > About OpenText Functional Testing.

  2. Click License.

    If at least one of your licenses is about to expire, OpenText Functional Testing displays the date of the license closest to expiration.

Back to top

AutoPass License Server

Concurrent licenses require the use of the AutoPass License Server. For supported versions of AutoPass, see the Support Matrix.

Download the installation from the ITOM Marketplace (requires login).

For more details, such as proxy settings or managing licenses and users, see the AutoPass License Server online documentation.

Back to top

See also: