summaryrefslogtreecommitdiffstats
path: root/googletest
diff options
context:
space:
mode:
authorAbseil Team <absl-team@google.com>2019-09-05 21:40:42 (GMT)
committerGennadiy Rozental <rogeeff@google.com>2019-09-06 12:00:11 (GMT)
commit6123df929dbae61032417a42531d9e99d66df95b (patch)
treeefe444a06770b3b2244285fec3250ee6062e2d43 /googletest
parentab8f346b076f76f7770f33437fb5823fa444cb80 (diff)
downloadgoogletest-6123df929dbae61032417a42531d9e99d66df95b.zip
googletest-6123df929dbae61032417a42531d9e99d66df95b.tar.gz
googletest-6123df929dbae61032417a42531d9e99d66df95b.tar.bz2
Googletest export
Internal Change PiperOrigin-RevId: 267457395
Diffstat (limited to 'googletest')
-rw-r--r--googletest/docs/faq.md2
-rw-r--r--googletest/docs/primer.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/googletest/docs/faq.md b/googletest/docs/faq.md
index 9949fec..960a827 100644
--- a/googletest/docs/faq.md
+++ b/googletest/docs/faq.md
@@ -298,7 +298,7 @@ In the end, this boils down to good concurrent programming. You have to make
sure that there is no race conditions or dead locks in your program. No silver
bullet - sorry!
-## Should I use the constructor/destructor of the test fixture or SetUp()/TearDown()?
+## Should I use the constructor/destructor of the test fixture or SetUp()/TearDown()? {#CtorVsSetUp}
The first thing to remember is that googletest does **not** reuse the same test
fixture object across multiple tests. For each `TEST_F`, googletest will create
diff --git a/googletest/docs/primer.md b/googletest/docs/primer.md
index caf9c43..ae03105 100644
--- a/googletest/docs/primer.md
+++ b/googletest/docs/primer.md
@@ -302,7 +302,7 @@ for
**Availability**: Linux, Windows, Mac.
-## Test Fixtures: Using the Same Data Configuration for Multiple Tests
+## Test Fixtures: Using the Same Data Configuration for Multiple Tests {#same-data-multiple-tests}
If you find yourself writing two or more tests that operate on similar data, you
can use a *test fixture*. It allows you to reuse the same configuration of