What's New in ReadyAPI

Applies to ReadyAPI 3.54, last modified on September 23, 2024
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.

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 ReadyAPI's 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.

Please see here for a list of fixes included in this patch.

See Also

Version History

Download ReadyAPI
Highlight search results