aboutsummaryrefslogtreecommitdiffstats
path: root/googlemock/docs/FrequentlyAskedQuestions.md
diff options
context:
space:
mode:
authorGennadiy Civil <gennadiycivil@users.noreply.github.com>2018-08-08 12:19:04 -0700
committerGitHub <noreply@github.com>2018-08-08 12:19:04 -0700
commit11f5a2740aa8a55d620fba6957e53ad08721cf54 (patch)
tree04f982e6158e57f68529ca47e37ec377574647dd /googlemock/docs/FrequentlyAskedQuestions.md
parent008e54c1dd407b6edd680fccf78cd194365e0507 (diff)
parent66bd580b5bc054522f7fab13463a47aa156a2d4b (diff)
downloadgoogletest-11f5a2740aa8a55d620fba6957e53ad08721cf54.tar.gz
googletest-11f5a2740aa8a55d620fba6957e53ad08721cf54.tar.bz2
googletest-11f5a2740aa8a55d620fba6957e53ad08721cf54.zip
Merge branch 'master' into cross-testing-patch-1
Diffstat (limited to 'googlemock/docs/FrequentlyAskedQuestions.md')
-rw-r--r--googlemock/docs/FrequentlyAskedQuestions.md5
1 files changed, 2 insertions, 3 deletions
diff --git a/googlemock/docs/FrequentlyAskedQuestions.md b/googlemock/docs/FrequentlyAskedQuestions.md
index 5eac83f4..9008c637 100644
--- a/googlemock/docs/FrequentlyAskedQuestions.md
+++ b/googlemock/docs/FrequentlyAskedQuestions.md
@@ -240,7 +240,7 @@ You cannot mock a variadic function (i.e. a function taking ellipsis
The problem is that in general, there is _no way_ for a mock object to
know how many arguments are passed to the variadic method, and what
the arguments' types are. Only the _author of the base class_ knows
-the protocol, and we cannot look into his head.
+the protocol, and we cannot look into their head.
Therefore, to mock such a function, the _user_ must teach the mock
object how to figure out the number of arguments and their types. One
@@ -528,7 +528,7 @@ interface, which then can be easily mocked. It's a bit of work
initially, but usually pays for itself quickly.
This Google Testing Blog
-[post](http://googletesting.blogspot.com/2008/06/defeat-static-cling.html)
+[post](https://testing.googleblog.com/2008/06/defeat-static-cling.html)
says it excellently. Check it out.
## My mock object needs to do complex stuff. It's a lot of pain to specify the actions. Google Mock sucks! ##
@@ -607,7 +607,6 @@ See this [recipe](CookBook.md#mocking_side_effects) for more details and an exam
If you cannot find the answer to your question in this FAQ, there are
some other resources you can use:
- 1. read other [documentation](Documentation.md),
1. search the mailing list [archive](http://groups.google.com/group/googlemock/topics),
1. ask it on [googlemock@googlegroups.com](mailto:googlemock@googlegroups.com) and someone will answer it (to prevent spam, we require you to join the [discussion group](http://groups.google.com/group/googlemock) before you can post.).