ReadyAPI 3.7.0 includes support for testing Kafka APIs, support for assertion groups, and some more improvements. Below is the list of changes relative to the previous version of the product – ReadyAPI 3.6. For information on the changes made to other versions, see Version History.
ReadyAPI now supports testing of Kafka-based APIs:
You add a new Kafka API to your project and then add topics and operations to that API using special dialog boxes and editors:
Use the new Event-Driven test step to send and receive messages of asynchronous Kafka APIs. The test step operates in one of the following modes:
In Subscribe mode, it connects to a Kafka topic and receives messages from it as long as the connection is open.
In Publish mode, it connects to a topic, publishes a message there, and disconnects.
You can add assertions to the Event-Driven test step working in Subscribe mode to check incoming messages:
ReadyAPI can also serialize and deserialize Kafka messages using connection to Schema Registries.
Assertions in a functional test can now be grouped into an assertion group:
An assertion group behaves like a regular assertion: it can either pass or fail. Its status depends on the statuses of assertions included in it and the conditions applied (
AND / OR).
We’ve removed some rarely used tabs:
– The Resources tab from the REST service editor.
– The Objects tab from the GraphQL service editor.
– The Operations tab from the SOAP and XML-RPC service editors.
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.