aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGennadiy Civil <gennadiycivil@users.noreply.github.com>2017-08-02 16:45:13 -0400
committerGitHub <noreply@github.com>2017-08-02 16:45:13 -0400
commitd966d5fbe005d8de37362e578851bd520909064b (patch)
tree0a8dc0e1b014faa8f9e744be7bb5c97d36c4987d
parente2e37c94320b8637a5696f7cbe7078f1ae4cd809 (diff)
parent2eaab21554e992be5c62772a473c123f5e262220 (diff)
downloadgoogletest-d966d5fbe005d8de37362e578851bd520909064b.tar.gz
googletest-d966d5fbe005d8de37362e578851bd520909064b.tar.bz2
googletest-d966d5fbe005d8de37362e578851bd520909064b.zip
Merge pull request #968 from nicolacavallini/link_typed_test_docs
added link to sample 6 in the documentation of typed test
-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 fc27d1d0..98533723 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_`);` |