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.
271 Well, specifying the expectation beforehand allows gMock to report a violation
290 In gMock we use the `EXPECT_CALL()` macro to set an expectation on a mock
318 more information about the expectation. We'll discuss how each clause works in
321 This syntax is designed to make an expectation read like English. For example,
342 failed expectation in messages, making debugging easier.
404 occur. It allows us to repeat an expectation many times without actually writing
446 expectation matches using a series of `WillOnce()` clauses followed by an
525 So far we've only shown examples where you have a single expectation. More
530 the **reverse order** they are defined, and stop when an active expectation that
532 older ones."). If the matching expectation cannot take any more calls, you will
544 error, as the last matching expectation (#2) has been saturated. If, however,
546 as now #1 will be the matching expectation.
558 **Tip:** It is very common to start with a catch-all expectation for a method
568 By default, an expectation can match a call even though an earlier expectation
623 see that the arguments match expectation #2 (remember that we always pick the
624 last matching expectation). Now, since we said that there should be only two
686 By the way, the other situation where an expectation may *not* be sticky is when
687 it's in a sequence - as soon as another expectation that comes after it in the