mirror of
https://github.com/google/googletest.git
synced 2026-02-06 09:49:54 +08:00
docs: add NaggyMock description to gmock cookbook
This commit is contained in:
parent
9156d4caac
commit
04e9129ce6
@ -457,6 +457,21 @@ TEST(...) {
|
||||
// is called.
|
||||
}
|
||||
```
|
||||
The default behavior for mock objects in gMock is *naggy*. That is, if you use
|
||||
`MockFoo` directly (without wrapping it in `NiceMock` or `StrictMock`),
|
||||
uninteresting calls will be allowed but will generate warnings.
|
||||
|
||||
You can also explicitly state this behavior using `NaggyMock`:
|
||||
|
||||
```cpp
|
||||
using ::testing::NaggyMock;
|
||||
|
||||
TEST(...) {
|
||||
NaggyMock<MockFoo> mock_foo;
|
||||
EXPECT_CALL(mock_foo, DoThis());
|
||||
... code that uses mock_foo ...
|
||||
}
|
||||
```
|
||||
|
||||
{: .callout .note}
|
||||
NOTE: `NiceMock` and `StrictMock` only affects *uninteresting* calls (calls of
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user