googletest/googlemock
Daniel Cheng b479e7a3c1 Guard Abseil flags usage in googlemock with GTEST_NO_ABSL_FLAGS.
googletest avoids using the Abseil flag library, so googlemock should
do the same for consistency.

PiperOrigin-RevId: 614713968
Change-Id: I0925804b8644ddc6fd3ad07a320d94829b11bb8e
2024-03-11 10:31:56 -07:00
..
cmake Ensure that gtest/gmock pkgconfig requirements specify version 2020-03-21 06:38:09 -04:00
docs Googletest export 2021-01-13 20:59:12 -05:00
include/gmock Guard Abseil flags usage in googlemock with GTEST_NO_ABSL_FLAGS. 2024-03-11 10:31:56 -07:00
src Use _Exit instead of _exit in GoogleTest 2024-02-07 09:01:25 -08:00
test Accept one-shot callables in InvokeArgument. 2024-02-29 07:42:26 -08:00
CMakeLists.txt Get include dirs from target rather than global variables. 2024-02-11 18:50:28 +01:00
README.md Merge pull request #4349 from sthd:httpToHttps 2023-08-23 09:30:13 -07:00

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.