aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGennadiy Civil <gennadiycivil@users.noreply.github.com>2018-08-29 00:43:34 -0400
committerGitHub <noreply@github.com>2018-08-29 00:43:34 -0400
commit3d5612182581df64acc12d2633e473decf5adc47 (patch)
tree5e964310c8581c00dcf874ace68e9b419ea1e466
parent58f3f1005cffce8a9d005d0361d3471cd9947501 (diff)
parentca912f8b7000268da4ae37d68eda3b9b513d63ef (diff)
downloadgoogletest-3d5612182581df64acc12d2633e473decf5adc47.tar.gz
Merge pull request #1794 from BlueMonday/patch-1
Fix broken FAQ link in primer.md
-rw-r--r--googletest/docs/primer.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/googletest/docs/primer.md b/googletest/docs/primer.md
index 02dea424..7a8ea8d7 100644
--- a/googletest/docs/primer.md
+++ b/googletest/docs/primer.md
@@ -317,7 +317,7 @@ To create a fixture:
1. If necessary, write a destructor or `TearDown()` function to release any
resources you allocated in `SetUp()` . To learn when you should use the
constructor/destructor and when you should use `SetUp()/TearDown()`, read
- this [FAQ](faq.md#should-i-use-the-constructordestructor-of-the-test-fixture-or-the-set-uptear-down-function) entry.
+ this [FAQ](faq.md#should-i-use-the-constructordestructor-of-the-test-fixture-or-setupteardown) entry.
1. If needed, define subroutines for your tests to share.
When using a fixture, use `TEST_F()` instead of `TEST()` as it allows you to