Join Wintertainment 2021 to share your stories, have fun, earn community badges, and more!

Bug Fixes in LoadComplete 4.30

Applies to LoadComplete 4.97, last modified on May 20, 2019

In LoadComplete 4.30, the following bugs reported by our customers have been fixed:

  • Fixed: Sometimes load tests did not stop at the end, and a few virtual users kept running and never finished.

  • Fixed: Recorded requests were grouped into pages incorrectly, which caused “Software caused connection abort” errors during the playback.

  • Fixed: If the request body ended with an ampersand ( & ), LoadComplete appended the equals characters ( = ) to the request body during the playback.

  • Fixed: LoadComplete could not simulate cookies for requests whose query string included http:// or https://.

  • Fixed: The built-in correlation rule for JSF/ViewState was not triggered for javax.faces.ViewState parameters.

  • Fixed: The autocorrelation rule created for the X-CSRFToken header did not work.

  • Fixed: The access violation error in the Remote Agent which prevented tests from ending properly.

  • Fixed: A misleading error message in the test log when LoadComplete could not obtain data from Remote Agent.

  • Fixed: Duplicate pages in Top 10 in the reports for load tests that used the continuous load.

  • Fixed: The Amazon Cloud initialization error on computers with .NET Framework 4.x but without .NET Framework 3.5, such as computers running Windows 8 or later.

  • Fixed: The Scenario editor did not display bodies of RIA requests whose Content-Type header contained the charset in quotes, such as application/soap+xml; charset="utf-8".

  • Fixed: Exiting LoadComplete after entering Local IP(s) in the Load Test editor resulted in a crash.

  • Fixed: "Save to Variable" was enabled for objects in RIA responses, even though not supported.

See Also

Version History

Highlight search results