...
- gRPC 1.0.0 or later
- Parasoft SOAtest 20202022.1 or later
Installation
This artifact can be installed from the UI or the command line.
...
| Key 1 - 4 | Specify the key for the custom header to send in the metadata of each gRPC call. Up to four custom headers are allowed. The key you specify should have a corresponding value. Keys are case insensitive and cannot start with the prefix |
|---|---|
| Value 1 - 4 | Specify the value for the custom header to send in the metadata of each gRPC call. Up to four custom headers are allowed. The value you specify should have a corresponding key. Binary values must be base64 encoded. |
Streaming Settings
| Scroll Table Layout | ||
|---|---|---|
|
...
Multiple messaging clients (or Protobuf ProtoBuf clients) are needed to test the other three gRPC method types for streaming. In each case the client requests and server responses are decoupled. Tools that are configured to send will not have any response payload and tools that are configured to receive will ignore the request payload. It is also necessary to send the completed notification from SOAtest after sending requests, even for server streaming method types that only take one request message. A tool configured to receive the completed notification will wait for that event or report an error if another response message is received. This allows SOAtest to consume a dynamic number of response messages from a gRPC stream by checking if the stream has completed inside of a looping test suite.
...
- Reorganized configuration sections
- Token-based authentication in gRPC call credentials
- Send gRPC metadata custom headers and show in traffic viewer
- Verify expected status codes from gRPC calls
1.0
- Initial release
Third-Party Content
...