Lines Matching refs:Sometimes

493 Sometimes a method has a long list of arguments that is mostly uninteresting.
818 Sometimes you may want to call `Foo::Concrete()` instead of
923 Sometimes, however, you know what you're doing and want the compiler to give you
1053 Sometimes it's not enough to match the arguments individually. For example, we
1357 Sometimes an STL container (e.g. list, vector, map, ...) is passed to a mock
1362 Sometimes, though, you may want to be more flexible (for example, the first
1716 Sometimes requiring everything to occur in a predetermined order can lead to
1850 always returns the same value whenever it's executed. Sometimes you may want to
1962 Sometimes a method exhibits its effect not via returning a value but via side
2111 Sometimes, you may want to change this default value, or you may want to specify
2250 arguments as the mock function you use it for. Sometimes you may have a function
2336 Sometimes a mock function will receive a function pointer, a functor (in other
2435 Sometimes you have an action that returns *something*, but you need an action
2994 Sometimes you might want to test a mock object's behavior in phases whose sizes
3043 Sometimes you want to make sure a mock object is destructed at the right time,
3156 Sometimes you are confident that your tests are correct and may not appreciate
3433 Sometimes you'll want to define a matcher that has parameters. For that you can
4000 Sometimes you'll want to parameterize an action you define. For that we have
4063 Sometimes, however, we may want to be more explicit about the types. There are
4087 Sometimes you want to give an action explicit template parameters that cannot be
4238 be used. Sometimes that can be a problem. For example, if you want to use the