Lines Matching full:matchers
632 # Using Matchers #
646 ## Using Simple Matchers ##
648 You can use matchers to match arguments that have a certain property:
670 ## Combining Matchers ##
672 You can build complex matchers from existing ones using `AllOf()`,
691 ## Casting Matchers ##
693 Google Mock matchers are statically typed, meaning that the compiler
872 As a convenience and example, Google Mock provides some matchers for
876 ## Using Matchers as Predicates ##
881 it would be a shame if Google Mock matchers are not allowed to
897 Since you can build complex matchers from simpler ones easily using
907 ## Using Matchers in Google Test Assertions ##
909 Since matchers are basically predicates that also know how to describe
957 ## Using Predicates as Matchers ##
959 Google Mock provides a built-in set of matchers. In case you find them
986 matchers like `Eq(bar)`, `Le(bar)`, and so on.
1057 C++ functions often take pointers as arguments. You can use matchers
1058 like `NULL`, `NotNull()`, and other comparison matchers to match a
1183 // Or, an array of element matchers.
1207 ## Sharing Matchers ##
1210 a ref-counted implementation object. Copying matchers is allowed and
1272 matchers in the third `EXPECT_CALL()`, but not those in the first two,
2029 Just like matchers, a Google Mock action object consists of a pointer
2382 ## Writing New Matchers Quickly ##
2384 The `MATCHER*` family of macros can be used to define custom matchers
2459 ## Writing New Parameterized Matchers Quickly ##
2491 `MATCHER_P10` to support multi-parameter matchers:
2555 useful when composing matchers. Matchers that don't have a parameter
2567 You can overload matchers with different numbers of parameters:
2580 that pay off in the long run. They also allow overloading matchers
2584 ## Writing New Monomorphic Matchers ##
2688 ## Writing New Polymorphic Matchers ##
2690 You've learned how to write your own matchers in the previous
2696 you can learn the trick from `<gmock/gmock-matchers.h>` but it's a bit
