aboutsummaryrefslogtreecommitdiffstats
path: root/googlemock/docs/CookBook.md
diff options
context:
space:
mode:
authorHerbert Thielen <thielen@hs-worms.de>2017-10-04 21:03:47 +0200
committerGitHub <noreply@github.com>2017-10-04 21:03:47 +0200
commitceee80c383d6f34af1a4e0fbb464f3f144cded68 (patch)
treeacddac2058e907f3db9bafe616b38e156becb51d /googlemock/docs/CookBook.md
parent98024ad2027387680fd4af72b70c14667850b09c (diff)
parent7b6561c56e353100aca8458d7bc49c4e0119bae8 (diff)
downloadgoogletest-ceee80c383d6f34af1a4e0fbb464f3f144cded68.tar.gz
googletest-ceee80c383d6f34af1a4e0fbb464f3f144cded68.tar.bz2
googletest-ceee80c383d6f34af1a4e0fbb464f3f144cded68.zip
Merge branch 'master' into hethi/issue-360-remove-GTEST_HAS_PARAM_TESTS
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