Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
googletest
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Chen Yisong
googletest
Commits
274afe50
Commit
274afe50
authored
Sep 11, 2019
by
Abseil Team
Committed by
Shaindel Schwartz
Sep 12, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Googletest export
In the text fixtures section, point to the specific FAQ entry on constructors vs. `SetUp`. PiperOrigin-RevId: 268509969
parent
33a0d4f6
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
primer.md
googletest/docs/primer.md
+1
-1
No files found.
googletest/docs/primer.md
View file @
274afe50
...
...
@@ -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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment