diff options
Diffstat (limited to 'googlemock/docs')
| -rw-r--r-- | googlemock/docs/Documentation.md | 2 | ||||
| -rw-r--r-- | googlemock/docs/ForDummies.md | 6 | ||||
| -rw-r--r-- | googlemock/docs/cheat_sheet.md (renamed from googlemock/docs/CheatSheet.md) | 0 | ||||
| -rw-r--r-- | googlemock/docs/cook_book.md | 4 |
4 files changed, 6 insertions, 6 deletions
diff --git a/googlemock/docs/Documentation.md b/googlemock/docs/Documentation.md index af8a3b9..c2b00ba 100644 --- a/googlemock/docs/Documentation.md +++ b/googlemock/docs/Documentation.md @@ -5,7 +5,7 @@ documentation for that specific version instead (e.g. by checking out the respective git branch/tag).** * [ForDummies](ForDummies.md) -- start here if you are new to Google Mock. - * [CheatSheet](CheatSheet.md) -- a quick reference. + * [CheatSheet](cheat_sheet.md) -- a quick reference. * [CookBook](cook_book.md) -- recipes for doing various tasks using Google Mock. * [FrequentlyAskedQuestions](FrequentlyAskedQuestions.md) -- check here before asking a question on the mailing list. diff --git a/googlemock/docs/ForDummies.md b/googlemock/docs/ForDummies.md index c8a83cb..4b7551e 100644 --- a/googlemock/docs/ForDummies.md +++ b/googlemock/docs/ForDummies.md @@ -249,7 +249,7 @@ EXPECT_CALL(turtle, Forward(_)); `_` is an instance of what we call **matchers**. A matcher is like a predicate and can test whether an argument is what we'd expect. You can use a matcher inside `EXPECT_CALL()` wherever a function argument is expected. -A list of built-in matchers can be found in the [CheatSheet](CheatSheet.md). For example, here's the `Ge` (greater than or equal) matcher: +A list of built-in matchers can be found in the [CheatSheet](cheat_sheet.md). For example, here's the `Ge` (greater than or equal) matcher: ```cpp using ::testing::Ge; @@ -264,7 +264,7 @@ The first clause we can specify following an `EXPECT_CALL()` is `Times()`. We ca An interesting special case is when we say `Times(0)`. You may have guessed - it means that the function shouldn't be called with the given arguments at all, and Google Mock will report a Google Test failure whenever the function is (wrongfully) called. -We've seen `AtLeast(n)` as an example of fuzzy cardinalities earlier. For the list of built-in cardinalities you can use, see the [CheatSheet](CheatSheet.md). +We've seen `AtLeast(n)` as an example of fuzzy cardinalities earlier. For the list of built-in cardinalities you can use, see the [CheatSheet](cheat_sheet.md). The `Times()` clause can be omitted. **If you omit `Times()`, Google Mock will infer the cardinality for you.** The rules are easy to remember: @@ -305,7 +305,7 @@ says that `turtle.GetY()` will be called _at least twice_ (Google Mock knows thi Of course, if you explicitly write a `Times()`, Google Mock will not try to infer the cardinality itself. What if the number you specified is larger than there are `WillOnce()` clauses? Well, after all `WillOnce()`s are used up, Google Mock will do the _default_ action for the function every time (unless, of course, you have a `WillRepeatedly()`.). -What can we do inside `WillOnce()` besides `Return()`? You can return a reference using `ReturnRef(variable)`, or invoke a pre-defined function, among [others](CheatSheet.md#actions). +What can we do inside `WillOnce()` besides `Return()`? You can return a reference using `ReturnRef(variable)`, or invoke a pre-defined function, among [others](cheat_sheet.md#actions). **Important note:** The `EXPECT_CALL()` statement evaluates the action clause only once, even though the action may be performed many times. Therefore you must be careful about side effects. The following may not do what you want: diff --git a/googlemock/docs/CheatSheet.md b/googlemock/docs/cheat_sheet.md index d09d910..d09d910 100644 --- a/googlemock/docs/CheatSheet.md +++ b/googlemock/docs/cheat_sheet.md diff --git a/googlemock/docs/cook_book.md b/googlemock/docs/cook_book.md index 6b0228a..f25b681 100644 --- a/googlemock/docs/cook_book.md +++ b/googlemock/docs/cook_book.md @@ -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 |