aspnetcore/grpc/test-client.md
Testing is an important aspect of building stable and maintainable software. Part of writing high-quality tests is removing external dependencies. This article discusses using mock gRPC clients in tests to remove gRPC calls to external servers.
To demonstrate client app tests, review the following type in the sample app.
View or download sample code (how to download)
The Worker is a BackgroundService that makes calls to a gRPC server.
The preceding type:
TesterClient is generated automatically by the tooling package Grpc.Tools based on the test.proto file, during the build process.TesterClient and IGreetRepository. The app is configured to use the gRPC client factory to create TesterClient.IGreetRepository service and TesterClient client using a mock object framework, such as Moq. A mocked object is a fabricated object with a predetermined set of property and method behaviors used for testing. For more information, see xref:test/integration-tests#introduction-to-integration-tests.For more information on the C# assets automatically generated by Grpc.Tools, see gRPC services with C#: Generated C# assets.
gRPC clients are concrete client types that are generated from .proto files. The concrete gRPC client has methods that translate to the gRPC service in the .proto file. For example, a service called Greeter generates a GreeterClient type with methods to call the service.
A mocking framework can mock a gRPC client type. When a mocked client is passed to the type, the test uses the mocked method instead of sending a gRPC call to a server.
The preceding unit test:
IGreetRepository and TesterClient using Moq.SaveGreeting is called with the greeting message returned by the mocked TesterClient.CallHelpers from the gRPC examples