Xceptance has released version 4.5.6 of its load testing and test automation product Xceptance LoadTest. This is a bug fix release.
- Fix: When (re-)loading a test suite, Script Developer checks if the scripts need to be migrated to a newer script version and updates the scripts if necessary. However, this did not happen for Java modules, so when reloading an already migrated test suite, Script Developer prompted for migration once again.
- Fix: In the load test report, the custom value charts represented all the values measured for a certain second as a simple average value only, but not as a min/max value. This way, spikes were hardly visible and the shown value range in the charts did not match the minimum/maximum values in the data table.
- Fix: Fix: When running client performance tests via Firefox with script test cases that had been exported to Java, client performance data was gathered successfully, but wasn’t reported to Graphite.
- Fix: It could happen that an agent controller failed to install a freshly uploaded test suite if there were multiple XLT installations on the same machine and their agent controllers were all active and in use. In such a scenario, one agent controller could overwrite/delete the test suite archive of another agent controller as all agent controllers used the same file name in the tmp directory.
- Fix: In case an agent controller had problems installing a test suite after an upload operation, the processing status was not updated correctly so the master controller waited forever for the agent controller to finish.
- Fix: The communication between master and agent controllers is protected by a password. If the configured password contains non-ASCII characters, then parts of the communication (upload and download, that is) could fail depending on the platform’s default character encoding.
- Improvement: When replaying script test cases, the framework will now automatically retry a script command in case the target element was reported as “stale” because of asynchronous page updates. This approach greatly simplifies scripting and makes the scripts more robust.
- Improvement: In case a server is more restrictive regarding the supported encryption protocols, XLT may fail to establish a secure connection. This is because the JRE limits the set of enabled protocols to SSLv3 and TLSv1 by default. Luckily, the JRE supports TLSv1.1 and TLSv1.2 as well. To reconfigure the set of enabled protocols, use the new setting com.xceptance.xlt.ssl.protocols = TLSv1, TLSv1.1, TLSv1.2.
- Fix: In case an XML script test case fails when being replayed via the XLT framework, the corresponding script stack trace contains the line number of the offending command. However, this line number was not always correct.
Download and More Information
You can find more information about this release at https://lab.xceptance.de/releases/xlt/latest/releasenotes.html. Download the latest release from our homepage: https://www.xceptance.com/de/xlt/download.html
As always, this update is free of charge for every user. You can use XLT freely for your daily automation work, regression testing, and performance validation.