Features Added to ReadyAPI 3.52.0
Important Notice for ReadyAPI Customers
Starting from ReadyAPI 3.62.0, VirtServer 3.29.0, and TestEngine 1.34.0, SmartBear Product Family has fully deprecated file-based licenses and transitioned to the ID-based SmartBear License Management (SLM) system. Any customers still using file-based licenses must complete their migration to SLM by September 30, 2025.
From October 1, 2025, existing and activated file-based licenses will continue to work for some time. However, SmartBear will no longer generate new file-based licenses or support activation and deactivation of file-based licenses in ReadyAPI, VirtServer, or TestEngine. All new and updated licenses are now issued in SLM only.
All technical support for file-based licenses has now ceased, and SmartBear no longer maintains the file-based licensing system. Any access or service issues will result in service disruptions that we will not be able to restore.
If you have not completed the process of migrating, contact your Account Manager or SmartBear representative today. Our teams are ready to assist with smooth transition strategies. For additional support, log a request with our SmartBear Support, who are standing by to help.
For further information and timelines, refer to the File-Based License End-of-Life Policy 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.
PKCE flow for OIDC
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.
ReadyAPI Feature Enhancement
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.
Improvements
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.
General Updates
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.