Bug Fixes in ReadyAPI 3.63.0
In ReadyAPI 3.63.0, we fixed the following issues reported by our customers:
Note
RIA-5xxx1 represents the Jira ticket number. It helps you track back the bugs resolved in version 3.63.0.
Fixed:
An issue related to project password handling (RIA-25855).
An issue where ReadyAPI froze when importing an API definition from an unreachable private SwaggerHub On-Prem instance. ReadyAPI now displays a progress bar and a timeout message with guidance to import the definition manually from a file (RIA-24862).
An issue where, after disabling JxBrowser in vmoptions and generating an Access Token in Auth Manager, ReadyAPI displayed a blank window or an incorrect success message instead of the expected “Login Failure” (RIA-25511).
An error that occurred when importing and refactoring an API definition from SwaggerHub (RIA-25808).
A regression in version 3.62.0, where LoadUI data sources did not return data, causing test failures. This issue no longer occurs in version 3.63.0 (RIA-25986)
A bug introduced in version 3.62.0 where ReadyAPI froze when the same recorded traffic item was used twice in a row. This issue is resolved in version 3.63.0 (RIA-26014).