summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAbseil Team <absl-team@google.com>2019-09-11 18:57:59 (GMT)
committerShaindel Schwartz <shaindel@google.com>2019-09-12 16:10:33 (GMT)
commit274afe50cf57630ef9d34e702cf77f1854358581 (patch)
treecab341b3bb7e4267470e2e8ede7b3183c95fc51b
parent33a0d4f6d76a0ed6061e612848532cba82d42870 (diff)
downloadgoogletest-274afe50cf57630ef9d34e702cf77f1854358581.zip
googletest-274afe50cf57630ef9d34e702cf77f1854358581.tar.gz
googletest-274afe50cf57630ef9d34e702cf77f1854358581.tar.bz2
Googletest export
In the text fixtures section, point to the specific FAQ entry on constructors vs. `SetUp`. PiperOrigin-RevId: 268509969
-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 0356968..0317692 100644
--- a/googletest/docs/primer.md
+++ b/googletest/docs/primer.md
@@ -319,7 +319,7 @@ To create a fixture:
4. 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
- the [FAQ](faq.md).
+ the [FAQ](faq.md#CtorVsSetUp).
5. If needed, define subroutines for your tests to share.
When using a fixture, use `TEST_F()` instead of `TEST()` as it allows you to