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 webpage provides documentation for the \u003ccode\u003eMockSqlDatabasesServiceConnection\u003c/code\u003e class, which is used to test code that interacts with \u003ccode\u003eSqlDatabasesServiceClient\u003c/code\u003e by simulating responses, including errors.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation includes version information, with \u003ccode\u003e2.37.0-rc\u003c/code\u003e being the latest release candidate and a list that includes all versions from that down to \u003ccode\u003e2.11.0\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eMockSqlDatabasesServiceConnection\u003c/code\u003e class uses \u003ccode\u003egMock\u003c/code\u003e for its methods, and the documentation provides links to the \u003ccode\u003egMock\u003c/code\u003e documentation for further details on implementation.\u003c/p\u003e\n"],["\u003cp\u003eThe class contains several virtual methods for database operations, such as \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, each taking a specific request object as input and returning either an \u003ccode\u003eOperation\u003c/code\u003e or a \u003ccode\u003eDatabase\u003c/code\u003e object encapsulated in a \u003ccode\u003eStatusOr\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThere is also an example given for testing, which although is BigQuery specific, highlights the principles applicable for any \u003ccode\u003e*Client\u003c/code\u003e and \u003ccode\u003e*Connection\u003c/code\u003e interaction.\u003c/p\u003e\n"]]],[],null,[]]
