summaryrefslogtreecommitdiffstats
path: root/googlemock
diff options
context:
space:
mode:
authorGennadiy Civil <misterg@google.com>2018-06-11 15:40:35 (GMT)
committerGennadiy Civil <misterg@google.com>2018-06-11 15:40:35 (GMT)
commit8f87d00398228925b1542b81710a9015c8f68e7b (patch)
treea383d30b17b861537037174038fc3e15daa6e055 /googlemock
parentde47b0d30c1d2a2072eb1c2a2e852d6aaa028931 (diff)
downloadgoogletest-8f87d00398228925b1542b81710a9015c8f68e7b.zip
googletest-8f87d00398228925b1542b81710a9015c8f68e7b.tar.gz
googletest-8f87d00398228925b1542b81710a9015c8f68e7b.tar.bz2
Rename AdvancedGuide.md to advanced.md and adjust the links.
Part of documentation rationalization work
Diffstat (limited to 'googlemock')
-rw-r--r--googlemock/docs/CheatSheet.md2
-rw-r--r--googlemock/docs/CookBook.md2
-rw-r--r--googlemock/docs/ForDummies.md2
3 files changed, 3 insertions, 3 deletions
diff --git a/googlemock/docs/CheatSheet.md b/googlemock/docs/CheatSheet.md
index d078b42..d54dd16 100644
--- a/googlemock/docs/CheatSheet.md
+++ b/googlemock/docs/CheatSheet.md
@@ -229,7 +229,7 @@ The `argument` can be either a C string or a C++ string object:
`ContainsRegex()` and `MatchesRegex()` use the regular expression
syntax defined
-[here](../../googletest/docs/AdvancedGuide.md#regular-expression-syntax).
+[here](../../googletest/docs/advanced.md#regular-expression-syntax).
`StrCaseEq()`, `StrCaseNe()`, `StrEq()`, and `StrNe()` work for wide
strings as well.
diff --git a/googlemock/docs/CookBook.md b/googlemock/docs/CookBook.md
index 3737d03..bd9f026 100644
--- a/googlemock/docs/CookBook.md
+++ b/googlemock/docs/CookBook.md
@@ -3655,6 +3655,6 @@ This printer knows how to print built-in C++ types, native arrays, STL
containers, and any type that supports the `<<` operator. For other
types, it prints the raw bytes in the value and hopes that you the
user can figure it out.
-[Google Test's advanced guide](../../googletest/docs/AdvancedGuide.md#teaching-google-test-how-to-print-your-values)
+[Google Test's advanced guide](../../googletest/docs/advanced.md#teaching-google-test-how-to-print-your-values)
explains how to extend the printer to do a better job at
printing your particular type than to dump the bytes.
diff --git a/googlemock/docs/ForDummies.md b/googlemock/docs/ForDummies.md
index 7691056..1e0fd41 100644
--- a/googlemock/docs/ForDummies.md
+++ b/googlemock/docs/ForDummies.md
@@ -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.