Googletest export
Address OSS Issue #2463 https://github.com/google/googletest/issues/2463 PiperOrigin-RevId: 333289989
This commit is contained in:
parent
634c52d99c
commit
df94fc5f7e
@ -1132,10 +1132,11 @@ Hamcrest project, which adds `assertThat()` to JUnit.
|
||||
|
||||
### Using Predicates as Matchers
|
||||
|
||||
gMock provides a [built-in set](#MatcherList) of matchers. In case you find them
|
||||
lacking, you can use an arbitrary unary predicate function or functor as a
|
||||
matcher - as long as the predicate accepts a value of the type you want. You do
|
||||
this by wrapping the predicate inside the `Truly()` function, for example:
|
||||
gMock provides a [built-in set](cheat_sheet.md#MatcherList) of matchers. In case
|
||||
you find them lacking, you can use an arbitrary unary predicate function or
|
||||
functor as a matcher - as long as the predicate accepts a value of the type you
|
||||
want. You do this by wrapping the predicate inside the `Truly()` function, for
|
||||
example:
|
||||
|
||||
```cpp
|
||||
using ::testing::Truly;
|
||||
|
@ -371,9 +371,11 @@ Verifies that `val1` is less than, or almost equal to, `val2`. You can replace
|
||||
|
||||
### Asserting Using gMock Matchers
|
||||
|
||||
[gMock](../../googlemock) comes with a library of matchers for validating
|
||||
arguments passed to mock objects. A gMock *matcher* is basically a predicate
|
||||
that knows how to describe itself. It can be used in these assertion macros:
|
||||
[gMock](../../googlemock) comes with
|
||||
[a library of matchers](../../googlemock/docs/cheat_sheet.md#MatcherList) for
|
||||
validating arguments passed to mock objects. A gMock *matcher* is basically a
|
||||
predicate that knows how to describe itself. It can be used in these assertion
|
||||
macros:
|
||||
|
||||
<!-- mdformat off(github rendering does not support multiline tables) -->
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user