License editions and types

This topic includes information on all the license editions and license types for OpenText Functional Testing for Developers.

Supported license editions

The following license editions can be used to activate OpenText Functional Testing for Developers:

  • The UFT Developer standalone license.
  • UFT One
  • UFT Ultimate

  • UFT Runtime Engine - enables only running tests.

Note: The UFT Ultimate license is no longer available for purchase and is supported for existing customers only.

Back to top

License types

There are two types of licenses:

Seat licenses

A machine-specific license based on a specific locking code per computer.

The key must be entered once only, and provides one installation per key.

A computer with multiple bootable partitions may generate a different locking code for each partition.

When obtaining a seat license key, you must use the locking code for the partition on which you want to use the product.

Concurrent licenses

A license taken from a license server on a per-session basis. You must have an active network connection to install and check out commuter licenses.

Each time OpenText Functional Testing for Developers starts, it tries to connect to the License Server for an available license.

Each key provides unlimited installations. The license server regulates the number of licenses in use at any given time.

Concurrent licenses are consumed as long as the runtime engine is active, and include the following additional types:

Commuter licenses

Use a commuter license when you plan to have no access to the License Server.

With a commuter license, an active network connection is not required.

When you are finished using a commuter license, return it to make it available for other users.
Remote commuter licenses

Request a remote commuter license if you are not able to connect to the License Server to check one out.

You must send the request to another user who does have access to the License Server, who in turn must send you the required key.

Concurrent licenses are released if the runtime engine is idle beyond the defined timeout. The engine is active only when it interacts with your application using the Object Identification Center (OIC) or while running tests. You can configure the timeout length or cancel the timeout completely in the runtime engine settings. For details, see Customize the runtime engine settings.

Both commuter and remote commuter licenses expire at 23:59 of the expiration day. If you do not check your commuter license in before it expires, OpenText Functional Testing for Developers automatically reverts to the previous license state.

Parallel tests and license consumption

When using a seat license, a single license is consumed and up to four test operations can run in parallel.

When using concurrent licenses, more than one license can be consumed at a time:

  • Four parallel test operations can run for each license consumed.
  • In the runtime engine settings, define the maximum number of licenses this engine instance can consume.
  • When running parallel tests, licenses are gradually consumed and released as needed.

Back to top

See also: