You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using turtle mock to mock objects that have virtual functions, frequently those virtual functions are intended to have their base implementation called.
Turtle mock has no mechanism to do that.
Ideally, the syntax for declaring a mock member function can be extended to signal that the base implementation should be called.
MOCK_CONST_METHOD(..., callBaseImpl);
The text was updated successfully, but these errors were encountered:
But when you have several hundred instances of a MOCK_EXPECT() on a function that needs to call the base class's function, it gets very tedious to have to use .calls() for each place.
I know that you're not actively working on this library anymore, but if someone does a drive-by contribution to add support for this that would be nice.
When using turtle mock to mock objects that have virtual functions, frequently those virtual functions are intended to have their base implementation called.
Turtle mock has no mechanism to do that.
Ideally, the syntax for declaring a mock member function can be extended to signal that the base implementation should be called.
MOCK_CONST_METHOD(..., callBaseImpl);
The text was updated successfully, but these errors were encountered: