Home
last modified time | relevance | path

Searched refs:matchers (Results 1 – 25 of 28) sorted by relevance

12

/freebsd/lib/googletest/tests/gmock_main/
H A DMakefile9 GTESTS+= gmock-matchers-arithmetic_test
10 GTESTS+= gmock-matchers-comparisons_test
11 GTESTS+= gmock-matchers-containers_test
12 GTESTS+= gmock-matchers-misc_test
/freebsd/contrib/googletest/docs/reference/
H A Dmocking.md60 `EXPECT_CALL(`*`mock_object`*`,`*`method_name`*`(`*`matchers...`*`))`
64 that match the given matchers *`matchers...`*. `EXPECT_CALL` must precede any
67 The parameter *`matchers...`* is a comma-separated list of
68 [matchers](../gmock_for_dummies.md#matchers-what-arguments-do-we-expect) that
71 matchers. If `(`*`matchers...`*`)` is omitted, the expectation behaves as if
72 each argument's matcher were a [wildcard matcher (`_`)](matchers.md#wildcard).
73 See the [Matchers Reference](matchers.md) for a list of all built-in matchers.
79 EXPECT_CALL(mock_object, method_name(matchers...))
115 GoogleTest provides some built-in matchers for 2-tuples, including the `Lt()`
116 matcher above. See [Multi-argument Matchers](matchers.md#MultiArgMatchers).
[all …]
H A Dmatchers.md21 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…
[all …]
H A Dassertions.md76 The following assertion allows [matchers](matchers.md) to be used to verify
84 Verifies that *`value`* matches the [matcher](matchers.md) *`matcher`*.
115 GoogleTest provides a built-in library of matchers—see the
116 [Matchers Reference](matchers.md). It is also possible to write your own
117 matchers—see [Writing New Matchers Quickly](../gmock_cook_book.md#NewMatchers).
118 The use of matchers makes `EXPECT_THAT` a powerful, extensible assertion.
568 The parameter *`matcher`* is either a [matcher](matchers.md) for a `const
572 [`ContainsRegex(s)`](matchers.md#string-matchers), **not**
573 [`Eq(s)`](matchers.md#generic-comparison).
620 The parameter *`matcher`* is either a [matcher](matchers.md) for a `const
[all …]
/freebsd/contrib/googletest/googlemock/test/
H A Dgmock-internal-utils_test.cc292 std::tuple<> matchers; in TEST() local
295 EXPECT_TRUE(TupleMatches(matchers, values)); in TEST()
299 std::tuple<Matcher<int>> matchers(Eq(1)); in TEST() local
302 EXPECT_TRUE(TupleMatches(matchers, values1)); in TEST()
303 EXPECT_FALSE(TupleMatches(matchers, values2)); in TEST()
307 std::tuple<Matcher<int>, Matcher<char>> matchers(Eq(1), Eq('a')); in TEST() local
311 EXPECT_TRUE(TupleMatches(matchers, values1)); in TEST()
312 EXPECT_FALSE(TupleMatches(matchers, values2)); in TEST()
313 EXPECT_FALSE(TupleMatches(matchers, values3)); in TEST()
314 EXPECT_FALSE(TupleMatches(matchers, values4)); in TEST()
[all …]
H A Dgmock-matchers-misc_test.cc1506 std::vector<Matcher<int>> matchers{Ge(1), Lt(2)}; in TEST() local
1507 EXPECT_THAT(0, Not(AllOfArray(matchers))); in TEST()
1508 EXPECT_THAT(1, AllOfArray(matchers)); in TEST()
1509 EXPECT_THAT(2, Not(AllOfArray(matchers))); in TEST()
1560 std::vector<Matcher<int>> matchers{Lt(1), Ge(2)}; in TEST() local
1561 EXPECT_THAT(0, AnyOfArray(matchers)); in TEST()
1562 EXPECT_THAT(1, Not(AnyOfArray(matchers))); in TEST()
1563 EXPECT_THAT(2, AnyOfArray(matchers)); in TEST()
/freebsd/lib/googletest/gmock/
H A DMakefile22 MAIN_INCS+= gmock/gmock-matchers.h
24 MAIN_INCS+= gmock/gmock-more-matchers.h
36 INTERNAL_CUSTOM_INCS+= gmock/internal/custom/gmock-matchers.h
/freebsd/contrib/llvm-project/clang/include/
H A Dmodule.modulemap14 // FIXME: Exclude these headers to avoid pulling all of the AST matchers
16 // importing the AST matchers library gives a link dependency on the AST
17 // matchers (and thus the AST), which clang-format should not have.
193 // FIXME: Exclude these headers to avoid pulling all of the AST matchers
195 // importing the AST matchers library gives a link dependency on the AST
196 // matchers (and thus the AST), which clang-format should not have.
/freebsd/contrib/googletest/googlemock/include/gmock/
H A Dgmock-matchers.h630 static void ExplainMatchFailuresTo(const MatcherTuple& matchers, in ExplainMatchFailuresTo() argument
634 TuplePrefix<N - 1>::ExplainMatchFailuresTo(matchers, values, os); in ExplainMatchFailuresTo()
639 std::get<N - 1>(matchers); in ExplainMatchFailuresTo()
645 std::get<N - 1>(matchers).DescribeTo(os); in ExplainMatchFailuresTo()
695 void ExplainMatchFailureTupleTo(const MatcherTuple& matchers, in ExplainMatchFailureTupleTo() argument
698 matchers, values, os); in ExplainMatchFailureTupleTo()
1280 explicit AllOfMatcherImpl(std::vector<Matcher<T>> matchers)
1281 : matchers_(std::move(matchers)) {}
1341 VariadicMatcher(const Args&... matchers) // NOLINT
1342 : matchers_(matchers...) {
[all …]
H A Dgmock-spec-builders.h289 const ArgumentMatcherTuple& matchers) in OnCallSpec() argument
291 matchers_(matchers), in OnCallSpec()
1073 const ArgumentMatcherTuple& matchers() const { return matchers_; } in matchers() function
1291 const ArgumentMatcherTuple& matchers) in MockSpec() argument
1292 : function_mocker_(function_mocker), matchers_(matchers) {} in MockSpec()
/freebsd/contrib/googletest/googlemock/
H A DREADME.md22 - Comes with a rich set of matchers for validating function arguments.
27 - Lets a user extend it by defining new matchers and actions.
H A DCMakeLists.txt146 cxx_test(gmock-matchers-arithmetic_test gmock_main)
147 cxx_test(gmock-matchers-comparisons_test gmock_main)
148 cxx_test(gmock-matchers-containers_test gmock_main)
149 cxx_test(gmock-matchers-misc_test gmock_main)
/freebsd/contrib/llvm-project/compiler-rt/lib/xray/
H A Dxray_always_instrument.txt1 # List of function matchers common to C/C++ applications that make sense to
H A Dxray_never_instrument.txt1 # List of function matchers common to C/C++ applications that make sense to
/freebsd/contrib/googletest/docs/
H A Dindex.md20 matchers, actions, invariants, and more.
H A Dgmock_for_dummies.md296 EXPECT_CALL(mock_object, method(matchers))
305 If the method is not overloaded, the macro can also be called without matchers:
369 `_` is an instance of what we call **matchers**. A matcher is like a predicate
374 In the above examples, `100` and `50` are also matchers; implicitly, they are
377 [built-in matchers](reference/matchers.md) for common types (as well as
378 [custom matchers](gmock_cook_book.md#NewMatchers)); for example:
556 one with more specific matchers **after** the other, or the more specific rule
H A Dgmock_cook_book.md556 argument matchers:
862 You can use matchers to match arguments that have a certain property:
882 You can build complex matchers from existing ones using `AllOf()`,
901 Matchers are function objects, and parametrized matchers can be composed just
919 gMock matchers are statically typed, meaning that the compiler can catch your
1091 matchers.
1093 As a convenience and example, gMock provides some matchers for 2-tuples,
1095 [Multi-argument Matchers](reference/matchers.md#MultiArgMatchers) for the
1108 matchers were not allowed to participate.
1126 Since you can build complex matchers from simpler ones easily using gMock, this
[all …]
H A Dgmock_cheat_sheet.md173 See the [Matchers Reference](reference/matchers.md).
H A Dfaq.md92 significant advantage of the matcher approach is that matchers can be easily
93 combined to form new matchers, while the `EXPECT_NE`, etc, macros cannot be
94 easily combined. Therefore we want to invest more in the matchers than in the
H A Dadvanced.md177 (Please read the [previous](#asserting-using-gmock-matchers) section first if
180 You can use the gMock [string matchers](reference/matchers.md#string-matchers)
/freebsd/lib/googletest/gtest/
H A DMakefile17 MAIN_INCS+= gtest/gtest-matchers.h
/freebsd/contrib/llvm-project/llvm/lib/Target/AMDGPU/
H A DAMDGPUCombine.td132 // FIXME: Should have ComplexPattern like in/out matchers
/freebsd/contrib/llvm-project/llvm/utils/TableGen/Common/GlobalISel/
H A DGlobalISelMatchTable.h376 iterator_range<std::vector<Matcher *>::iterator> matchers() { in matchers() function
428 iterator_range<std::vector<Matcher *>::iterator> matchers() { in matchers() function
H A DGlobalISelMatchTable.cpp112 append_range(OptRules, CurrentGroup->matchers()); in optimizeRules()
/freebsd/contrib/llvm-project/llvm/lib/Target/PowerPC/
H A DPPCRegisterInfo.td523 // for the asm parser does not work, and we need to specify custom matchers.

12