Bug Fixes in ReadyAPI 3.62.0

A bug in the MQTT Plugin where the New Connection window did not open and threw an exception. Updated the plugin to the latest ReadyAPI version. Preparing to update MQTT to v5.0 in the Q4 release.

A regression bug in TestRunner, introduced in version 3.59.0, that caused the system to mark passing assertions as failures in the GUI (behavior differed from 3.42.2). The issue also generated duplicate error messages in the logs. The fix ensures TestRunner correctly recognizes passing assertions and logs each error message only once (RIA-25227).

An issue where enabling "Preferences > Other > ReadyAPI > Complete error logs > Logs complete messages to reports on error" caused the application to keep detailed logs for both failed and successful test runs in memory. This led to OutOfMemoryException errors. The issue is now resolved (RIA-23666).

An issue in ReadyAPI where the system may not always read and correctly assign variables that the user sets in a load test’s Setup Script, such as context.expected = "EXPECTED_STRING". The fix ensures ReadyAPI consistently reads and applies the variable as expected (RIA-22999).

An issue where ReadyAPI sometimes froze during the execution of a test case or test suite. This behavior affects running Test Suites, Test Cases, REST test steps, SOAP test steps. When you set the "Add System Headers" project property to true, ReadyAPI performs a host check on the first run of the entire test suite or test case, causing slower startup. If you set this property at a test suite level, only that test suite and its test cases perform the host check on the first run. The same logic applies when set at the test case level. Setting the property to false skips the host check, preventing the application from freezing during the first run of a test suite or test case (RIA-25401).