summaryrefslogtreecommitdiff
path: root/googletest/docs
diff options
context:
space:
mode:
authorDerek Mauro <dmauro@google.com>2021-01-13 20:58:40 -0500
committerDerek Mauro <dmauro@google.com>2021-01-13 20:58:40 -0500
commitd72813110ce1d52820227ea0377462d4552d00d1 (patch)
tree84823c7710fb44246f17a656e3fd40df52559aa6 /googletest/docs
parent389cb68b87193358358ae87cc56d257fd0d80189 (diff)
parented1bf868464cfef290c89cad70ba0c908bf63ae9 (diff)
downloadgoogletest-git-d72813110ce1d52820227ea0377462d4552d00d1.tar.gz
Merge pull request #3189 from ellert:gtest-help-test-GNU/kFreeBSD
PiperOrigin-RevId: 349349288
Diffstat (limited to 'googletest/docs')
-rw-r--r--googletest/docs/advanced.md10
-rw-r--r--googletest/docs/faq.md2
2 files changed, 6 insertions, 6 deletions
diff --git a/googletest/docs/advanced.md b/googletest/docs/advanced.md
index 89aca1cf..7ac5a538 100644
--- a/googletest/docs/advanced.md
+++ b/googletest/docs/advanced.md
@@ -1432,8 +1432,8 @@ given test suite, whether their definitions come before or *after* the
You can see [sample7_unittest.cc] and [sample8_unittest.cc] for more examples.
-[sample7_unittest.cc]: ../samples/sample7_unittest.cc "Parameterized Test example"
-[sample8_unittest.cc]: ../samples/sample8_unittest.cc "Parameterized Test example with multiple parameters"
+[sample7_unittest.cc]: ../googletest/samples/sample7_unittest.cc "Parameterized Test example"
+[sample8_unittest.cc]: ../googletest/samples/sample8_unittest.cc "Parameterized Test example with multiple parameters"
### Creating Value-Parameterized Abstract Tests
@@ -1583,7 +1583,7 @@ TYPED_TEST(FooTest, HasPropertyA) { ... }
You can see [sample6_unittest.cc] for a complete example.
-[sample6_unittest.cc]: ../samples/sample6_unittest.cc "Typed Test example"
+[sample6_unittest.cc]: ../googletest/samples/sample6_unittest.cc "Typed Test example"
## Type-Parameterized Tests
@@ -2026,7 +2026,7 @@ You can do so by adding one line:
Now, sit back and enjoy a completely different output from your tests. For more
details, see [sample9_unittest.cc].
-[sample9_unittest.cc]: ../samples/sample9_unittest.cc "Event listener example"
+[sample9_unittest.cc]: ../googletest/samples/sample9_unittest.cc "Event listener example"
You may append more than one listener to the list. When an `On*Start()` or
`OnTestPartResult()` event is fired, the listeners will receive it in the order
@@ -2053,7 +2053,7 @@ by the former.
See [sample10_unittest.cc] for an example of a failure-raising listener.
-[sample10_unittest.cc]: ../samples/sample10_unittest.cc "Failure-raising listener example"
+[sample10_unittest.cc]: ../googletest/samples/sample10_unittest.cc "Failure-raising listener example"
## Running Test Programs: Advanced Options
diff --git a/googletest/docs/faq.md b/googletest/docs/faq.md
index b59e1a0d..d91bd4d0 100644
--- a/googletest/docs/faq.md
+++ b/googletest/docs/faq.md
@@ -281,7 +281,7 @@ If necessary, you can continue to derive test fixtures from a derived fixture.
googletest has no limit on how deep the hierarchy can be.
For a complete example using derived test fixtures, see
-[sample5_unittest.cc](../samples/sample5_unittest.cc).
+[sample5_unittest.cc](../googletest/samples/sample5_unittest.cc).
## My compiler complains "void value not ignored as it ought to be." What does this mean?