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.
ReadyAPI 3.51.0 includes a few changes compared to the previous product version – ReadyAPI 3.50.0. For information on the changes made to other versions, see Version History.
Note
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.
We introduced a migration tool enabling users to smoothly transition to the latest version of the H2 database. For more details, refer to the H2 Migration page.
We added the capability to bulk delete custom properties. Previously, users could only delete one custom property at a time. This enhancement enables users to select multiple items and perform a bulk action.
A warning is now displayed when deleting methods in ReadyAPI. It alerts users if the method they’re deleting is being used by any test steps.
Users can no longer delete a request if it’s used by any existing test step. To delete such a request, it is required to modify test steps.
In instances where ReadyAPI was unable to import a test step due to a missing request, a warning was previously shown separately for each test step. We have introduced an "OK to all" function, allowing users to close just one popup window for potentially many with larger projects.
Note
We have identified some use cases where ReadyAPI Windows users required broader character encoding through UTF-8. To set encoding to UTF-8, you need to make one configuration change to <readyapi-installation-folder>\bin\ReadyAPI.vmoptions. Insert a new line at the end and add -Dfile.encoding=UTF-8. Save, close the file, and open ReadyAPI. For additional details on setting the encoding to UTF-8, refer to this page.
Please see here for a list of fixes included in this patch.