Application developers may want to test their code with simulated responses, including errors, from an object of type SqlUsersServiceClient. To do so, construct an object of type SqlUsersServiceClient 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\u003eMockSqlUsersServiceConnection\u003c/code\u003e class, which is designed to allow for the testing of \u003ccode\u003eSqlUsersServiceClient\u003c/code\u003e with simulated responses.\u003c/p\u003e\n"],["\u003cp\u003eThe content lists available versions of the class, starting from version 2.17.0 up to the latest release candidate 2.37.0-rc, and includes links to the corresponding documentation for each.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eMockSqlUsersServiceConnection\u003c/code\u003e class uses gMock to implement its 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, and \u003ccode\u003eUpdate()\u003c/code\u003e, allowing developers to program the behavior of the mock within their tests.\u003c/p\u003e\n"],["\u003cp\u003eEach function of \u003ccode\u003eMockSqlUsersServiceConnection\u003c/code\u003e is documented with its parameter, along with the expected return type, such as \u003ccode\u003eStatusOr< google::cloud::sql::v1::Operation >\u003c/code\u003e or \u003ccode\u003eStatusOr< google::cloud::sql::v1::User >\u003c/code\u003e, as defined by the functions \u003ccode\u003eDelete\u003c/code\u003e, \u003ccode\u003eInsert\u003c/code\u003e, \u003ccode\u003eUpdate\u003c/code\u003e and \u003ccode\u003eGet\u003c/code\u003e respectively.\u003c/p\u003e\n"],["\u003cp\u003eThere is an example provided that links to a mock in the BigQuery library, illustrating the overall principle of using a *Client and *Connection for testing, which is applicable to all such pairs across the Google Cloud C++ libraries.\u003c/p\u003e\n"]]],[],null,[]]
