Mocking gRPC services

WireMock 3.2.0+ supports mocking of gRPC services via the WireMock extension for gRPC.

The extension scans for descriptor files (generated from the service’s .proto files) in the grpc subdirectory of WireMock’s root.

Using these, it converts incoming messages to JSON before passing them to WireMock’s core stubbing system which allows the existing JSON matchers to be used when matching requests. It also converts JSON responses back into proto messages so that all of WireMock’s response definition features including templating can be used.

WireMock and gRPC schema

The extension also adds a Java DSL that works with the Java classes generated by protoc, while also providing a more gRPC idiomatic way of defining stubs.

Java usage #

Setup #

Add the extension JAR dependency to your project:


implementation 'org.wiremock:wiremock-grpc-extension:0.6.0'



Create a root directory for WireMock e.g. src/test/resources/wiremock and create a subdirectory under this named grpc.

Put the descriptor files generated by protoc from your .proto files into the grpc directory.

Initialise WireMock server with the extension enabled and the root directory set to the path created in the previous steps:

// Same config object also for the JUnit 4 rule or JUnit 5 extension
WireMockServer wm = new WireMockServer(wireMockConfig()
        .extensions(new GrpcExtensionFactory())

Initialise a service class for the gRPC service you want to mock (this must be defined in the .proto file you compiled to a descriptor):

WireMockGrpcService mockGreetingService =
    new WireMockGrpcService(
        new WireMock(wm.getPort()),

Stubbing via JSON matching + responses #

To specify request criteria and response data via JSON:

        .withRequestMessage(equalToJson("{ \"name\":  \"Tom\" }"))
        .willReturn(json("{ "greeting": "Hi Tom from JSON" }")));

Or with a templated response:

        .withRequestMessage(equalToJson("{ \"name\":  \"${json-unit.any-string}\" }"))
                "{ \"greeting\": \"Hello \" }")));

Stubbing via Java message objects #

Matching and stubbing in the Java DSL can also be specified using the Java classes generated by protoc:


Non-OK responses #

You can return gRPC error codes instead of an OK response:

            HelloRequest.newBuilder().setName("Prereq failure")
        .willReturn(Status.FAILED_PRECONDITION, "Failed on some prerequisite"));

More examples #

For a more complete set of examples, see the Java demo project.

Standalone usage #

Setup #

Download the standalone JAR at version 3.2.0 or above and the gRPC extension JAR into your working directory.

Create a WireMock data directory with a subdirectory for stub mappings and one for descriptor files:

mkdir -p wiremock/mappings wiremock/grpc

Compile your proto files into descriptors:

protoc --descriptor_set_out wiremock/grpc/services.dsc ExampleServices.proto

Run WireMock with both on the classpath:

java -cp wiremock-standalone-3.5.4.jar:wiremock-grpc-extension-standalone-0.6.0.jar \
  wiremock.Run \
  --root-dir wiremock-data

Stubbing #

gRPC stubs are defined using WireMock’s standard JSON format. Requests should always be matched with a POST method and a URL path of /<fully-qualified service name>/<method name>.

  "request" : {
    "urlPath" : "/com.example.grpc.GreetingService/greeting",
    "method" : "POST",
    "bodyPatterns" : [{
      "equalToJson" : "{ \"name\":  \"Tom\" }"
  "response" : {
    "status" : 200,
    "body" : "{\n  \"greeting\": \"Hi Tom\"\n}",
    "headers" : {
      "grpc-status-name" : "OK"

More Demos #

For more see the standalone demo project.