outman/googletest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update matchers.md: include and namespace instructions

Browse Source 
* Added a note on which header to include to use the built-in matchers to the top of the page.
* Moved a sentence about the namespace to the top of the page.
This commit is contained in:
XAMeLeOH 2024-09-26 00:16:25 +02:00 committed by GitHub
parent 6dae7eb4a5
commit a8b80f122b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/reference/matchers.md
View File

@ -1,6 +1,11 @@
# Matchers Reference # 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: `EXPECT_CALL()`, or use it to validate a value directly using two macros:
| Macro | Description | | Macro | Description |
@ -21,8 +26,7 @@ expected_value)`.
Built-in matchers (where `argument` is the function argument, e.g. Built-in matchers (where `argument` is the function argument, e.g.
`actual_value` in the example above, or when used in the context of `actual_value` in the example above, or when used in the context of
`EXPECT_CALL(mock_object, method(matchers))`, the arguments of `method`) are `EXPECT_CALL(mock_object, method(matchers))`, the arguments of `method`) are
divided into several categories. All matchers are defined in the `::testing` divided into several categories.
namespace unless otherwise noted.
## Wildcard ## Wildcard