In previous version of Google Mock you can only mock virtual functions, see the documentation in the project’s page. More recent versions allowed to mock non-virtual methods, using what they call hi-perf dependency injection. As user @congusbongus states in the comment below this answer: Google Mock relies on adding member variables to support method mocking, … Read more
Yes, you can call EXPECT_CALL on the same mock object multiple times. As long as you assure that all EXPECT_CALL were called before the mocked methods were actually used. Otherwise your test will rely on undefined behavior. From ForDummies: Important note: gMock requires expectations to be set before the mock functions are called, otherwise the … Read more
This is a result of holding p as a shared_ptr, using InSequence and the order in which you have declared your expectations. When you call EXPECT_CALL(*c, myMethod(Eq(p))); you increase the use_count of p. In order for the leak detection to pass, p must be destroyed at (or before) the end of TEST. The problem here … Read more
There are no needs to explicitly tell that no methods will be called. If you set the logging level high enough, you should get a message if a method is called (if no expectation is set). Other then that, you can set expectations like this : EXPECT_CALL( mockObj, Foo(_) ).Times(0); on all methods.
“Google Mock is not a testing framework itself. Instead, it needs a testing framework for writing tests. Google Mock works seamlessly with Google Test. It comes with a copy of Google Test bundled. Starting with version 1.1.0, you can also use it with any C++ testing framework of your choice. ” – Google Mock, System … Read more
All documentation is covered in the official github repo. The primer documentation also covers a lot of information regarding the test macros. You could use the following summary and the examples linked to choose what you want to use. TEST() is useful when you want to write unit tests for static or global functions or … Read more
A feasible workaround for google mock framework’s problems with non (const) copyable function arguments and retun values is to use proxy mock methods. Suppose you have the following interface definition (if it’s good style to use std::unique_ptr in this way seems to be more or less a philosophical question, I personally like it to enforce … Read more
I use it frequently. It’s trivial to do relatively easy things, and possible to do very difficult things – that’s pretty much what I want from a framework. The hardest part about writing custom Matchers (and other stuff) with Google’s mocks isn’t Google’s mocks, it’s C++’s template errors… they’re close to impossible to parse. I … Read more
There are subtle but significant differences between the two statements. EXPECT_CALL sets expectation on a mock calls. Writing EXPECT_CALL(mock, methodX(_)).WillRepeatedly(do_action); tells gMock that methodX may be called on mock any number of times with any arguments, and when it is, mock will perform do_action. On the other hand, ON_CALL(mock, methodX(_)).WillByDefault(do_action); tells gMock that whenever methodX … Read more