Scripting tools

The following table lists the tools you can use to create scripts for your load tests.

For details on supported versions, see Support Matrix.

Script tool Description  Supported protocols Vuser Type
VuGen

 

VuGen is a tool to record web-based applications on the transport level.

For further details on protocols, see VuGen Protocols in the VuGen Help Center.

  • Web HTTP/HTML
  • Mobile Application - HTTP/HTML
  • Web Services
  • MQTT

Web Vuser

TruClient

TruClient is a tool for recording web-based applications as you perform your business process.

For details on supported browsers in TruClient, see Browsers in TruClient in the VuGen Help Center.

The following TruClient scripts are no longer supported:

  • Scripts created with the TruClient Firefox .xpi extension.

  • Scripts created with the TruClient standalone.

  • Scripts created with Internet Explorer.

Note: The TruClient 2.0 - Web protocol supports Google Chrome (version 128.0.6613.138) or Microsoft Edge (version 128.0.2739.79). To use a TruClient 2.0 - Web script with a Windows OPLG, you must also use the latest OPLG version. For details, see OPLG requirements.

  • TruClient - Native Mobile

  • TruClient - Mobile Web

  • TruClient - Web

  • TruClient 2.0 - Web (as a technical preview)

GUI Vuser

TruAPI
  • TruAPI is an innovative scripting tool based on node.js.
  • TruAPI enables you to create JavaScript-based Vuser scripts and provides an API for handling transactions, think time, logging, and HTTP handling.
  • TruAPI scripts can be packaged and uploaded to OpenText Core Performance Engineering and added to a test definition.

For details, see TruAPI.

  Web Vuser
JMeter

Apache JMeter is an open source performance testing tool.

  • Hits per second and Throughput graphs in test results are only available for JMeter scripts that use HTTP Request Sampler.
  • Upload a JMeter script to OpenText Core Performance Engineering in .zip format.
  • Include only one .jmx file in the root folder of the .zip file.

    If the JMeter script has dependencies on third-party plugins, you can include them in the lib/ext sub folder of the .zip file.

    If the JMeter script has dependencies on external .jar files (for example, JDBC drivers), you can include them in the lib sub folder of the .zip file.

    Other dependent files, for example, a *.csv file for parametrization, and folders can be added into the .zip file.

  • When you add a JMeter script that contains multiple enabled thread groups to a load test, OpenText Core Performance Engineering creates a duplicate script for each enabled thread group. The script name comprises <script name> (<thread group name>). For example, for a JMeter script called multi_thread_groups that contains three thread groups called apache jmeter home, nodejs doc, and nodejs blog, the following scripts are created and added to a load test: multi_thread_groups (apache jmeter home), multi_thread_groups (nodejs doc), multi_thread_groups (nodejs blog).

    Note: When reloading a JMeter script that contains multiple enabled thread groups, additions or deletions of thread groups in the script are not automatically reflected in OpenText Core Performance Engineering. This means that for thread groups that have been added to the reloaded script, new scripts are not created for load tests in OpenText Core Performance Engineering and for thread groups that have been removed from the reloaded script, scripts are not deleted from load tests in OpenText Core Performance Engineering. You must add or delete such scripts manually and until you do so, a warning is displayed for the relevant load test and the Run Test button is inactive.

  • To report transaction data, use the JMeter Transaction Controller to enclose relevant test steps.

  • If you are running this script type with on-premises load generators, you need to install a JDK (recommended 64-bit OpenJDK 11).

  • Open Model Thread Group and third-party JMeter plugins related to scheduling or threads are not supported.

Tip:

  • We recommend using the latest supported version of JMeter to create your scripts. For details on supported versions, see Support Matrix.

  • We recommend that your JMeter script only defines the steps for a single Vuser and uses a single thread group.

 

Dev Vuser

Gatling

Gatling is an open source performance testing tool.

  • OpenText Core Performance Engineering supports Gatling scripts (in Scala) that use HTTP requests.
  • Upload a Gatling script to OpenText Core Performance Engineering in .zip format.
  • If there are multiple Gatling scenarios in a simulation, only the first scenario is run.
  • If you are running this script type with on-premises load generators, you need to install JDK (recommended 64-bit OpenJDK 11).

For details, see Gatling script integration.

 

Dev Vuser

Selenium

Selenium is an open source performance testing tool.

  • OpenText Core Performance Engineering supports Selenium scripts that use the JUnit testing framework (version 4.13.2) or Mocha (version 10.4.0).
  • You can only run Selenium scripts on cloud-based load generators and Windows on-premises load generators (version 2023.03 or later).
  • If you are running Selenium scripts on a Windows on-premises load generator, you need to install JDK (64-bit OpenJDK 11+), Google Chrome, and the ChromeDriver matching the browser version.
  • Upload a Selenium script to OpenText Core Performance Engineering in .zip format (for Junit) or .tgz format (for Mocha).
  • Metrics for Throughput and Hits per Second are not supported.
  • Taking snapshots on error is not supported.

For details, see Selenium scripts.

  GUI Vuser
DevWeb

DevWeb is a new protocol offering, focusing on the HTTP (transport) level. It provides a lightweight, scalable, cross-platform solution using a brand new JavaScript SDK and engine.

For details on the DevWeb Protocol, see the LoadRunner Professional Help Center.

DevWeb Web Vuser
Silk Performer

Use Silk Performer to create scripts that can run as GUI or Web Vusers.

For details on uploading Silk Performer scripts, see Upload Silk Performer scripts.

  • Silk Web browser-driven, shown in LRC as SP Browser-driven.
  • Web low level (HTTP), shown in LRC as SP Web Basic
  • Web business transaction (HTML/HTTP), shown in LRC as SP Web Page-level
  • HTTP Live Streaming (HLS), shown in LRC as SP HLS
  • XML/SOAP, shown in LRC as SP Web Services
GUI Vuser:

SP Browser-driven

 

Web Vuser:

SP Web Basic, SP Web Page-level, SP HLS, and SP Web Services

VuGen - ERP

Use VuGen to record scripts on supported Enterprise Resource Planning (ERP) protocols.

Note: SAP GUI protocol scripts can only run on on-premises load generators.

  • SAP GUI

  • SAP - Web
  • Oracle NCA

  • Oracle - Web

  • Siebel Web

    Note:

    • Siebel Web is supported only on cloud and Windows on-premises load generators.
    • You must add the ssdtcorr.dll file to the script. For details on Siebel correlation, refer to the VuGen Help Center.
ERP Vuser
VuGen - legacy

Use VuGen to record scripts on supported legacy protocols.

Legacy protocol scripts can only run on on-premises load generators.

  • Citrix ICA

  • .NET

  • ODBC

  • RDP (Remote Desktop Protocol)

  • RTE (Remote Terminal Emulator)

  • Windows Sockets

Legacy Vuser

Localized script support

OpenText Core Performance Engineering supports scripts written in non-Latin alphabets. However, you still must use Latin characters for file and folder names.

For scripts developed prior to VuGen 12.53, do one of the following:

  • On a machine whose region locale is set to a non-Latin alphabet, open and save the script using VuGen 12.53.

  • Manually update the .usr file by adding the following setting to the General section:

    ScriptLocale=<language code>

    For details, see Language Code Identifier Reference.

Back to top