diff options
| author | Gennadiy Civil <misterg@google.com> | 2019-06-19 16:48:38 -0400 |
|---|---|---|
| committer | Gennadiy Civil <misterg@google.com> | 2019-06-19 16:48:38 -0400 |
| commit | 5ed950c9e39cff044e84ca27d1b6919fa8dd7148 (patch) | |
| tree | 7e1e1dc73c35e6074906560d954cda807bb19dc7 /googletest/docs | |
| parent | ac31db8facf718ea98d28e63986642eb14a018d9 (diff) | |
| download | googletest-5ed950c9e39cff044e84ca27d1b6919fa8dd7148.tar.gz googletest-5ed950c9e39cff044e84ca27d1b6919fa8dd7148.tar.bz2 googletest-5ed950c9e39cff044e84ca27d1b6919fa8dd7148.zip | |
Renaming doc files to make the file names more palatable and in preparation for including documentation in sync process
Diffstat (limited to 'googletest/docs')
| -rw-r--r-- | googletest/docs/advanced.md | 6 | ||||
| -rw-r--r-- | googletest/docs/primer.md | 2 |
2 files changed, 4 insertions, 4 deletions
diff --git a/googletest/docs/advanced.md b/googletest/docs/advanced.md index 8f230ced..c8a7eb6f 100644 --- a/googletest/docs/advanced.md +++ b/googletest/docs/advanced.md @@ -394,14 +394,14 @@ using ::testing::StartsWith; EXPECT_THAT(Foo(), StartsWith("Hello")); ``` -Read this [recipe](../../googlemock/docs/CookBook.md#using-matchers-in-google-test-assertions) in +Read this [recipe](../../googlemock/docs/cook_book.md#using-matchers-in-google-test-assertions) in the gMock Cookbook for more details. gMock has a rich set of matchers. You can do many things googletest cannot do alone with them. For a list of matchers gMock provides, read -[this](../../googlemock/docs/CookBook.md#using-matchers). Especially useful among them are +[this](../../googlemock/docs/cook_book.md#using-matchers). Especially useful among them are some [protocol buffer matchers](https://github.com/google/nucleus/blob/master/nucleus/testing/protocol-buffer-matchers.h). It's easy to write -your [own matchers](../../googlemock/docs/CookBook.md#writing-new-matchers-quickly) too. +your [own matchers](../../googlemock/docs/cook_book.md#writing-new-matchers-quickly) too. For example, you can use gMock's [EqualsProto](https://github.com/google/nucleus/blob/master/nucleus/testing/protocol-buffer-matchers.h) diff --git a/googletest/docs/primer.md b/googletest/docs/primer.md index 8f4d4a05..450707b8 100644 --- a/googletest/docs/primer.md +++ b/googletest/docs/primer.md @@ -164,7 +164,7 @@ you'll get a compiler error. We used to require the arguments to support the `<<` is supported, it will be called to print the arguments when the assertion fails; otherwise googletest will attempt to print them in the best way it can. For more details and how to customize the printing of the arguments, see -gMock [recipe](../../googlemock/docs/CookBook.md#teaching-google-mock-how-to-print-your-values).). +gMock [recipe](../../googlemock/docs/cook_book.md#teaching-google-mock-how-to-print-your-values).). These assertions can work with a user-defined type, but only if you define the corresponding comparison operator (e.g. `==`, `<`, etc). Since this is |