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
881 ## Using Matchers as Predicates ##
886 it would be a shame if Google Mock matchers are not allowed to
902 Since you can build complex matchers from simpler ones easily using
912 ## Using Matchers in Google Test Assertions ##
914 Since matchers are basically predicates that also know how to describe
962 ## Using Predicates as Matchers ##
964 Google Mock provides a built-in set of matchers. In case you find them
991 matchers like `Eq(bar)`, `Le(bar)`, and so on.
1062 C++ functions often take pointers as arguments. You can use matchers
1063 like `NULL`, `NotNull()`, and other comparison matchers to match a
1188 // Or, an array of element matchers.
1212 ## Sharing Matchers ##
1215 a ref-counted implementation object. Copying matchers is allowed and
1277 matchers in the third `EXPECT_CALL()`, but not those in the first two,
2097 Just like matchers, a Google Mock action object consists of a pointer
2513 ## Writing New Matchers Quickly ##
2515 The `MATCHER*` family of macros can be used to define custom matchers
2610 ## Writing New Parameterized Matchers Quickly ##
2644 `MATCHER_P10` to support multi-parameter matchers:
2706 useful when composing matchers. Matchers that don't have a parameter
2718 You can overload matchers with different numbers of parameters:
2731 that pay off in the long run. They also allow overloading matchers
2735 ## Writing New Monomorphic Matchers ##
2839 ## Writing New Polymorphic Matchers ##
2841 You've learned how to write your own matchers in the previous
2847 you can learn the trick from `"gmock/gmock-matchers.h"` but it's a bit
