License editions and types

This topic includes information on all the license editions and license types for UFT Developer.

Supported license editions

The following license editions can be used to activate UFT Developer:

UFT Developer:

  • The UFT Developer standalone license.

UFT:

  • UFT One
  • UFT Ultimate

  • UFT Runtime License - enables test execution only.

Back to top

UFT Developer license types

There are two types of UFT Developer 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 UFT Developer.

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 UFT Developer 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 UFT Developer 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, you can use UFT Developer without an active network connection.

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 UFT Developer runtime engine is idle beyond the defined timeout. The engine is active only when it interacts with your application via the Object Identification Center (OIC) or while running tests. You can configure the timeout length or cancel the timeout completely in UFT Developer’s engine runtime settings. For details, see Customize UFT Developer 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, UFT Developer automatically reverts to the previous license state.

Parallel tests and license consumption

When using a seat license, UFT Developer consumes a single license and can run up to four test operations in parallel.

When using concurrent licenses, UFT Developer can consume more than one license at a time:

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

Back to top

See also: