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
cfb5ef4e
Commit
cfb5ef4e
authored
Mar 03, 2020
by
Abseil Team
Committed by
vslashg
Mar 17, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Googletest export
Remove public buganizer reference from googletest cookbook. It also seems that this bug is obsolete. PiperOrigin-RevId: 298598298
parent
e588eb1f
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
cook_book.md
googlemock/docs/cook_book.md
+1
-1
No files found.
googlemock/docs/cook_book.md
View file @
cfb5ef4e
...
...
@@ -421,7 +421,7 @@ sadly they are side effects of C++'s limitations):
`NiceMock<StrictMock<MockFoo> >`
) is
**not**
supported.
2.
`NiceMock<MockFoo>`
and
`StrictMock<MockFoo>`
may not work correctly if the
destructor of
`MockFoo`
is not virtual. We would like to fix this, but it
requires cleaning up existing tests.
http://b/28934720 tracks the issue.
requires cleaning up existing tests.
3.
During the constructor or destructor of
`MockFoo`
, the mock object is
*not*
nice or strict. This may cause surprises if the constructor or destructor
calls a mock method on
`this`
object. (This behavior, however, is consistent
...
...
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