This topic describes the changes made to LoadComplete 4.61. For information on the changes made to other versions of the product, see Version History.
Smarter handling of recording issues. Depending on the LoadComplete settings and recording conditions, you can get empty scenarios after recording. This can happen, for example, if the recorder filters out all the recorded requests according to the LoadComplete settings. Another possible cause is that you used some other browser for recording, not the one you selected in the Recording dialog box.
Earlier versions of LoadComplete displayed one warning message for this problem. The new version analyzes the situation thoroughly and provides more specific hints that help you find the cause of the problem faster.
Support for recent Chrome versions and Windows security updates. LoadComplete experienced issues with traffic recording in Chrome on computers with recent Windows updates. Version 4.61 fixes these issues.
A new setting for excluding problematic requests from simulation. LoadComplete 4.61 includes a new Recording setting – Disable requests with 4xx and 5xx responses. If it is enabled, the recorder automatically disables requests with 4xx and 5xx HTTP response codes in the recorded traffic. These response codes indicate client or server errors. The new setting helps you record user scenarios that are ready for playback right after recording (without any changes).
Better logging in distributed tests. Earlier versions of LoadComplete failed to post any results to the test log if a communication error occurred when interacting with Remote Agents. Now, it saves the logs of those Remote Agent instances that work properly till the end of the test run.
Export of failed log items. In earlier versions of the product, the “Export ...” commands on the test log toolbar exported all the log items. Now, you can export only errors and warnings, and skip information on successfully simulated requests.
Smarter traffic simulation. LoadComplete now tries to re-establish the connection that was reset by the remote server.
A number of bugs reported by our customers have been fixed.