aboutsummaryrefslogtreecommitdiffstats
path: root/googlemock/docs/CookBook.md
diff options
context:
space:
mode:
authorGennadiy Civil <gennadiycivil@users.noreply.github.com>2017-10-20 17:25:41 -0400
committerGitHub <noreply@github.com>2017-10-20 17:25:41 -0400
commitc208d8df23d6bd4fbe153a34d092aff0fddbc6a5 (patch)
tree820e437ce56c2a4c0d39b783176bf1db1605a283 /googlemock/docs/CookBook.md
parent3eaba9f07c5f81a8b83432e4ae389ee42337393f (diff)
parent69e48e92de43960a316a826293510b7b3deb9eca (diff)
downloadgoogletest-c208d8df23d6bd4fbe153a34d092aff0fddbc6a5.tar.gz
googletest-c208d8df23d6bd4fbe153a34d092aff0fddbc6a5.tar.bz2
googletest-c208d8df23d6bd4fbe153a34d092aff0fddbc6a5.zip
Merge branch 'master' into master
Diffstat (limited to 'googlemock/docs/CookBook.md')
-rw-r--r--googlemock/docs/CookBook.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/googlemock/docs/CookBook.md b/googlemock/docs/CookBook.md
index 753c6dd3..3d07e68b 100644
--- a/googlemock/docs/CookBook.md
+++ b/googlemock/docs/CookBook.md
@@ -227,7 +227,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, he 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. If the user believes these calls are harmless, they can add an `EXPECT_CALL()` to suppress the warning.
However, sometimes you may want to suppress all "uninteresting call"
warnings, while sometimes you may want the opposite, i.e. to treat all