Lines Matching refs:matchers

21 Built-in matchers (where `argument` is the function argument, e.g.
23 `EXPECT_CALL(mock_object, method(matchers))`, the arguments of `method`) are
24 divided into several categories. All matchers are defined in the `::testing`
53 Except `Ref()`, these matchers make a *copy* of `value` in case it's modified or
75 The above matchers use ULP-based comparison (the same as used in googletest).
109 [here](../advanced.md#regular-expression-syntax). All of these matchers, except
127 …` | The same as `ElementsAre()` except that the expected element values/matchers come from an init…
129 …rderedElementsAre(x0, x1, ..., xk)` for some subset `{x0, x1, ..., xk}` of the expected matchers. |
130 …f(array, count)` | Some subset of `argument` matches `UnorderedElementsAre(`expected matchers`)`. |
134 …ame as `UnorderedElementsAre()` except that the expected element values/matchers come from an init…
141 *   These matchers can also match:
170 …ent` is a compatible object where each field matches piecewise with the matchers `m...`. A compati…
214 Technically, all matchers match a *single* value. A "multi-argument" matcher is
215 just one that matches a *tuple*. The following matchers can be used to match a
237 You can make a matcher from one or more other matchers:
241 | `AllOf(m1, m2, ..., mn)` | `argument` matches all of the matchers `m1` to `mn`. |
242 …, or `AllOfArray(array, count)` | The same as `AllOf()` except that the matchers come from an init…
243 | `AnyOf(m1, m2, ..., mn)` | `argument` matches at least one of the matchers `m1` to `mn`. |
244 …, or `AnyOfArray(array, count)` | The same as `AnyOf()` except that the matchers come from an init…