@improbable-eng/grpc-web-fake-transport

Fake Transport for use with @improbable-eng/grpc-web.

Usage

FakeTransportBuilder builds a Transport that can be configured to send preset headers, messages, and trailers for testing.

By default the Transport that FakeTranportBuilder.build() generates will trigger all of the specified response behaviours (.withHeaders(metadata), .withMessages([msgOne, msgTwo]), .withTrailers(metadata)) when the client has finished sending.

This is usually the desired flow as all of the response behaviour is triggered only after the client has finished sending as would most commonly occur in production usage.

However, in the case of bi-directional or other complex usage it can be helpful to use .withManualTrigger() to disable automatic sending of messages or headers/trailers and trigger the sending manually using sendHeaders(), sendMessages() and sendTrailers().

With Service Stubs generated by ts-protoc-gen

1import { FakeTransportBuilder } from '@improbable-eng/grpc-web-fake-transport';
2
3const fakeTransport = new FakeTransportBuilder()
4  .withMessages([ new PingResponse() ])
5  .build();
6
7const client = new PingServiceClient("https://example.com", {
8  transport: fakeTransport
9});
10
11client.DoPing(/* ... */);

With grpc-web

1import { grpc } from '@improbable-eng/grpc-web';
2import { FakeTransportBuilder } from '@improbable-eng/grpc-web-fake-transport';
3
4const fakeTransport = new FakeTransportBuilder()
5  .withMessages([ new PingResponse() ])
6  .build();
7
8grpc.invoke(PingService.DoPing, {
9  host: "https://example.com",
10  transport: fakeTransport,
11  /* ... */
12});

With withManualTrigger()

1import { grpc } from '@improbable-eng/grpc-web';
2import { FakeTransportBuilder } from '@improbable-eng/grpc-web-fake-transport';
3
4const fakeTransport = new FakeTransportBuilder()
5  .withManualTrigger()
6  .withHeaders(new grpc.Metadata({ headerKey: "value" }))
7  .withMessages([ new PingResponse() ])
8  .withTrailers(new grpc.Metadata({ trailerKey: "value" }))
9  .build();
10
11grpc.invoke(PingService.DoPing, {
12  host: "https://example.com",
13  transport: fakeTransport,
14  /* ... */
15});
16
17// Manually trigger the response behaviours
18fakeTransport.sendHeaders();
19fakeTransport.sendMessages();
20fakeTransport.sendTrailers();

Alternatively replace the Default Transport when initialising your tests:

1import { grpc } from "@improbable-eng/grpc-web";
2import { NodeHttpTransport } from "@improbable-eng/grpc-web-fake-transport";
3
4// Do this first, before you make any grpc requests!
5grpc.setDefaultTransport(fakeTransport);