summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authornicolacavallini <nicola.alessandro.cavallini@gmail.com>2016-12-23 10:45:08 (GMT)
committernicolacavallini <nicola.alessandro.cavallini@gmail.com>2016-12-23 10:45:08 (GMT)
commit2eaab21554e992be5c62772a473c123f5e262220 (patch)
tree6d02adf42b4f36163f84a5fc97807b7be9a75a4a
parent5e7fd50e17b6edf1cadff973d0ec68966cf3265e (diff)
downloadgoogletest-2eaab21554e992be5c62772a473c123f5e262220.zip
googletest-2eaab21554e992be5c62772a473c123f5e262220.tar.gz
googletest-2eaab21554e992be5c62772a473c123f5e262220.tar.bz2
added link to sample 6 in the documentation of typed testrefs/pull/968/head
-rw-r--r--googletest/docs/AdvancedGuide.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/googletest/docs/AdvancedGuide.md b/googletest/docs/AdvancedGuide.md
index 93a6520..8712766 100644
--- a/googletest/docs/AdvancedGuide.md
+++ b/googletest/docs/AdvancedGuide.md
@@ -1344,7 +1344,7 @@ TYPED_TEST(FooTest, DoesBlah) {
TYPED_TEST(FooTest, HasPropertyA) { ... }
```
-You can see `samples/sample6_unittest.cc` for a complete example.
+You can see [`samples/sample6_unittest.cc`](../samples/sample6_unittest.cc) for a complete example.
_Availability:_ Linux, Windows (requires MSVC 8.0 or above), Mac;
since version 1.1.0.
@@ -1551,7 +1551,7 @@ exception, you could catch the exception and assert on it. But Google
Test doesn't use exceptions, so how do we test that a piece of code
generates an expected failure?
-`"gtest/gtest-spi.h"` contains some constructs to do this. After
+`"gtest/gtest-spi.h"` contains some constructs to do this. After
`#include`ing this header, you can use
| `EXPECT_FATAL_FAILURE(`_statement, substring_`);` |