aboutsummaryrefslogtreecommitdiffstats
path: root/googlemock/docs/CookBook.md
diff options
context:
space:
mode:
authorGaspard Petit <gaspard.petit@eidosmontreal.com>2018-01-09 15:22:30 -0500
committerGaspard Petit <gaspard.petit@eidosmontreal.com>2018-01-09 15:22:30 -0500
commit5d96565ccc4b5bbd72100729361516de79b61353 (patch)
tree93aa8a57b1f8015974c44a6e5ec5efa8d69ddbab /googlemock/docs/CookBook.md
parent8b491162f79282b79292e0f4166194b3f7ccb7b1 (diff)
parent23015249236e60b94b5010330ef687de43d2e923 (diff)
downloadgoogletest-5d96565ccc4b5bbd72100729361516de79b61353.tar.gz
googletest-5d96565ccc4b5bbd72100729361516de79b61353.tar.bz2
googletest-5d96565ccc4b5bbd72100729361516de79b61353.zip
Merge branch 'master' into support_xboxone
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