diff options
author | Tanzinul Islam <tanzislam@users.noreply.github.com> | 2017-11-19 20:17:46 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-11-19 20:17:46 +0000 |
commit | 4ba3803f936a2f432e60841bc9358ea2f3a951eb (patch) | |
tree | 778e7ffd3bfda62cd3be3e01a2d0207d5ffe1d82 /googlemock/docs/CookBook.md | |
parent | 78b1ff074799c776f90a77203fcd7adc98e11736 (diff) | |
parent | d175c8bf823e709d570772b038757fadf63bc632 (diff) | |
download | googletest-4ba3803f936a2f432e60841bc9358ea2f3a951eb.tar.gz googletest-4ba3803f936a2f432e60841bc9358ea2f3a951eb.tar.bz2 googletest-4ba3803f936a2f432e60841bc9358ea2f3a951eb.zip |
Merge branch 'master' into fix_death_test_child_mingw_wer_issue1116
Diffstat (limited to 'googlemock/docs/CookBook.md')
-rw-r--r-- | googlemock/docs/CookBook.md | 2 |
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 |