aboutsummaryrefslogtreecommitdiffstats
path: root/googlemock/docs/ForDummies.md
diff options
context:
space:
mode:
authorConor Burgess <Burgess.Conor@gmail.com>2018-08-17 17:15:32 +0100
committerGitHub <noreply@github.com>2018-08-17 17:15:32 +0100
commit687964c84f798ce331fc60f6b8f212410ef46b3c (patch)
tree20ed743afd555c46b91361cf864c76643f1d89b2 /googlemock/docs/ForDummies.md
parentf11a8f9131584cf4009eca8af8a66e920c1b7391 (diff)
parent02a8ca87735601466d8c564344f9be493da84708 (diff)
downloadgoogletest-687964c84f798ce331fc60f6b8f212410ef46b3c.tar.gz
googletest-687964c84f798ce331fc60f6b8f212410ef46b3c.tar.bz2
googletest-687964c84f798ce331fc60f6b8f212410ef46b3c.zip
Merge branch 'master' into fix-argc
Diffstat (limited to 'googlemock/docs/ForDummies.md')
-rw-r--r--googlemock/docs/ForDummies.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/googlemock/docs/ForDummies.md b/googlemock/docs/ForDummies.md
index 76910569..566a34e5 100644
--- a/googlemock/docs/ForDummies.md
+++ b/googlemock/docs/ForDummies.md
@@ -170,7 +170,7 @@ Admittedly, this test is contrived and doesn't do much. You can easily achieve t
## Using Google Mock with Any Testing Framework ##
If you want to use something other than Google Test (e.g. [CppUnit](http://sourceforge.net/projects/cppunit/) or
-[CxxTest](http://cxxtest.tigris.org/)) as your testing framework, just change the `main()` function in the previous section to:
+[CxxTest](https://cxxtest.com/)) as your testing framework, just change the `main()` function in the previous section to:
```
int main(int argc, char** argv) {
// The following line causes Google Mock to throw an exception on failure,
@@ -187,7 +187,7 @@ sometimes causes the test program to crash. You'll still be able to
notice that the test has failed, but it's not a graceful failure.
A better solution is to use Google Test's
-[event listener API](../../googletest/docs/AdvancedGuide.md#extending-google-test-by-handling-test-events)
+[event listener API](../../googletest/docs/advanced.md#extending-google-test-by-handling-test-events)
to report a test failure to your testing framework properly. You'll need to
implement the `OnTestPartResult()` method of the event listener interface, but it
should be straightforward.