Features Added to ReadyAPI 3.54.0

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.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.