Important Notice for ReadyAPI Customers
ReadyAPI has fully transitioned to the ID-based SmartBear License Management (SLM) system. We are now moving into the final phase of deprecation of file-based licenses. Customers still using file-based licensing need to plan for migration to SLM before September 30, 2025.
If you are still in the process of migrating or have yet to start, contact your Account Manager or SmartBear representative today. Our teams are ready to assist with smooth transition strategies. For additional support, please log a request with our Customer Care Team, who are standing by to help.
For further information and timelines, please refer to this page.
Note
We're updating ReadyAPI documentation to better serve you. Help prioritize enhancements by taking our quick 8-question survey. Your feedback is essential in fine-tuning for a smoother experience. Thank you for participating!
ReadyAPI 3.52.0 includes a few changes compared to the previous product version – ReadyAPI 3.51.0. For information on the changes made to other versions, see Version History.
SmartBear License Management's license authentication and request flows were revised in November 2023. Authentication using the username and password is no longer supported for test execution via TestRunners, Jenkins or Azure plugins, and SmartBear-hosted licenses. Username and password are limited to on-prem-hosted licenses only. Access Key is the required option for authentication if using SmartBear-hosted licenses headlessly.
SLM Onpremise 2.0 now supports OIDC. When you configure OIDC and request a license from the SLM On-premise server, your login will undergo a PKCE flow. Remember, this requires SLM Onpremise License Server 2.0 with OIDC configured.
Support for Client Credentials in TestRunners and Plugins will come in future releases.
We added PKCE flow for users authenticating to VirtServer when VirtServer is configured for OIDC. This feature will be compatible with VirtServer 3.20.0 or later (3.20.0 releases at the end of April 2024).
We added vmoptions parameter that disables basic auth for Auth Profile verification which caused some issues during PKCE login.
Some special characters like {,} will be replaced in automatically generated test case names based on request URLs due to compatibility issues with Groovy scripts.
By default,
sniHostCheckis now set tofalseto prevent compatibility issues with the latest version of the Jetty library.When selecting tags for custom arguments in TestRunner, you can now choose how to combine the tags using OR or AND operators.
We added a new vmoptions parameter to allow you to disable automatic product updates, product update notifications, and the option to check for updates.
We removed deprecated Windows .dll files that were used by the installer.
A warning will now appear when you close the script editor without saving changes.
We removed Optimizely, previously used for testing new features. Now, ReadyAPI startup should improve by approx. 10 seconds.
We updated TestEngine license location.
We updated the JDK to version 17.0.10.
ReadyAPI 3.52.0 includes newer versions of some libraries that version 3.51.0 used. If your scripts refer to classes from these libraries, you might need to update the scripts.
Note
It is recommended to skip version 3.52.0 if you're encountering the ReadyAPI freeze issue (RIA-21011) while retrieving the OAuth 2.0 token. The solution for this problem is not included in this version. Please wait for the next release for a fix.
Please see here for a list of fixes included in this patch.