Googletest export
Update broken links. PiperOrigin-RevId: 264405918
This commit is contained in:
parent
c9ccac7cb7
commit
d1ad644db4
@ -483,7 +483,7 @@ the *default* action for the function every time (unless, of course, you have a
|
|||||||
|
|
||||||
What can we do inside `WillOnce()` besides `Return()`? You can return a
|
What can we do inside `WillOnce()` besides `Return()`? You can return a
|
||||||
reference using `ReturnRef(*variable*)`, or invoke a pre-defined function, among
|
reference using `ReturnRef(*variable*)`, or invoke a pre-defined function, among
|
||||||
[others](#ActionList).
|
[others](cook_book.md#using-actions).
|
||||||
|
|
||||||
**Important note:** The `EXPECT_CALL()` statement evaluates the action clause
|
**Important note:** The `EXPECT_CALL()` statement evaluates the action clause
|
||||||
only once, even though the action may be performed many times. Therefore you
|
only once, even though the action may be performed many times. Therefore you
|
||||||
@ -561,7 +561,7 @@ overloaded). This makes any calls to the method expected. This is not necessary
|
|||||||
for methods that are not mentioned at all (these are "uninteresting"), but is
|
for methods that are not mentioned at all (these are "uninteresting"), but is
|
||||||
useful for methods that have some expectations, but for which other calls are
|
useful for methods that have some expectations, but for which other calls are
|
||||||
ok. See
|
ok. See
|
||||||
[Understanding Uninteresting vs Unexpected Calls](#uninteresting-vs-unexpected).
|
[Understanding Uninteresting vs Unexpected Calls](cook_book.md#uninteresting-vs-unexpected).
|
||||||
|
|
||||||
#### Ordered vs Unordered Calls {#OrderedCalls}
|
#### Ordered vs Unordered Calls {#OrderedCalls}
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user