ReadyAPI 3.8.0 extends support for Kafka testing, adds support for AsyncAPI definitions, and includes some more improvements. Below is the list of changes relative to the previous version of the product – ReadyAPI 3.7. For information on the changes made to other versions, see Version History.
Support for AsyncAPI definitions
Now, you can add asynchronous APIs to your project by importing AsyncAPI definitions. ReadyAPI automatically creates the needed resources and operations:
Click the image to enlarge it.
Extended Kafka support
-
The Event-Driven test step has been renamed to API Connection.
-
Now, the API Connection test step in a data-driven loop reuses an existing connection rather than creates a new one for each iteration.
-
The Properties panel now contains the connection settings of the API Connection test step:
Click the image to enlarge it.
-
Now, you can restore the connection settings of the API Connection test step to the default values. To learn more, see Simulating Consumers and Simulating Producers.
-
We have improved the way you work with metadata in the API Connection test step:
-
ReadyAPI prevents the creation of two Key parameters.
-
We have fixed a number of issues with the user interface.
-
More
-
Now, when you add new resources or methods to a REST API, ReadyAPI modifies its OpenAPI definition stored in the project.
-
The Assertion tab in the REST VirtResponse, SOAP VirtResponse, and Receive MQTT Message test steps now looks similar to that tab in other test steps, such as the REST Request test step.
-
We’ve updated a few third-party libraries to make the product even more reliable and secure. If your scripts refer to classes from these libraries, you might need to update the scripts.
-
We have fixed a few bugs reported by our customers.
