Manual docs tweaks still in preparation for including docs with code pushes
This commit is contained in:
parent
15756aa0c8
commit
a743249a55
@ -385,7 +385,7 @@ using ::testing::StartsWith;
|
|||||||
```
|
```
|
||||||
|
|
||||||
Read this
|
Read this
|
||||||
[recipe](https://github.com/google/googletest/blob/master/googlemock/docs/cook_book.md#using-matchers-in-googletest-assertions)
|
[recipe](../../googlemock/docs/cook_book.md#using-matchers-in-googletest-assertions)
|
||||||
in the gMock Cookbook for more details.
|
in the gMock Cookbook for more details.
|
||||||
|
|
||||||
gMock has a rich set of matchers. You can do many things googletest cannot do
|
gMock has a rich set of matchers. You can do many things googletest cannot do
|
||||||
|
@ -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
|
`<<` 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.
|
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
|
For more details and how to customize the printing of the arguments, see
|
||||||
[documentation](https://github.com/google/googletest/blob/master/googlemock/docs/cook_book.md#teaching-gmock-how-to-print-your-values)
|
[documentation](../../googlemock/docs/cook_book.md#teaching-gmock-how-to-print-your-values)
|
||||||
|
|
||||||
These assertions can work with a user-defined type, but only if you define the
|
These assertions can work with a user-defined type, but only if you define the
|
||||||
corresponding comparison operator (e.g. `==`, `<`, etc). Since this is
|
corresponding comparison operator (e.g. `==`, `<`, etc). Since this is
|
||||||
|
Loading…
Reference in New Issue
Block a user