Greetings! My team is trying to start using Pact in an ecosystem of scala-based gRPC microservices. One of the things I’m encouraging is the use of well-defined gRPC status codes when applicable. It seems to me that these codes can be meaningful in a contract. For example, we could use

NOT_FOUND

as a means to communicate non-existence of an entity. If the provider changed behavior to return

INVALID_ARGUMENT

instead in the same situation it would clearly break clients. Is there a way to write a consumer test matching on gRPC response status? An example would be ideal. I’m fearing there may not be based upon this code which seems to only perform validations on non-error responses, but I am not 100% sure I’m looking in the right spot.

This is a good idea. Can you raise an issue for this on the GitHub project?

@uglyog Sure, I can do that. Here I assume? https://github.com/pactflow/pact-protobuf-plugin Curious what you’ve seen from gRPC Java with respect to this? We tend to see actual non-OK status codes come back as

StatusRuntimeException

. Haven’t seen the ignoring issue, but maybe we’re using a different library (scalapb wrapper on grpc-netty) or you’re coming in at a different layer?

Curious what you’ve seen from gRPC Java with respect to this?

I haven't really dug into it, I was expecting to get some exception with the status and associated message, but I got an IO exception stating that the Protobuf message could not be parsed. It might be due to some interceptor needing to be setup, but I expected this behaviour out of the box and it looks like it ignores the status.

Do we not support expecting grpc error code today in the contract?