Application developers may want to test their code with simulated responses, including errors, from an object of type SqlDatabasesServiceClient. To do so, construct an object of type SqlDatabasesServiceClient with an instance of this class. Then use the Google Test framework functions to program the behavior of this mock.
See Also
This example for how to test your application with GoogleTest. While the example showcases types from the BigQuery library, the underlying principles apply for any pair of *Client and *Connection.
Functions
virtual options()
This function is implemented using gMock's MOCK_METHOD().
Consult the gMock documentation to use this mock in your tests.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["\u003cp\u003eThis document outlines the \u003ccode\u003eMockSqlDatabasesServiceConnection\u003c/code\u003e class, which is used to simulate responses from \u003ccode\u003eSqlDatabasesServiceClient\u003c/code\u003e for testing purposes.\u003c/p\u003e\n"],["\u003cp\u003eThe latest version available is \u003ccode\u003e2.37.0-rc\u003c/code\u003e, with a range of previous versions available, going down to \u003ccode\u003e2.11.0\u003c/code\u003e, each with its corresponding documentation.\u003c/p\u003e\n"],["\u003cp\u003eThe class leverages GoogleTest's gMock framework, specifically the \u003ccode\u003eMOCK_METHOD()\u003c/code\u003e macro, to enable mocking of functions such as \u003ccode\u003eoptions()\u003c/code\u003e, \u003ccode\u003eDelete()\u003c/code\u003e, \u003ccode\u003eGet()\u003c/code\u003e, \u003ccode\u003eInsert()\u003c/code\u003e, \u003ccode\u003eList()\u003c/code\u003e, \u003ccode\u003ePatch()\u003c/code\u003e, and \u003ccode\u003eUpdate()\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eEach of these mocked functions, like \u003ccode\u003eDelete\u003c/code\u003e, takes a request object, such as \u003ccode\u003eSqlDatabasesDeleteRequest\u003c/code\u003e, as a parameter and returns either a \u003ccode\u003eStatusOr\u003c/code\u003e object containing an \u003ccode\u003eOperation\u003c/code\u003e or \u003ccode\u003eDatabase\u003c/code\u003e or \u003ccode\u003eDatabasesListResponse\u003c/code\u003e type, or options.\u003c/p\u003e\n"],["\u003cp\u003eThere is a link provided to a BigQuery testing example that demonstrates the underlying principles of using mocks with \u003ccode\u003e*Client\u003c/code\u003e and \u003ccode\u003e*Connection\u003c/code\u003e pairs.\u003c/p\u003e\n"]]],[],null,[]]
