aboutsummaryrefslogtreecommitdiffstats
path: root/googlemock/docs/ForDummies.md
diff options
context:
space:
mode:
authorGennadiy Civil <gennadiycivil@users.noreply.github.com>2018-08-15 13:02:54 -0700
committerGitHub <noreply@github.com>2018-08-15 13:02:54 -0700
commit1246e5807a94081049285e8fda4309f67ef571b4 (patch)
treef2008a506ed390eb94da65cb8a0dc9351b7efb9b /googlemock/docs/ForDummies.md
parent4b6a7a49ab63f609630ce58c18a39c4048ab3ad5 (diff)
parent2172c08c9241ab0cc8857980bbe925fe1a55cf3c (diff)
downloadgoogletest-1246e5807a94081049285e8fda4309f67ef571b4.tar.gz
googletest-1246e5807a94081049285e8fda4309f67ef571b4.tar.bz2
googletest-1246e5807a94081049285e8fda4309f67ef571b4.zip
Merge branch 'master' into cleanup-cmake
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.