License descriptions

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 the user. 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.

You can use any of these licenses according to your requirements:

Product licenses
  • 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 a HCL OneTest Studio 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.

  • Floating licenses for test extensions:

    For HCL OneTest Performance, in addition to the license for product usage, if you use SOA, SAP, Citrix, and Siebel test extensions, you need separate software entitlements. You can map all the entitlements to one server ID. If you have an HCL OneTest Studio license, it is enough to start using the product as well as use the above test extensions. A license is checked out from the time the product is opened by the user. The license remains checked out until the user closes the product. When the user closes the product, after 15 minutes, the license is returned to the HCL® License & Delivery portal.

Licenses for schedule, in this context, is used to refer to both VU Schedule and Rate Schedule runs
  • HCL® OneTest Studio - Virtual Users:

    These are floating licenses that are purchased in blocks of 100 virtual users each. After the run, the licenses are checked back in to the server. For example, if you have 200 HCL® OneTest Studio - Virtual Users available, you can run schedule A with 100 virtual users and schedule B with 20 virtual users, leaving 80 virtual users for other team members to use for schedule execution using the same license server. After the schedule run completes, the all the virtual users are returned to the server for others to use.

  • HCL® OneTest Studio - Virtual User Execution Capacity:

    These licenses are referred as consumption-based license. They are purchased in blocks, for example, 1000 hours. Every time you run a schedule or compound test, the number of hours are deducted from the block. Prior to schedule run, the product provides an estimate of the VU-Hours required to run the schedule. At the end of successful schedule run, the product sends a request to the HCL® License & Delivery portal to deduct the number of VU-Hours consumed. For Run Until Finished schedule run, the estimate warns that the actual number of VU-Hours to be consumed cannot be determined.

    When you run a schedule, the product first searches HCL® OneTest Studio - Virtual Users licenses. If they are unavailable or insufficient, the schedule looks for HCL® OneTest Studio - Virtual User Execution Capacity licenses. For example, suppose you are entitled to 500 HCL® OneTest Studio - Virtual Users and 1000 hours HCL® OneTest Studio - Virtual User Execution Capacity license. If a team member starts schedule A that requires 400 virtual users and another team member starts schedule B that requires 200 virtual users, schedule A picks up 400 virtual users and runs as expected. Schedule B searches 200 virtual users but does not find them. So, the duration of schedule B will beis calculated and the estimated number of hours is displayed to the user. If the user clicks OK, HCL® OneTest Studio - Virtual User Execution Capacity licenses are consumed. The calculation of Rate Schedule VU-Hours is based on 1 transaction per second being the equivalent of one virtual tester.

You can add more virtual users or change the rate of execution during the test or schedule run only if there are sufficient number of Virtual User licenses or if a sufficient number of VU-Hours are on balance in the customer's account.