 |
Important Notice for ReadyAPI Customers |
ReadyAPI has fully transitioned to the ID-based SmartBear License Management (SLM) system. We strongly encourage users still utilizing file-based licensing, including key-based and ProtectionLS floating licenses, to migrate before the September 1, 2024 deadline to avoid commercial impact. Please be aware that support for file-based licensing has ended and technical support is no longer available, which may lead to unresolved technical issues.
If you cannot migrate from file-based licensing before September 1, 2024, it is crucial to contact your SmartBear representative immediately to align with our deprecation plans and avoid disruptions. Additionally, retaining file-based licenses for any solution expansions or renewals after this date will result in a service charge of up to 30% of the renewal or expansion invoice value to cover the extension costs. To avoid these charges, please initiate your migration now.
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.
|
Upcoming Enhancements to ReadyAPI Documentation Experience |
In the coming weeks, we will be updating the ReadyAPI product documentation to provide a more streamlined and consistent user experience across our entire product portfolio. While retaining all essential information, the updated documentation will feature a fresh design that makes it easier to navigate, read, and utilize.
The new documentation experience will offer several key benefits:
- Enhanced panel structure and navigation: A reorganized layout for quicker, more intuitive access to content.
- Improved search capabilities: Find information faster with a more powerful and precise search function.
- Better usability: Simplified viewing and expanding of sections, making it easier to locate and understand relevant details.
|
Git Pull Issue with Local Commits in ReadyAPI |
We identified an issue in ReadyAPI 3.57.0 where pulling changes from the remote repository fails if a local commit exists. The expected behavior is for Git to merge the changes or prompt for conflict resolution. This issue disrupts workflow and prevents synchronization. SmartBear is actively addressing this, and a fix will be included in the January release. If you use git to pull changes into local ReadyAPI, we recommend you stay on your current version of ReadyAPI until we release the fix in January 2025.
ReadyAPI 3.57.0 includes a few changes compared to the previous product version – ReadyAPI 3.56.0. For information on the changes made to other versions, see Version History.
|
SmartBear has made a number of library updates in ReadyAPI 3.57.0 which will require a TestEngine update to 1.32.0 for compatibility. TestEngine is currently incompatible with projects created in ReadyAPI 3.57.0. TestEngine 1.32.0 will support the updates and ReadyAPI 3.57.0 and will release the week of January 15th, 2025. We advise any customers planning to execute ReadyAPI projects in TestEngine to hold off on updating to ReadyAPI 3.57.0 until they can also update TestEngine in January. |
Conditional Match Enhancements
-
Progress Tracking for Conditional Match Creation: ReadyAPI now shows a progress status when generating a Conditional Match structure from recorded traffic. A loading animation and numerical progress indicator are displayed until all data is saved.
Virtual Service Enhancements
-
Route to Live for Virtual Services: We have introduced a new routing option in Virtual Service, called Route to Live. This option first routes a request to the virtual service. If the virtual service does not have the request configured or cannot generate a match, the request is automatically routed to the live system. This setting controls the runtime behavior of the virtual service, determining whether the response comes from the virtual service or the live backend.
-
In the Route to Live execution mode, the request is initially routed to the virtual service.
-
If the virtual service has this request configured, the response mapped for this request will be returned by the virtual service.
-
If the virtual service does not have this request configured, the request is then automatically routed to the live backend for fetching the live response.
For more information, visit this page.
-
-
Merging Virtual Services: You can now merge two virtual services when moving or copying VirtActions. If a Conditional Match is detected during the operation, ReadyAPI performs additional validation to check for duplicates in matches, responses, and signatures. A new conflict resolution feature allows you to choose whether to keep or overwrite duplicate items, with a detailed change log available after the operation completes. For more information, visit this page.
Git and Collaboration Enhancements
-
Simplified Git Setup for Composite Projects: When creating a composite project in ReadyAPI, the product now checks your Git configuration settings to ensure optimal collaboration. If adjustments are needed, you can easily update these settings before saving the composite project or committing it to Git. For more information, visit this page.
-
Global Preference for Line Separators in Project Files: You can now set a global preference to specify the line separator used in project files. For more information, visit this page.
General Enhancements
-
Enhanced Encryption in ReadyAPI: We updated encryption to improve security and performance across your projects.
-
SFTP Support in FTP Test Steps: ReadyAPI now lets you configure SFTP in FTP test steps, enabling secure file transfers directly within your tests. For more information, visit this page.
-
Library Updates: ReadyAPI 3.57.0 includes newer versions of some libraries that version 3.56.0 used. If your scripts refer to classes from these libraries, you might need to update the scripts.
Please see here for a list of fixes included in this patch.
