failed with flutter test:call from the client against the fake server, and verify behaviors changes from the server side about grpc-dart HOT 9 CLOSED

Yeup that sounds reasonable! My recommendation would be to mock the generated gRPC client instead, since you can be reasonably sure that the generated code uses gRPC-dart correctly, and that gRPC-dart itself is tested. This makes the complicated harness completely unnecessary.

To do this using mockito:

// Assuming you're testing a generated client called LoginClient
class MockLoginClient extends Mock implements LoginClient {}

test('login request', () async {
    final mockClient = MockLoginClient();

    var expectedResp = new LoginResp();
    loginResp.token = 'Token';
    loginResp.success = true;

    when(mockClient.loginRequest(any)).thenAnswer((_) => Future.value(loginResp));

    var loginReq = new LoginReq();
    loginReq.serverAddr = '127.0.01';
    loginReq.imei = 350..;
    loginReq.language = 'EN';
    loginReq.password = 'Password';
    loginReq.userName = 'UserName';

    var realResp = await mockClient.loginRequest(loginReq);
    expect(realResp, expectedResp);
});

Does that make sense?

from grpc-dart.

Thanks for your response.

but I got this error

type 'Future' is not a subtype of type 'ResponseFuture'

Any idea how I could solve this?

from grpc-dart.

I've posted workaround for mocking client responses: google/protobuf.dart#162 (comment)

from grpc-dart.

Are you writing a test to test your own GRPC Client?

client_test.dart is really structured to test the inner workings of the client / server communication down to the Http2 transport layer. If you want to go down to this level of testing you will still have to encode the LoginResp message to a StreamMessage for this to work. The serializations are usually generated as part of the protobuf tool.

In general, if you're writing your own client you likely don't want to go down to this level, which is really testing how grpc-dart works (which already has tests).

Does that make sense?

from grpc-dart.

I don't want to test GRPC client.I wrote an application with dart(client side) and go(server side) and for test I don't want to connect directly to db and get response.I want to write mock server and get response from this mock server.

from grpc-dart.

It looks like ResponseFuture is an implementation detail of the client. I've opened the above issue on the actual code generator to replace it with Future in generated Client signatures.

In the meantime as a workaround you could replace ResponseFuture with Future in the generated client.

from grpc-dart.

from grpc-dart.

Can you think of any way to work around it? To create ResponseFuture mock? I failed to do it :(

from grpc-dart.

Not that I can think of. ResponseFuture is very much an implementation detail -- its entire extension interface is private and it doesn't expose a way to create an already completed future (like Future.value).

If you attempt to mock ResponseFuture you would have to mock the relevant calls to Future, which I don't happen to know (probably just then but I'm not sure)

from grpc-dart.