Licenses
This topic describes the different license types and bundles that you can purchase in order to run tests.
Purchase a license
A OpenText Core Performance Engineering license consists of both a run type and Vuser type. You choose a protocol bundle which includes the required Vuser types.
You can purchase a combination of run types and bundles to meet your team's needs.
The following run types are available for purchase:
License | Description |
---|---|
Vusers (VU) |
|
Vuser hours (VUH) |
|
To purchase more licenses, click the Settings button on the banner and select License information. Click Purchase more licenses.
Protocol bundles
The following table describes the available bundles and their associated protocols.
For details about the supported protocol versions, see the Support Matrix.
Protocol bundle | Supported protocols | Description |
---|---|---|
GUI |
|
A GUI Vuser emulates actions on the GUI level. For example, a user clicking a button. Because the GUI has to be rendered for each virtual user, these Vusers consume significantly more processing resources. Note:
|
Web |
|
A Web Vuser emulates a user's actions at the network API level. For example, HTTP requests and responses without rendering the UI. Supported Silk Performer protocols are: Web low level, Web business transaction, HTTP Live Streaming, and XML/SOAP. For details, see Support Matrix. Note: Silk Performer scripts are only supported for on-premises load generators.
|
ERP |
|
ERP Vusers are used to test Enterprise Resource Planning systems, packaged suites of business applications. SAP GUI is only supported for on-premises load generators. Siebel Web is only supported for cloud load generators and Windows on-premises load generators. |
Legacy |
|
A Legacy Vuser is used for running legacy LRP/LRE protocol scripts. Note:
|
Dev |
|
A Dev Vuser is used for running third-party protocols, such as JMeter and Gatling. |
All protocols | All above protocols | An All protocols Vuser can be used to run any of the above Vuser types. |
Note: Beginning with version 2021.04, Flex and LeanFT scripts are no longer supported.
Virtual user hour (VUH) licenses
VUH licenses enable you to run Vusers by the hour. 1 VUH is effectively 1 Vuser running a load test for 1 hour.
Calculate the required number of VUH
As you create your test definition, the cart displays the number of VUH required to run your test.
The number of VUH is calculated by the following formula, rounding up to the nearest whole VUH:
(Vusers * Test execution time in seconds)/3600)
Note: Test execution time includes the test duration, the duration of all the ramp ups, the duration of all the tear downs, the paused time, and the actual delayed start.
Examples:
Vusers | Ramp up | Duration | Tear down | Vusers * Total test time | Total VUH |
---|---|---|---|---|---|
1 | 00:05:00 | 00:40:00 | 00:05:00 | 1 * 50 minutes | 1 |
10 | 00:10:00 | 00:40:00 | 00:10:00 | 10 * 60 minutes | 10 |
10 | 00:10:00 | 00:10:00 | 00:10:00 | 10 * 30 minutes | 5 |
Test runs with multiple scripts
When running a test with multiple scripts, use the above formula (where VUH is calculated for each script individually), and aggregate the cost of each script to get the total cost of the test run. This provides the VUH calculation at the test level.
Example:
Script name | Vusers | Ramp up | Duration | Tear down | Vusers * Total test time | Total VUH | |
---|---|---|---|---|---|---|---|
Script |
Test |
||||||
My_Script1 | 1 | 00:05:00 | 00:40:00 | 00:05:00 | 1 * 50 minutes | 1 | 16 |
My_Script2 | 10 | 00:10:00 | 00:40:00 | 00:10:00 | 10 * 60 minutes | 10 | |
My_Script3 | 10 | 00:10:00 | 00:10:00 | 00:10:00 | 10 * 30 minutes | 5 |
30-day trial license
The OpenText Core Performance Engineering 30-day trial license provides Vuser hours, which enable you to run load tests on Amazon Web Services (AWS).
The trial license includes 1,000 GUI VUHs with the following restrictions:
-
1 concurrent test limited to a 1-hour duration
-
Maximum concurrent Vusers per test run: 100 Web, 30 GUI, and 100 Dev
-
Maximum number of test runs: 10
-
Max hits/sec: 50
- Pacing: 1 second (default). You can manually configure the pacing, but you cannot set it to less than 1 second.
For details on extending a trial license, contact your account manager or sales representative.
See also: