ReadyAPI 3.20.0 includes support for gRPC APIs and a number of various improvements and fixes. Below is the list of changes relative to the previous version of the product - ReadyAPI 3.10.2. For information on the changes made to other versions, see Version History.
Support for gRPC services
ReadyAPI now supports testing of gRPC services:
-
You add a new gRPC definition to your project by using a .proto file. ReadyAPI uses the definition to serialize and deserialize gRPC messages:
Click the image to enlarge it.
-
Use the API Connection test step to send and receive messages of gRPC APIs:
Click the image to enlarge it.
Currently, ReadyAPI supports only gRPC operations of the unary type. -
ReadyAPI also supports sending gRPC messages over the SSL/TLS protocol with and without a Google OAuth 2.0 authentication token.
-
You can add a Smart Assertion to the API Connection test step to check incoming messages:
Click the image to enlarge it.
Dark theme
ReadyAPI now fully supports the dark UI theme:
Click the image to enlarge it.
To use this theme, enable it in the Preferences > UI window:
Click the image to enlarge it.
Masking encrypted properties
Now, ReadyAPI masks values of the encrypted properties in all the logs and reports:
-
ReadyAPI Log panels.
-
ReadyAPI reports:
-
Printable
-
JUnit-Style
-
Data export
-
Allure
-
-
Logs of the command-line test runners.
More
-
When you configure a SmartBear ID-based license, you can open the Proxy Preferences dialog from the License Manager.
-
The Docker image for running functional tests now supports SmartBear ID-based licenses.
-
We’ve introduced the Docker image for running security tests. To learn more, see Security Tests in Docker.
-
We’ve updated the Apache Log4j library to v. 2.16 to mitigate the CVE-2021-45046 issue.
-
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.
