Lines Matching full:just
164 You can mock class templates just like any class.
192 mocking virtual methods (just don't add `override`):
594 functionalities, rename stuff, etc instead of just trimming the class. This
612 just like they have been sharing `Concrete`. You can check in the interface
677 With that, you can use `MockFoo` in your tests as usual. Just remember that if
730 to test how your code uses `System` to do I/O, and you just want the file
838 (Why don't we just write `{ return foo.Concrete(str); }`? If you do that,
840 `Foo::Concrete()` is virtual. That's just how C++ works.)
897 Matchers are function objects, and parametrized matchers can be composed just
1101 Have you noticed that a matcher is just a fancy predicate that also knows how to
1124 using STL's `<functional>` header is just painful). For example, here's a
1176 executed. Just tell gMock that it should save a reference to `bar`, instead of a
1441 `begin()/end()`), not just the ones defined in STL. It will even work with
1446 * If the container is passed by pointer instead of by reference, just write
1460 again, there is no need to build it every time. Just assign it to a matcher
1520 wrong just from the test log itself.
1541 If you are not interested in how a mock method is called, just don't say
1563 If some calls to the method are allowed, but the rest are not, just list all the
1730 DAG into sequences, we just need to know which sequences each `EXPECT_CALL()`
1936 // just the method wasn't called.
2377 What if the callable takes an argument by reference? No problem - just wrap it
2529 As you may have realized, `InvokeWithoutArgs(...)` is just syntactic sugar for
2604 Just like matchers, a gMock action object consists of a pointer to a ref-counted
2664 events on a background thread, which made test timings difficult. You could just
2689 additional action to notify the `Notification` object. Now we can just call
2740 To mock a method that accepts or returns move-only types, you just use the
2780 If you just need to return a pre-defined move-only value, you can use the
2801 If you need your mock method to do more than just moving a pre-defined value,
2846 of this feature (it is no longer necessary - we're including it just for
3261 errors will be highlighted. Just press `<Enter>` on one of them and you'll be
3262 taken to the offending line. Or, you can just type `C-x`` to jump to the next
3274 just make sure `foo_test.run` or `runtests` is in the build command you supply
3530 just based on the number of parameters).
3629 Expanding what we learned above to *polymorphic* matchers is now just as simple
3638 // To implement a polymorphic matcher, we just need to make MatchAndExplain a
4337 Remember that function objects created with `AsStdFunction()` are just