diff options
Diffstat (limited to 'googlemock/docs/cook_book.md')
| -rw-r--r-- | googlemock/docs/cook_book.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/googlemock/docs/cook_book.md b/googlemock/docs/cook_book.md index 6b0228a5..d0402091 100644 --- a/googlemock/docs/cook_book.md +++ b/googlemock/docs/cook_book.md @@ -3,7 +3,7 @@ <!-- GOOGLETEST_CM0011 DO NOT DELETE --> You can find recipes for using Google Mock here. If you haven't yet, -please read the [ForDummies](ForDummies.md) document first to make sure you understand +please read the [ForDummies](for_dummies.md) document first to make sure you understand the basics. **Note:** Google Mock lives in the `testing` name space. For @@ -229,7 +229,7 @@ If a mock method has no `EXPECT_CALL` spec but is called, Google Mock will print a warning about the "uninteresting call". The rationale is: * New methods may be added to an interface after a test is written. We shouldn't fail a test just because a method it doesn't know about is called. - * However, this may also mean there's a bug in the test, so Google Mock shouldn't be silent either. If the user believes these calls are harmless, they can add an `EXPECT_CALL()` to suppress the warning. + * However, this may also mean there's a bug in the test, so Google Mock shouldn't be silent either. (Note that the user should [*not* add an `EXPECT_CALL()`](https://github.com/google/googletest/blob/master/googlemock/docs/CookBook.md#knowing-when-to-expect) to suppress the warning, even if they think the call is harmless). However, sometimes you may want to suppress all "uninteresting call" warnings, while sometimes you may want the opposite, i.e. to treat all @@ -866,7 +866,7 @@ says that `Blah()` will be called with arguments `x`, `y`, and `z` where `x < y < z`. As a convenience and example, Google Mock provides some matchers for -2-tuples, including the `Lt()` matcher above. See the [CheatSheet](CheatSheet.md) for +2-tuples, including the `Lt()` matcher above. See the [CheatSheet](cheat_sheet.md) for the complete list. Note that if you want to pass the arguments to a predicate of your own @@ -1391,7 +1391,7 @@ instead of being overly constraining. Google Mock allows you to impose an arbitrary DAG (directed acyclic graph) on the calls. One way to express the DAG is to use the -[After](CheatSheet.md#the-after-clause) clause of `EXPECT_CALL`. +[After](cheat_sheet.md#the-after-clause) clause of `EXPECT_CALL`. Another way is via the `InSequence()` clause (not the same as the `InSequence` class), which we borrowed from jMock 2. It's less |