7.3.x

XLT 7.3.1

See here for a complete list of all changes.

XLT Framework

Result Browser: Cannot view request details

Sometimes clicking on a request entry in the result browser does not show the request details on the right, but only a blank screen. Fixed.

Ignore socket instrumentation errors in dev mode

When running test scenarios from your IDE, XLT no longer throws an exception if it cannot instrument the socket layer, but logs a warning instead.

Load Testing

Report generator crashes on ARM Macs

The Report Generator JVM may crash on ARM-based Macs due to a bug in the jline library. This library has been updated to the latest version.

XLT 7.3.0

See here for a complete list of all changes.

XLT Framework

Truly disable the JavaScript engine when not needed

Load test scenarios typically use HtmlUnit and its Web client to load, evaluate, and interact with HTML pages. The Web client is also capable of executing JavaScript code found in a page. In load tests, JavaScript execution is typically disabled to conserve CPU resources. However, the JavaScript engine has always been initialized in the Web client.

The Web client has been changed to not initialize the JavaScript engine by default. Since the engine is heavy, this reduces CPU and memory usage.

Whether the JavaScript engine is to be enabled and whether JavaScript code is executed in the page can be controlled by these properties in the configuration of your test suite:

# Whether the Web client supports JavaScript at all (the main switch).
com.xceptance.xlt.javaScriptEngineEnabled = false

# Whether JavaScript code is executed right from the start.
com.xceptance.xlt.javaScriptEnabled = false

If you need JavaScript support in your test scenarios, be sure to add both properties and set them to true. Similarly, if you don’t need JavaScript, set both properties to false.

If you want to run JavaScript code for only a portion of your test scenario(s), you would need to enable the JavaScript engine while initially disabling JavaScript execution. You could then programmatically enable and disable the execution of JavaScript code in your test scenario(s) as needed.

Load Testing

Detailed status reporting removed from Master Controller

The Master Controller no longer supports listing the status of each individual test user when printing the load test status to the console. Printing the aggregated status per scenario is now the only option.

This reduction has allowed us to drastically reduce the amount of data that needs to be transferred from the Agent Controllers to the Master Controller every five seconds. Note that backward compatibility with Agent Controllers from a previous version of XLT 7.x is maintained.

Report generator enhanced

The Report Generator has been further enhanced to run faster and use fewer resources. This includes optimizations when parsing CSV files and executing request processing rules (also known as merge rules).

List of supported data centers updated

XLT ships with ec2_admin and gce_admin, our tools for managing machine instances in the Amazon and Google clouds. These tools now support recently opened data centers (regions).

Improved “infinity” cells in comparison reports

Fixed an issue with “infinity” table cells in comparison reports. The infinity symbol is now easier to recognize and has the correct background shading when the mouse is over it.