...
Multiple messaging clients (or 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.
Change Log
1.3
- Decode grpc-status-details-bin header to JSON when both Protobuf and gRPC extensions are loaded
1.2
- Return traffic message after reporting unexpected status code
1.1
- 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
...