mirror of
https://github.com/google/googletest.git
synced 2025-12-27 18:27:43 +08:00
065127f1e4
`EXPECT_THAT(foo, Matcher(bar))` can sometimes get accidentally written as a no-op `foo, Matcher(bar)`, causing the code to be exercised but defeating the purpose of testing. PiperOrigin-RevId: 841880995 Change-Id: Ia55548e3dd83a6f44fff7b5433c8c8ecd7ecbe03
Googletest Mocking (gMock) Framework
Overview
Google's framework for writing and using C++ mock classes. It can help you derive better designs of your system and write better tests.
It is inspired by:
It is designed with C++'s specifics in mind.
gMock:
- Provides a declarative syntax for defining mocks.
- Can define partial (hybrid) mocks, which are a cross of real and mock objects.
- Handles functions of arbitrary types and overloaded functions.
- Comes with a rich set of matchers for validating function arguments.
- Uses an intuitive syntax for controlling the behavior of a mock.
- Does automatic verification of expectations (no record-and-replay needed).
- Allows arbitrary (partial) ordering constraints on function calls to be expressed.
- Lets a user extend it by defining new matchers and actions.
- Does not use exceptions.
- Is easy to learn and use.
Details and examples can be found here:
GoogleMock is a part of GoogleTest C++ testing framework and a subject to the same requirements.