ReadyAPI 3.9.0 streamlines API testing by extending the API Connection test step and adding a new assertion. Below is the list of changes relative to the previous version of the product – ReadyAPI 3.8.1. For information on the changes made to other versions, see Version History.
REST support in the API Connection test step BETA
Now, you can test REST APIs by using the API Connection test step. It means you can send REST requests, get responses, and validate them as you do with the REST Request test step, but with the cleaner and more convenient user interface:
REST testing with the API Connection test step is close to that process with the REST Request test step:
You link an API request to a test step, so it synchronizes the resource path, REST method, and parameters.
You can validate the received response by using assertions.
The API Connection test step supports environments.
You can use property expansions in parameters and the request body.
However, there are some differences as compared to REST Request. For example, to set authentication, you select the needed Auth profile in the Authorization profile combo box instead of the Auth panel.
To learn more, see API Connection Test Step.
ReadyAPI 3.9.0 introduces the Smart Assertion. It verifies one or more values in the body or metadata of API responses:
The assertion is similar to the Message Content Assertion but has a number of improvements:
You can use it to verify response metadata: headers, the HTTP status code, and Kafka key and partition values.
You can use additional conditions when comparing values.
You can specify whether a value to be checked should be case-sensitive or not.
You can configure the assertion quicker because the configuration dialog has a cleaner interface.
To learn more, see Smart Assertion.
The Smart Assertion supersedes some existing assertions. Since ReadyAPI 3.9.0, they are deprecated in favor of the new assertion. These assertions will continue working, but we recommend that you replace them with the Smart Assertion: