Differences Between Supported Browsers

You may encounter differences in the test results and in the test run when replaying on a browser different than the one you recorded the script on.

Note:  

  • TruClient Browser has replaced use of the Firefox browser. Scripts that are configured to run with Firefox will automatically be run by TruClient Browser.
  • TruClient Lite supports only the Chrome browser. For details, see TruClient Lite.

The following table describes features that have limitations in one or more of the browsers.

Item/Feature

Chromium

Internet Explorer

TruClient Browser

Browser description

Chromium is an open-source Web browser project from which Google Chrome draws it source code.

Chromium source code on Github

Browser developed for Microsoft Windows.

TruClient browser developed for Windows, based on Mozilla technology.

Browser version

Chromium 63

Internet Explorer 10, 11

Equivalent to Firefox version 58.0.2

(For TruClient - Native Mobile scripts: Equivalent to Firefox version 50.0)

Modify browser preferences

(see Modify Browser Preferences)

SSL Connections

Report the number of open SSL connections.

Chromium does not expose the number of open SSL connections.

TruClient Browser does not expose the number of open SSL connections.

Responsive design based application

(see Responsive Design Based Applications)

Record snapshots

Snapshots generated during the recording of a script.

Modem speed emulation

 

Legend

Supported

Not supported

Partially supported

Note: All browsers support:

  • TruClient Coded, which enables converting TruClient actions to code. For details, see Convert TruClient Actions to Code.

  • Network Virtualization reports integration, which provides information about how your application performs over various networks. See NV Insights Report.

  • Network Virtualization emulation integration, which enables configuring a WAN profile on the group in the Controller.

  • Diagnostics integration, which enables server side diagnostics for J2EE and .Net applications.

  • Automatically or manually attaching the client certificate to the script folder when recording a script.

  • IP spoofing, which enables mimicking multiple IP addresses from the same load generator.

  • Verifying the content of a PDF document during script execution.

Back to top

See also: