Lines Matching refs:MockFoo

39 // Given a mock class MockFoo that is created using Google Mock,
40 // NiceMock<MockFoo> is a subclass of MockFoo that allows
42 // EXPECT_CALL specs), NaggyMock<MockFoo> is a subclass of MockFoo
44 // StrictMock<MockFoo> is a subclass of MockFoo that treats all
47 // Currently a mock is naggy by default, so MockFoo and
48 // NaggyMock<MockFoo> behave like the same.  However, we will soon
50 // leads to more maintainable tests.  When that happens, MockFoo will
51 // stop behaving like NaggyMock<MockFoo> and start behaving like
52 // NiceMock<MockFoo>.
56 // you can write NiceMock<MockFoo>(5, "a") to construct a nice mock
57 // where MockFoo has a constructor that accepts (int, const char*),
60 // A known limitation is that NiceMock<MockFoo>, NaggyMock<MockFoo>,
61 // and StrictMock<MockFoo> only works for mock methods defined using
62 // the MOCK_METHOD* family of macros DIRECTLY in the MockFoo class.
63 // If a mock method is defined in a base class of MockFoo, the "nice"