Known issues

This section displays the known issues when working with TruClient.

Note: For notes and limitations on LoadRunner Professional, see Known issues in the LoadRunner Professional Help Center.

Windows 10, Windows 11, and Windows Server 2016

Where applicable, we recommend using a Chromium or TruClient Browser on Windows 10, Windows 11, and Windows 2016.

Back to top

Permissions

  • The TruClient browser for Internet Explorer requires Read access to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer registry key and Write access to the HKEY_CURRENT_USER\SOFTWARE\Micro Focus\TruClient registry key.

    Resolution: Run VuGen or TruClient Standalone as an administrator.

  • When recording and replaying TruClient - Web scripts (and recording Web protocol scripts) on a Window Server operating system, it is recommended to disable Internet Explorer Enhanced Security Configuration (IE ESC).

    Resolution: In Windows 2012 R2, 2016, select Server Manager > Local Server > Internet Explorer Enhanced Security Configuration.

Back to top

Chromium and TruClient Browser

  • If you run a TruClient script in Controller, incorrect time measurements (0 in most cases) are displayed in the Analysis reports for Connection Time, DNS Time, Network Time, Server Time, and SSL per second.

  • If you run a TruClient script in Controller, the Connections graph is always empty.

  • Recording snapshots are not available.

  • Execution time of TruClient scripts replayed with TruClient Browser or Chromium appears slower than those replayed on Internet Explorer (or on TruClient Firefox in previous versions). This is a result of the TruClient instrumentation on TruClient Browser and Chromium. This primarily impacts the throughput generated by the Vusers.

    Tip: When replaying TruClient scripts with TruClient Browser or Chromium, run additional TruClient Vusers on more load generator machines than you would with Internet Explorer.

  • If you add a step for the authentication dialogue, you cannot use JavaScript API for the username, password, or domain. You can only use plain or parameter values.

Back to top

Chromium Browser

  • When there are multiple certificates available for use to visit a web page, Chromium can only pick up the first certificate.

  • When recording a script, the top level frame navigation event is omitted due to performance optimization. As a result, the Go Back or Go Forward step is not recorded automatically.

    Resolution: Manually add a Go Back a page or Go Forward a page step.

  • The ''Wait for File Download' step does not support the file types that are treated as dangerous by the browser. The types include but are not limited to .exe, .dll, .msi, .xml, .xsl, .js, .bat, .chm, .cmd, .jar, and .ini. The download of such files is blocked by the following prompt.

    "This type of file can harm your computer. Do you want to keep xxx anyway?"

Back to top

TruClient Browser

Due to changes in Mozilla technology, TruClient Browser now consumes significantly higher resources than other browsers (TruClient Browser is based on Firefox). As a result, we recommend using the default Chromium browser instead.

Back to top

Internet Explorer browser

  • In Windows 11, you cannot set a proxy address for IE browser by using the TC.SetProxy(option, settings) function or by changing proxy settings in General Settings > Browser Settings or Runtime Settings. Only system proxy is supported.

  • IE browser does not support browser cache in service mode. For workarounds, see Running TruClient as a service.

  • IE browser does not support Speed Simulation (defined in Runtime Settings > Network > Speed Simulation).

    Resolution: Use Network Virtualization instead. For details, see Network Virtualization.

  • IE does not support DOMStorage and AppCache cache separation for virtual users.

  • IP spoofing (running multiple Vusers with different IPs) is not supported when running a load test with the IE browser.
  • IE browser does not support the "Wait for File Download" step.

Back to top

All supported browsers

Due to dependency on browser vendors, TruClient's footprint might be affected by internal architectural changes to the browsers.

In addition, long runs may consume more memory.

To reduce the overall memory used, we recommend that you enable Simulate a new user for each iteration (found in General Settings > Runtime Settings > Replay).

Back to top

Custom configurations

If you added custom configurations to the pref.js or user.js files for TruClient scripts recorded with LoadRunner 11.52, you need to re-add them to the LoadRunner 12.xx script files.

Tip: It is recommended to back up existing files before you begin editing scripts with custom configurations in LoadRunner 12.xx.

Back to top

Step arguments

When using the Enter credential step, if you want to use dynamic values for the username, password, or domain, the step fails in most cases when using the JavaScript argument type.

Resolution: Use the Parameter argument type instead. For details, see TruClient step arguments.

Back to top

Deprecated features

Removed features

TruClient Lite was discontinued. We recommend using TruClient in VuGen instead. For more information, see the VuGen Help Center (select the version you are working with).

Planned future removal of functionality

Support will be discontinued for the following in an upcoming TruClient version:

Back to top

TruClient - UFT Mobile integration

The following are additional limitations when using TruClient - UFT Mobile integration:

  • A vertical scrollbar is not displayed in the UFTM wizard.

    Workaround: Use the arrow keys or mouse wheel to scroll.

  • To generate transaction response time information for your test, you must specify a packaged version of your native app and define Object Exists end events in your TruClient script steps.

  • Transactions are not supported for UFT Mobile configuration steps. Transactions are supported for all standard TruClient actions.

  • In certain WebView steps, the " _blank" attribute is not supported. This applies to the rare case where the link is set to target="_blank", or when using the API AUT.window.open with target="_blank".

See also: