Licenses for DevOps Test Integrations and APIs and DevOps Test Virtualization

You can find information about the licenses that you can purchase to use HCL DevOps Test Integrations and APIs (Test Integrations and APIs) and HCL DevOps Test Virtualization (Test Virtualization).

Test Integrations and APIs licensing

The usage of base product and test extensions are enabled by floating licenses, whereas schedule runs can be enabled by either floating or consumption-based licenses. With floating licenses, multiple users can use the product; however, the total number of concurrent users cannot exceed the number of floating licenses you purchase.

When a software order is placed and acknowledged, a software entitlement is created for you. You can then create devices and map the software entitlement with the devices. Every device is associated to a server ID. This server ID is applied in the product. Multiple software entitlements can be created based on the requirements.

Floating license to use the product

To use the product, you need a floating license that is mapped to the product or you can also use an HCL DevOps Test Workbench (Test Workbench) floating license.

A floating license is checked out when you use the product and is returned to HCL® License & Delivery portal when the license is not used for 15 minutes.

A single license enables you to run the following assets in Test Integrations and APIs:

Tests or test Suites
Stubs run in a limited capacity with one transaction per second and for a maximum duration of five minutes.

Note: If you want to run stubs in Test Integrations and APIs or by using an Test Integrations and APIs Agent, you must purchase the Test Virtualization Concurrent Virtual Services licenses.

You must set up licensing before you can use Test Integrations and APIs, see Setting up licenses for DevOps Test Integrations and APIs.

Test Virtualization Concurrent Virtual Services licensing

Test Virtualization 10.2.0 or later, supports Concurrent Virtual Services licensing. With this form of licensing, each concurrent virtual service consumes a single license.

A single Concurrent Virtual Services license is consumed for each stub that runs under the following circumstances:

When you run stubs in a Docker container or use the command line to run stubs.
When you run tests that contain stubs in a Docker container or use the command line to run such tests.
When you run test suites that contain stubs in a Docker container or use the command line to run such test suites.

Each stub that runs under a concurrent virtual service license is limited to 10 transactions per second.

The Concurrent Virtual Services license is returned to the license pool in the following conditions:

When the running stub is stopped.
When the container is terminated if it encounters an error, the license is returned within 15 minutes from termination of the container.

This license requires that a FlexNet Cloud License Server is configured with valid Concurrent Virtual Services licenses.

If you run any resource other than a stub in a Docker container a single Test Integrations and APIs license is acquired for the duration of the run and returned once the run is completed.

For example, if you run a test or test suite that contains a stub, the following licenses are consumed:

A single Test Integrations and APIs license is consumed to run the test or test suite.
A single Concurrent Virtual Services license is consumed to run the stub.

You must set up licensing before you can run virtual services, see Setting up licenses for DevOps Test Virtualization.