summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGennadiy Civil <gennadiycivil@users.noreply.github.com>2019-07-15 19:46:09 (GMT)
committerGitHub <noreply@github.com>2019-07-15 19:46:09 (GMT)
commitafa914325696789fc633fa2aa85bb8328c712a5d (patch)
treeec3342aacd38872da6d987b3357cea0f74c1bd2d
parentb97b96a1a434446819b593d18976322f0db6280c (diff)
parentb0568dcb4accfc5e3ae61862517983569414370d (diff)
downloadgoogletest-afa914325696789fc633fa2aa85bb8328c712a5d.zip
googletest-afa914325696789fc633fa2aa85bb8328c712a5d.tar.gz
googletest-afa914325696789fc633fa2aa85bb8328c712a5d.tar.bz2
Merge pull request #2324 from kuzkry/fix-broken-link
Fix a broken link
-rw-r--r--googlemock/docs/cook_book.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/googlemock/docs/cook_book.md b/googlemock/docs/cook_book.md
index d040209..8be6d1f 100644
--- a/googlemock/docs/cook_book.md
+++ b/googlemock/docs/cook_book.md
@@ -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. (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, 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/cook_book.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