organicmaps/googletest
13
Fork 0
mirror of https://github.com/google/googletest.git synced 2025-04-04 21:15:03 +00:00
Code Issues 1 Projects Releases Wiki Activity Actions

Merge 15de0806de into 52204f78f9

Browse source
This commit is contained in:
XAMeLeOH 2025-03-30 14:21:40 +00:00 • committed by GitHub
commit f3710f77be
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 11 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/reference/actions.md
View file

@ -1,8 +1,10 @@
# Actions Reference
[**Actions**](../gmock_for_dummies.md#actions-what-should-it-do) specify what a
mock function should do when invoked. This page lists the built-in actions
provided by GoogleTest. All actions are defined in the `::testing` namespace.
mock function should do when invoked.
This page lists the built-in actions provided by GoogleTest.
To use them, add #include <gmock/gmock.h>.
All actions are defined in the `::testing` namespace.
## Returning a Value

10
docs/reference/matchers.md
View file

@ -1,6 +1,11 @@
# Matchers Reference
A **matcher** matches a *single* argument. You can use it inside `ON_CALL()` or
A **matcher** matches a *single* argument.
This page lists the built-in matchers provided by GoogleTest.
To use them, add `#include <gtest/gtest.h>`.
All matchers are defined in the `::testing` namespace unless otherwise noted.
You can use a matcher inside `ON_CALL()` or
`EXPECT_CALL()`, or use it to validate a value directly using two macros:
| Macro | Description |
@ -21,8 +26,7 @@ expected_value)`.
Built-in matchers (where `argument` is the function argument, e.g.
`actual_value` in the example above, or when used in the context of
`EXPECT_CALL(mock_object, method(matchers))`, the arguments of `method`) are
divided into several categories. All matchers are defined in the `::testing`
namespace unless otherwise noted.
divided into several categories.
## Wildcard