Lines Matching refs:expectation

249 Actual function call count doesn't match this expectation:
257 the line number to jump right to the failed expectation.
273 Well, specifying the expectation beforehand allows gMock to report a violation
292 In gMock we use the `EXPECT_CALL()` macro to set an expectation on a mock
320 more information about the expectation. We'll discuss how each clause works in
323 This syntax is designed to make an expectation read like English. For example,
344 failed expectation in messages, making debugging easier.
406 occur. It allows us to repeat an expectation many times without actually writing
448 expectation matches using a series of `WillOnce()` clauses followed by an
527 So far we've only shown examples where you have a single expectation. More
532 the **reverse order** they are defined, and stop when an active expectation that
534 older ones."). If the matching expectation cannot take any more calls, you will
546 error, as the last matching expectation (#2) has been saturated. If, however,
548 as now #1 will be the matching expectation.
560 **Tip:** It is very common to start with a catch-all expectation for a method
570 By default, an expectation can match a call even though an earlier expectation
625 see that the arguments match expectation #2 (remember that we always pick the
626 last matching expectation). Now, since we said that there should be only two
688 By the way, the other situation where an expectation may *not* be sticky is when
689 it's in a sequence - as soon as another expectation that comes after it in the