This topic describes the changes made to LoadComplete 3.20. For information on the changes made to other versions of the product, see Version History.
Windows 10 support. Now, you can record and run load tests on Microsoft Windows 10 (both 32-bit and 64-bit versions).
Edge support. With LoadComplete 3.2, you can record scenarios, including HTTPS scenarios, in the Microsoft Edge web browser.
HTML5 and WebSocket support. You can record scenarios and run load tests for HTML5 web applications. As part of this support, we added the possibility of recording and playing back WebSocket traffic. LoadComplete automatically detects WebSocket connections and records data transferred over these connections. See Support for HTML5 Applications and Support for WebSocket Protocol (HTML5).
Load balancer support. With LoadComplete 3.2, you can run load tests in a load-balanced environment. The product includes new special settings that let you configure IP aliasing to make the tested load balancer treat simulated virtual users as distinct clients. See Load Testing in Load-Balanced Environments.
Extended authentication support. LoadComplete now supports Microsoft Sharepoint Forms Based Authentication (FBA). To use this authentication type in your tests, just record the actions you want to simulate. FBA is handled in the same way as other Basic authentication types.
The User-Agent list now includes strings for the most recent versions of popular modern desktop and mobile browsers:
Proxy recording in proxy mode. By default, LoadComplete uses proxy mode for traffic recording. In earlier versions, this mode does not record traffic if your computer is connected to the tested web server via proxy. Version 3.2 removes this limitation. Now, the proxy mode supports recording requests and responses that come through a third-party proxy.
You can set the allowed number of errors for your load tests and individual virtual users. LoadComplete will stop the test run or virtual users simulation when the number of errors reaches the specified limit.
Black and white lists of servers and applications. In addition to the list of applications and servers to be ignored during the scenario recording, LoadComplete 3.2 also includes a list of applications and servers, traffic from which you want to include into the recorded scenarios. If this list contains any values, LoadComplete will record traffic from the specified servers and applications only, and will ignore traffic from other applications and servers. See Excluding Undesirable Traffic.
New settings that control the number of errors. In the load test editor, you can now set the allowed number of errors for virtual user groups or for the entire load test. LoadComplete will stop the test run or virtual user simulation, when the number of logged errors reaches the specified limit. See Virtual Users Table and Stop on Error Settings.
When comparing test results, you can explicitly set a baseline report and a report to compare with the baseline report. See Comparing Two Result Sets.
In version 3.2, LoadComplete supports only one pagination mode: it always inserts pages detected automatically and custom pages you create manually into scenarios. In earlier versions, this pagination mode was known as Hybrid.
Version 3.2 includes a new Correlate parameters automatically option that you can use to enable or disable correlation of dynamic parameters in requests and responses. By default, the option is on (auto-correction is enabled).
Using new items of the context menu of the request tree, you can now quickly exclude certain requests from simulation. See Enabling and Disabling Operations.
Using the new commands of the Hosts table’s context menu, you can easily disable requests to multiple servers in your scenario.
You can rename pages and requests directly in the requests tree of the Scenario editor.
Remote Agent is now always installed and run as a service (earlier, it could run as an application).
LoadComplete now registers the bundled Remote Agent as a service and uses this Remote Agent for running tests on the local computer. This means that the Master and LocalHost stations now refer to the same Remote Agent and that they cannot be used simultaneously in the same test. In other respects, you use this local Remote Agent instance in your distributed tests in the same way you use Remote Agent instances running on other computers.
Remote Agent cannot be installed on a computer, where LoadComplete is installed.
Options that affect scenario recording and test running have been rearranged into the following groups:
Network - Options that affect the way LoadComplete connects to the network and the protocols it uses to establish secure connections during the scenario recording and test running.
Recording - Options that affect scenario recording.
Simulating - Options that affect the way LoadComplete simulates the recorded traffic, and store the requests and responses contents.
The Load Test editor’s toolbar now includes new commands that help you copy and paste records of the Virtual Users table easier.
Changes in the Create New Project wizard:
In earlier versions, the wizard had a page where you could only specify two servers for monitoring and could not add counters. In version 3.2, the wizard does not have this page anymore. It contains a button that opens the Counter wizard, where you can create as many counters for servers as needed.
You can no longer set the Quality of Service criteria for the new project in the wizard. If needed, you can set them in the Project editor after the project is created.
We have fixed a number of bugs reported by our customers.
Integration with source control systems has been dropped. You can still store your LoadComplete projects in source control systems, but you have to use external clients for this.
Windows XP and Windows Server 2003 are no longer supported for scenario recording and load simulation.
When installing LoadComplete 3 on Windows 10, you may see the following error:
Sentinel Runtime Environment Installer failed with the following error: file processing error.
You can ignore this error. It affects neither the installation process, nor the functioning of LoadComplete.
However, you may also see errors when uninstalling LoadComplete 3. If so, we recommend that after uninstalling LoadComplete you reinstall all the products on this computer that use the Sentinel HASP licensing system. (Uninstall all of them first, then install them again.)