2020-06-25 11:56:24 -04:00
# gMock Cheat Sheet
2015-08-24 18:41:02 -04:00
2020-06-25 11:56:24 -04:00
## Defining a Mock Class
2015-08-24 18:41:02 -04:00
2020-06-25 11:56:24 -04:00
### Mocking a Normal Class {#MockClass}
2015-08-24 18:41:02 -04:00
Given
2019-07-17 15:35:48 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2015-08-24 18:41:02 -04:00
class Foo {
...
virtual ~Foo();
virtual int GetSize() const = 0;
virtual string Describe(const char* name) = 0;
virtual string Describe(int type) = 0;
virtual bool Process(Bar elem, int count) = 0;
};
```
2019-07-17 15:35:48 -04:00
2015-08-24 18:41:02 -04:00
(note that `~Foo()` **must** be virtual) we can define its mock as
2019-07-17 15:35:48 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2015-08-24 18:41:02 -04:00
#include "gmock/gmock.h"
class MockFoo : public Foo {
2019-07-17 15:35:48 -04:00
...
MOCK_METHOD(int, GetSize, (), (const, override));
MOCK_METHOD(string, Describe, (const char* name), (override));
MOCK_METHOD(string, Describe, (int type), (override));
MOCK_METHOD(bool, Process, (Bar elem, int count), (override));
2015-08-24 18:41:02 -04:00
};
```
2019-07-17 15:35:48 -04:00
To create a "nice" mock, which ignores all uninteresting calls, a "naggy" mock,
which warns on all uninteresting calls, or a "strict" mock, which treats them as
failures:
2018-09-03 21:56:23 +03:00
```cpp
2019-07-17 15:35:48 -04:00
using ::testing::NiceMock;
using ::testing::NaggyMock;
using ::testing::StrictMock;
NiceMock< MockFoo > nice_foo; // The type is a subclass of MockFoo.
NaggyMock< MockFoo > naggy_foo; // The type is a subclass of MockFoo.
StrictMock< MockFoo > strict_foo; // The type is a subclass of MockFoo.
2015-08-24 18:41:02 -04:00
```
2021-02-18 19:18:34 -05:00
{: .callout .note}
2019-07-17 15:35:48 -04:00
**Note:** A mock object is currently naggy by default. We may make it nice by
default in the future.
2020-06-25 11:56:24 -04:00
### Mocking a Class Template {#MockTemplate}
2019-07-17 15:35:48 -04:00
Class templates can be mocked just like any class.
2015-08-24 18:41:02 -04:00
To mock
2019-07-17 15:35:48 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2015-08-24 18:41:02 -04:00
template < typename Elem >
class StackInterface {
...
virtual ~StackInterface();
virtual int GetSize() const = 0;
virtual void Push(const Elem& x) = 0;
};
```
2019-07-17 15:35:48 -04:00
(note that all member functions that are mocked, including `~StackInterface()`
**must** be virtual).
2018-09-03 21:56:23 +03:00
```cpp
2015-08-24 18:41:02 -04:00
template < typename Elem >
class MockStack : public StackInterface< Elem > {
...
2019-07-17 15:35:48 -04:00
MOCK_METHOD(int, GetSize, (), (const, override));
MOCK_METHOD(void, Push, (const Elem& x), (override));
2015-08-24 18:41:02 -04:00
};
```
2020-06-25 11:56:24 -04:00
### Specifying Calling Conventions for Mock Functions
2019-07-17 15:35:48 -04:00
If your mock function doesn't use the default calling convention, you can
specify it by adding `Calltype(convention)` to `MOCK_METHOD` 's 4th parameter.
For example,
2015-08-24 18:41:02 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2019-07-17 15:35:48 -04:00
MOCK_METHOD(bool, Foo, (int n), (Calltype(STDMETHODCALLTYPE)));
MOCK_METHOD(int, Bar, (double x, double y),
(const, Calltype(STDMETHODCALLTYPE)));
2015-08-24 18:41:02 -04:00
```
2019-07-17 15:35:48 -04:00
2015-08-24 18:41:02 -04:00
where `STDMETHODCALLTYPE` is defined by `<objbase.h>` on Windows.
2020-06-25 11:56:24 -04:00
## Using Mocks in Tests {#UsingMocks}
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
The typical work flow is:
1. Import the gMock names you need to use. All gMock symbols are in the
`testing` namespace unless they are macros or otherwise noted.
2. Create the mock objects.
3. Optionally, set the default actions of the mock objects.
4. Set your expectations on the mock objects (How will they be called? What
will they do?).
5. Exercise code that uses the mock objects; if necessary, check the result
using googletest assertions.
6. When a mock object is destructed, gMock automatically verifies that all
expectations on it have been satisfied.
Here's an example:
2015-08-24 18:41:02 -04:00
2018-09-03 21:56:23 +03:00
```cpp
using ::testing::Return; // #1
2015-08-24 18:41:02 -04:00
TEST(BarTest, DoesThis) {
MockFoo foo; // #2
ON_CALL(foo, GetSize()) // #3
.WillByDefault(Return(1));
// ... other default actions ...
EXPECT_CALL(foo, Describe(5)) // #4
.Times(3)
.WillRepeatedly(Return("Category 5"));
// ... other expectations ...
2021-03-22 19:35:21 -07:00
EXPECT_EQ(MyProductionFunction(& foo), "good"); // #5
2015-08-24 18:41:02 -04:00
} // #6
```
2020-06-25 11:56:24 -04:00
## Setting Default Actions {#OnCall}
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
gMock has a **built-in default action** for any function that returns `void` ,
`bool` , a numeric value, or a pointer. In C++11, it will additionally returns
the default-constructed value, if one exists for the given type.
To customize the default action for functions with return type *`T`* :
2015-08-24 18:41:02 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2015-08-24 18:41:02 -04:00
using ::testing::DefaultValue;
// Sets the default value to be returned. T must be CopyConstructible.
DefaultValue< T > ::Set(value);
// Sets a factory. Will be invoked on demand. T must be MoveConstructible.
2019-07-17 15:35:48 -04:00
// T MakeT();
2015-08-24 18:41:02 -04:00
DefaultValue< T > ::SetFactory(&MakeT);
// ... use the mocks ...
// Resets the default value.
DefaultValue< T > ::Clear();
```
2019-07-17 15:35:48 -04:00
Example usage:
2018-09-03 21:56:23 +03:00
```cpp
2019-07-17 15:35:48 -04:00
// Sets the default action for return type std::unique_ptr< Buzz > to
// creating a new Buzz every time.
DefaultValue< std::unique_ptr < Buzz > >::SetFactory(
[] { return MakeUnique< Buzz > (AccessLevel::kInternal); });
// When this fires, the default action of MakeBuzz() will run, which
// will return a new Buzz object.
EXPECT_CALL(mock_buzzer_, MakeBuzz("hello")).Times(AnyNumber());
auto buzz1 = mock_buzzer_.MakeBuzz("hello");
auto buzz2 = mock_buzzer_.MakeBuzz("hello");
2021-03-22 19:35:21 -07:00
EXPECT_NE(buzz1, nullptr);
EXPECT_NE(buzz2, nullptr);
2019-07-17 15:35:48 -04:00
EXPECT_NE(buzz1, buzz2);
// Resets the default action for return type std::unique_ptr< Buzz > ,
// to avoid interfere with other tests.
DefaultValue< std::unique_ptr < Buzz > >::Clear();
2015-08-24 18:41:02 -04:00
```
2019-07-17 15:35:48 -04:00
To customize the default action for a particular method of a specific mock
object, use `ON_CALL()` . `ON_CALL()` has a similar syntax to `EXPECT_CALL()` ,
but it is used for setting default behaviors (when you do not require that the
2021-01-22 13:49:00 -05:00
mock method is called). See [here ](gmock_cook_book.md#UseOnCall ) for a more
detailed discussion.
2015-08-24 18:41:02 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2019-07-17 15:35:48 -04:00
ON_CALL(mock-object, method(matchers))
.With(multi-argument-matcher) ?
.WillByDefault(action);
2015-08-24 18:41:02 -04:00
```
2020-06-25 11:56:24 -04:00
## Setting Expectations {#ExpectCall}
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
`EXPECT_CALL()` sets **expectations** on a mock method (How will it be called?
What will it do?):
2015-08-24 18:41:02 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2019-07-17 15:35:48 -04:00
EXPECT_CALL(mock-object, method (matchers)?)
.With(multi-argument-matcher) ?
.Times(cardinality) ?
.InSequence(sequences) *
.After(expectations) *
.WillOnce(action) *
.WillRepeatedly(action) ?
.RetiresOnSaturation(); ?
2015-08-24 18:41:02 -04:00
```
2019-09-06 15:54:21 -04:00
For each item above, `?` means it can be used at most once, while `*` means it
can be used any number of times.
In order to pass, `EXPECT_CALL` must be used before the calls are actually made.
The `(matchers)` is a comma-separated list of matchers that correspond to each
of the arguments of `method` , and sets the expectation only for calls of
`method` that matches all of the matchers.
2019-07-17 15:35:48 -04:00
If `(matchers)` is omitted, the expectation is the same as if the matchers were
set to anything matchers (for example, `(_, _, _, _)` for a four-arg method).
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
If `Times()` is omitted, the cardinality is assumed to be:
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
* `Times(1)` when there is neither `WillOnce()` nor `WillRepeatedly()` ;
* `Times(n)` when there are `n` `WillOnce()` s but no `WillRepeatedly()` , where
`n` >= 1; or
* `Times(AtLeast(n))` when there are `n` `WillOnce()` s and a
`WillRepeatedly()` , where `n` >= 0.
A method with no `EXPECT_CALL()` is free to be invoked *any number of times* ,
and the default action will be taken each time.
2020-06-25 11:56:24 -04:00
## Matchers {#MatcherList}
2019-07-17 15:35:48 -04:00
2021-04-27 16:22:33 -04:00
See the [Matchers Reference ](reference/matchers.md ).
2015-08-24 18:41:02 -04:00
2020-06-25 11:56:24 -04:00
## Actions {#ActionList}
2015-08-24 18:41:02 -04:00
**Actions** specify what a mock function should do when invoked.
2020-06-25 11:56:24 -04:00
### Returning a Value
2019-07-17 15:35:48 -04:00
2019-10-23 14:09:41 -04:00
| | |
| :-------------------------------- | :-------------------------------------------- |
| `Return()` | Return from a `void` mock function. |
| `Return(value)` | Return `value` . If the type of `value` is different to the mock function's return type, `value` is converted to the latter type < i > at the time the expectation is set</ i > , not when the action is executed. |
| `ReturnArg<N>()` | Return the `N` -th (0-based) argument. |
| `ReturnNew<T>(a1, ..., ak)` | Return `new T(a1, ..., ak)` ; a different object is created each time. |
| `ReturnNull()` | Return a null pointer. |
| `ReturnPointee(ptr)` | Return the value pointed to by `ptr` . |
| `ReturnRef(variable)` | Return a reference to `variable` . |
| `ReturnRefOfCopy(value)` | Return a reference to a copy of `value` ; the copy lives as long as the action. |
| `ReturnRoundRobin({a1, ..., ak})` | Each call will return the next `ai` in the list, starting at the beginning when the end of the list is reached. |
2019-07-17 15:35:48 -04:00
2020-06-25 11:56:24 -04:00
### Side Effects
2019-07-17 15:35:48 -04:00
2019-07-29 10:53:47 -04:00
| | |
2019-07-17 15:35:48 -04:00
| :--------------------------------- | :-------------------------------------- |
2019-08-02 10:58:20 -04:00
| `Assign(&variable, value)` | Assign `value` to variable. |
| `DeleteArg<N>()` | Delete the `N` -th (0-based) argument, which must be a pointer. |
| `SaveArg<N>(pointer)` | Save the `N` -th (0-based) argument to `*pointer` . |
| `SaveArgPointee<N>(pointer)` | Save the value pointed to by the `N` -th (0-based) argument to `*pointer` . |
2020-11-24 10:30:01 -05:00
| `SetArgReferee<N>(value)` | Assign `value` to the variable referenced by the `N` -th (0-based) argument. |
2019-08-02 10:58:20 -04:00
| `SetArgPointee<N>(value)` | Assign `value` to the variable pointed by the `N` -th (0-based) argument. |
| `SetArgumentPointee<N>(value)` | Same as `SetArgPointee<N>(value)` . Deprecated. Will be removed in v1.7.0. |
| `SetArrayArgument<N>(first, last)` | Copies the elements in source range [`first`, `last` ) to the array pointed to by the `N` -th (0-based) argument, which can be either a pointer or an iterator. The action does not take ownership of the elements in the source range. |
| `SetErrnoAndReturn(error, value)` | Set `errno` to `error` and return `value` . |
| `Throw(exception)` | Throws the given exception, which can be any copyable value. Available since v1.1.0. |
2019-07-17 15:35:48 -04:00
2020-06-25 11:56:24 -04:00
### Using a Function, Functor, or Lambda as an Action
2019-07-17 15:35:48 -04:00
In the following, by "callable" we mean a free function, `std::function` ,
2019-08-01 15:04:08 -04:00
functor, or lambda.
2019-07-17 15:35:48 -04:00
2019-07-29 10:53:47 -04:00
| | |
2019-07-17 15:35:48 -04:00
| :---------------------------------- | :------------------------------------- |
2019-08-02 10:58:20 -04:00
| `f` | Invoke f with the arguments passed to the mock function, where f is a callable. |
| `Invoke(f)` | Invoke `f` with the arguments passed to the mock function, where `f` can be a global/static function or a functor. |
| `Invoke(object_pointer, &class::method)` | Invoke the method on the object with the arguments passed to the mock function. |
| `InvokeWithoutArgs(f)` | Invoke `f` , which can be a global/static function or a functor. `f` must take no arguments. |
| `InvokeWithoutArgs(object_pointer, &class::method)` | Invoke the method on the object, which takes no arguments. |
| `InvokeArgument<N>(arg1, arg2, ..., argk)` | Invoke the mock function's `N` -th (0-based) argument, which must be a function or a functor, with the `k` arguments. |
2019-07-17 15:35:48 -04:00
The return value of the invoked function is used as the return value of the
action.
When defining a callable to be used with `Invoke*()` , you can declare any unused
parameters as `Unused` :
2015-08-24 18:41:02 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2019-07-17 15:35:48 -04:00
using ::testing::Invoke;
double Distance(Unused, double x, double y) { return sqrt(x*x + y*y); }
...
EXPECT_CALL(mock, Foo("Hi", _, _ )).WillOnce(Invoke(Distance));
2015-08-24 18:41:02 -04:00
```
2019-07-17 15:35:48 -04:00
`Invoke(callback)` and `InvokeWithoutArgs(callback)` take ownership of
`callback` , which must be permanent. The type of `callback` must be a base
callback type instead of a derived one, e.g.
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
```cpp
BlockingClosure* done = new BlockingClosure;
... Invoke(done) ...; // This won't compile!
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
Closure* done2 = new BlockingClosure;
... Invoke(done2) ...; // This works.
```
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
In `InvokeArgument<N>(...)` , if an argument needs to be passed by reference,
2020-07-07 12:47:27 -04:00
wrap it inside `std::ref()` . For example,
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
```cpp
using ::testing::InvokeArgument;
...
2020-07-07 12:47:27 -04:00
InvokeArgument< 2 > (5, string("Hi"), std::ref(foo))
2019-07-17 15:35:48 -04:00
```
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
calls the mock function's #2 argument, passing to it `5` and `string("Hi")` by
value, and `foo` by reference.
2020-06-25 11:56:24 -04:00
### Default Action
2019-07-17 15:35:48 -04:00
| Matcher | Description |
| :------------ | :----------------------------------------------------- |
2019-08-02 10:58:20 -04:00
| `DoDefault()` | Do the default action (specified by `ON_CALL()` or the built-in one). |
2019-07-17 15:35:48 -04:00
2021-02-18 19:18:34 -05:00
{: .callout .note}
2019-07-17 15:35:48 -04:00
**Note:** due to technical reasons, `DoDefault()` cannot be used inside a
composite action - trying to do so will result in a run-time error.
2020-06-25 11:56:24 -04:00
### Composite Actions
2019-07-29 10:53:47 -04:00
| | |
2019-07-17 15:35:48 -04:00
| :----------------------------- | :------------------------------------------ |
2020-08-17 12:07:02 -04:00
| `DoAll(a1, a2, ..., an)` | Do all actions `a1` to `an` and return the result of `an` in each invocation. The first `n - 1` sub-actions must return void and will receive a readonly view of the arguments. |
2019-08-02 10:58:20 -04:00
| `IgnoreResult(a)` | Perform action `a` and ignore its result. `a` must not return void. |
| `WithArg<N>(a)` | Pass the `N` -th (0-based) argument of the mock function to action `a` and perform it. |
| `WithArgs<N1, N2, ..., Nk>(a)` | Pass the selected (0-based) arguments of the mock function to action `a` and perform it. |
| `WithoutArgs(a)` | Perform action `a` without any arguments. |
2019-07-17 15:35:48 -04:00
2020-06-25 11:56:24 -04:00
### Defining Actions
2019-07-29 10:53:47 -04:00
| | |
2019-07-17 15:35:48 -04:00
| :--------------------------------- | :-------------------------------------- |
2019-08-02 10:58:20 -04:00
| `ACTION(Sum) { return arg0 + arg1; }` | Defines an action `Sum()` to return the sum of the mock function's argument #0 and #1 . |
| `ACTION_P(Plus, n) { return arg0 + n; }` | Defines an action `Plus(n)` to return the sum of the mock function's argument #0 and `n` . |
| `ACTION_Pk(Foo, p1, ..., pk) { statements; }` | Defines a parameterized action `Foo(p1, ..., pk)` to execute the given `statements` . |
2015-08-24 18:41:02 -04:00
The `ACTION*` macros cannot be used inside a function or class.
2020-06-25 11:56:24 -04:00
## Cardinalities {#CardinalityList}
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
These are used in `Times()` to specify how many times a mock function will be
called:
2015-08-24 18:41:02 -04:00
2019-07-29 10:53:47 -04:00
| | |
2019-07-17 15:35:48 -04:00
| :---------------- | :----------------------------------------------------- |
| `AnyNumber()` | The function can be called any number of times. |
| `AtLeast(n)` | The call is expected at least `n` times. |
| `AtMost(n)` | The call is expected at most `n` times. |
2019-08-02 10:58:20 -04:00
| `Between(m, n)` | The call is expected between `m` and `n` (inclusive) times. |
| `Exactly(n) or n` | The call is expected exactly `n` times. In particular, the call should never happen when `n` is 0. |
2015-08-24 18:41:02 -04:00
2020-06-25 11:56:24 -04:00
## Expectation Order
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
By default, the expectations can be matched in *any* order. If some or all
expectations must be matched in a given order, there are two ways to specify it.
They can be used either independently or together.
2015-08-24 18:41:02 -04:00
2020-06-25 11:56:24 -04:00
### The After Clause {#AfterClause}
2015-08-24 18:41:02 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2015-08-24 18:41:02 -04:00
using ::testing::Expectation;
...
Expectation init_x = EXPECT_CALL(foo, InitX());
Expectation init_y = EXPECT_CALL(foo, InitY());
EXPECT_CALL(foo, Bar())
2019-07-17 15:35:48 -04:00
.After(init_x, init_y);
2015-08-24 18:41:02 -04:00
```
2019-07-17 15:35:48 -04:00
says that `Bar()` can be called only after both `InitX()` and `InitY()` have
been called.
If you don't know how many pre-requisites an expectation has when you write it,
you can use an `ExpectationSet` to collect them:
2015-08-24 18:41:02 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2015-08-24 18:41:02 -04:00
using ::testing::ExpectationSet;
...
ExpectationSet all_inits;
for (int i = 0; i < element_count ; i + + ) {
all_inits += EXPECT_CALL(foo, InitElement(i));
}
EXPECT_CALL(foo, Bar())
2019-07-17 15:35:48 -04:00
.After(all_inits);
2015-08-24 18:41:02 -04:00
```
2019-07-17 15:35:48 -04:00
says that `Bar()` can be called only after all elements have been initialized
(but we don't care about which elements get initialized before the others).
Modifying an `ExpectationSet` after using it in an `.After()` doesn't affect the
meaning of the `.After()` .
2015-08-24 18:41:02 -04:00
2020-06-25 11:56:24 -04:00
### Sequences {#UsingSequences}
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
When you have a long chain of sequential expectations, it's easier to specify
2021-04-26 14:30:13 -04:00
the order using **sequences** , which don't require you to give each expectation
2019-07-17 15:35:48 -04:00
in the chain a different name. *All expected calls* in the same sequence must
occur in the order they are specified.
2015-08-24 18:41:02 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2019-07-17 15:35:48 -04:00
using ::testing::Return;
2015-08-24 18:41:02 -04:00
using ::testing::Sequence;
Sequence s1, s2;
...
EXPECT_CALL(foo, Reset())
.InSequence(s1, s2)
.WillOnce(Return(true));
EXPECT_CALL(foo, GetSize())
.InSequence(s1)
.WillOnce(Return(1));
EXPECT_CALL(foo, Describe(A< const char * > ()))
.InSequence(s2)
.WillOnce(Return("dummy"));
```
2019-07-17 15:35:48 -04:00
says that `Reset()` must be called before *both* `GetSize()` *and* `Describe()` ,
and the latter two can occur in any order.
2015-08-24 18:41:02 -04:00
To put many expectations in a sequence conveniently:
2019-07-17 15:35:48 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2015-08-24 18:41:02 -04:00
using ::testing::InSequence;
{
2019-07-17 15:35:48 -04:00
InSequence seq;
2015-08-24 18:41:02 -04:00
EXPECT_CALL(...)...;
EXPECT_CALL(...)...;
...
EXPECT_CALL(...)...;
}
```
2019-07-17 15:35:48 -04:00
says that all expected calls in the scope of `seq` must occur in strict order.
The name `seq` is irrelevant.
2020-06-25 11:56:24 -04:00
## Verifying and Resetting a Mock
2019-07-17 15:35:48 -04:00
gMock will verify the expectations on a mock object when it is destructed, or
you can do it earlier:
2015-08-24 18:41:02 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2015-08-24 18:41:02 -04:00
using ::testing::Mock;
...
// Verifies and removes the expectations on mock_obj;
2019-08-12 07:09:50 +02:00
// returns true if and only if successful.
2015-08-24 18:41:02 -04:00
Mock::VerifyAndClearExpectations(&mock_obj);
...
// Verifies and removes the expectations on mock_obj;
// also removes the default actions set by ON_CALL();
2019-08-12 07:09:50 +02:00
// returns true if and only if successful.
2015-08-24 18:41:02 -04:00
Mock::VerifyAndClear(&mock_obj);
```
2019-07-17 15:35:48 -04:00
You can also tell gMock that a mock object can be leaked and doesn't need to be
verified:
2018-09-03 21:56:23 +03:00
```cpp
2015-08-24 18:41:02 -04:00
Mock::AllowLeak(&mock_obj);
```
2020-06-25 11:56:24 -04:00
## Mock Classes
2019-07-17 15:35:48 -04:00
gMock defines a convenient mock class template
2015-08-24 18:41:02 -04:00
2018-09-03 21:56:23 +03:00
```cpp
2015-08-24 18:41:02 -04:00
class MockFunction< R ( A1 , . . . , An ) > {
public:
2019-07-17 15:35:48 -04:00
MOCK_METHOD(R, Call, (A1, ..., An));
2015-08-24 18:41:02 -04:00
};
```
2019-07-17 15:35:48 -04:00
2021-01-22 13:49:00 -05:00
See this [recipe ](gmock_cook_book.md#using-check-points ) for one application of
it.
2015-08-24 18:41:02 -04:00
2020-06-25 11:56:24 -04:00
## Flags
2015-08-24 18:41:02 -04:00
2019-07-17 15:35:48 -04:00
| Flag | Description |
| :----------------------------- | :---------------------------------------- |
2019-08-02 10:58:20 -04:00
| `--gmock_catch_leaked_mocks=0` | Don't report leaked mock objects as failures. |
| `--gmock_verbose=LEVEL` | Sets the default verbosity level (`info`, `warning` , or `error` ) of Google Mock messages. |