Conditional Match Enhancements$$$Setting Date Delta Using Property Expansion: Conditional Match now supports setting Date Delta using Property Expansion. You can specify the default date format dd-MM-yyyy in Virtual Service Preferences; allowing responses to have dates relative to request dates. Property expansion and date offset syntax; including requestDateDelta and currentDateDelta; are applied to request and response fields with this format. For more information; visit this page.$$$$$$Selected Items Previewer: A new Selected Items Previewer in the Configure dialog for Conditional Match allows you to visualize relationships between signatures; requests; and responses. Select a signature; request; or response to see its related matches. For more information; visit this page.$$$$$$Array Parameter Size in Conditional Match: Users can now specify the size of array parameters in signatures. For more information; visit this page.$$$$$$Ignore Null/Empty Parameters in Conditional Match: Users now have the option to ignore null or empty parameters when matching signatures. For more information; visit this page.$$$$$$Aliases for Any and Empty Values in Conditional Match: Users can now use aliases for any and empty values in the Valid Value column when configuring a Conditional Match. The alias * represents any value; while _ signifies an empty value. For more information; visit this page.$$$$$$Default Response per Signature: You can now configure a default response for each signature. If an incoming request matches a signature but no specific response is found; the default response for that signature will be used. If no signatures match; the global default response will be sent. For more information; visit this page.

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.$$$$$$ReadyAPI 3.54.0 includes a few changes compared to the previous product version – ReadyAPI 3.53.0. For information on the changes made to other versions; see Version History.$$$$$$Conditional Match$$$We are introducing Conditional Match; a new dispatch style setting within ReadyAPIs Virtualization module. This feature offers enhanced control over how virtual services respond to requests; facilitating more realistic and dynamic testing scenarios. Learn more about Conditional Match here.$$$$$$Functionality Improvements$$$ReadyAPI now allows fetching Avro/Protobuf key schema from a file.$$$$$$We added support for new custom Kafka test step properties:$$$$$$connectionSettings$$$$$$data$$$$$$channel$$$$$$endpoint$$$$$$schemas$$$$$$We have updated Swagger Compliance Assertion for OAS 3.1.$$$$$$We have introduced Property Expansion support for the MQTT plugin.$$$$$$Integration Enhancements$$$We added support for Client ID and Client Secret from SLM On-premise License Server 2.0 to the Maven integration when using SLM on-premise.$$$$$$Plugin Updates$$$Client credentials for the SLM on-premise license server (version 2.0 or later) are now supported in both Jenkins Plugin version 1.11.0 and Azure Plugin version 2.1.8.$$$$$$We have released version 1.6.6 of the ready-mqtt-plugin.$$$$$$General Updates$$$ReadyAPI 3.54.0 includes newer versions of some libraries that version 3.53.0 used. If your scripts refer to classes from these libraries; you might need to update the scripts.$$$$$$We updated the JDK to version 17.0.11.$$$$$$Known Issues$$$We have identified a bug in TestRunner when using the -i argument; which commands the runner to enable UI components via the UISupport class in your tests. This argument currently fails to initialize a license and requires a fix. Please refrain from using the -i argument until we confirm the issue has been resolved.

ReadyAPI Feature Enhancement$$$Users can use a file named readyapi-install.vmoptions to specify JVM options that ReadyAPI will incorporate post-installation. The file must be in the same directory as the ReadyAPI installer.$$$$$$In the ReadyAPI PKCE flow for logging into Virtserver; there is a timeout of 20 seconds. ReadyAPI waits for 20 seconds for the browser to open; for users to enter authorization credentials; and for Okta to redirect back to ReadyAPI. If this process exceeds 20 seconds; ReadyAPI displays the Login Screen again with the Login with OIDC button. This timeout value can be configured via the vmoption virtserver.oidc.login.timeout.$$$$$$General Updates$$$We updated Spring to version 5.3.33.

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 that 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; sniHostCheck is now set to false to 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:tIt is recommended to skip version 3.52.0 if youre 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 and security vulnerabilities included in this patch.

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.$$$$$$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:tWe 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 and security vulnerabilities included in this patch.