diff options
| author | Abseil Team <absl-team@google.com> | 2019-09-11 14:57:59 -0400 |
|---|---|---|
| committer | Shaindel Schwartz <shaindel@google.com> | 2019-09-12 12:10:33 -0400 |
| commit | 274afe50cf57630ef9d34e702cf77f1854358581 (patch) | |
| tree | cab341b3bb7e4267470e2e8ede7b3183c95fc51b | |
| parent | 33a0d4f6d76a0ed6061e612848532cba82d42870 (diff) | |
| download | googletest-git-274afe50cf57630ef9d34e702cf77f1854358581.tar.gz | |
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.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/googletest/docs/primer.md b/googletest/docs/primer.md index 03569688..0317692b 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 |