summaryrefslogtreecommitdiffstats
path: root/googletest/docs
diff options
context:
space:
mode:
authorVadim Kotov <vkotovv@gmail.com>2018-08-20 15:31:55 +0300
committerGitHub <noreply@github.com>2018-08-20 15:31:55 +0300
commit02c4f1af9d3cebdb963387a9450f33d22cc29e8f (patch)
treecdb40fe632628494a82e7cbb9c22ebb2dfda8c6f /googletest/docs
parent1778f2091e90c9cf36d0f7c01f3da5dd203db3a4 (diff)
downloadgoogletest-02c4f1af9d3cebdb963387a9450f33d22cc29e8f.tar.gz
googletest-02c4f1af9d3cebdb963387a9450f33d22cc29e8f.zip
docs: fixed broken references to sections in Advanced guide
Diffstat (limited to 'googletest/docs')
-rw-r--r--googletest/docs/advanced.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/googletest/docs/advanced.md b/googletest/docs/advanced.md
index 3a097f1b..599b8fb7 100644
--- a/googletest/docs/advanced.md
+++ b/googletest/docs/advanced.md
@@ -649,7 +649,7 @@ _death tests_. More generally, any test that checks that a program terminates
Note that if a piece of code throws an exception, we don't consider it "death"
for the purpose of death tests, as the caller of the code could catch the
exception and avoid the crash. If you want to verify exceptions thrown by your
-code, see [Exception Assertions](#ExceptionAssertions).
+code, see [Exception Assertions](#exception-assertions).
If you want to test `EXPECT_*()/ASSERT_*()` failures in your test code, see
Catching Failures
@@ -2120,7 +2120,7 @@ $ foo_test --gtest_repeat=1000 --gtest_filter=FooBar.*
Repeat the tests whose name matches the filter 1000 times.
```
-If your test program contains [global set-up/tear-down](#GlobalSetUp) code, it
+If your test program contains [global set-up/tear-down](#global-set-up-and-tear-down) code, it
will be repeated in each iteration as well, as the flakiness may be in it. You
can also specify the repeat count by setting the `GTEST_REPEAT` environment
variable.
OpenPOWER on IntegriCloud