 |
Important Notice for ReadyAPI Customers |
ReadyAPI has moved to SmartBear License Management. From September 2023, all licenses issued for your subscription term will be ID-based licenses by default. If you are not currently on ID-based licensing, it's time to migrate immediately. File-based licensing will no longer be supported as of October 2023. This means that technical support requests related to file-based licensing will not be accommodated. If you encounter technical issues that you're unable to resolve, it could lead to service interruption. For customers still in the process of migration, we recommend reaching out to your Account Manager to discuss your migration plan. Alternatively, you can log a support request with our Customer Care Team for assistance.
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. |
Facilitated H2 Migration
We introduced a migration tool enabling users to smoothly transition to the latest version of the H2 database. For more details, refer to H2 Migration page.
ReadyAPI Feature Enhancement
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.
Improvements
-
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.
