summaryrefslogtreecommitdiffstats
path: root/googlemock
diff options
context:
space:
mode:
authorAbseil Team <absl-team@google.com>2020-03-03 15:08:02 (GMT)
committerAndy Soffer <asoffer@google.com>2020-03-04 19:05:44 (GMT)
commita6b3a029f7edef0d171c5122bba82b17769e945e (patch)
tree8f14d6d3a281959bf6a0c71d4beb653ac276bbca /googlemock
parente588eb1ff9ff6598666279b737b27f983156ad85 (diff)
downloadgoogletest-a6b3a029f7edef0d171c5122bba82b17769e945e.zip
googletest-a6b3a029f7edef0d171c5122bba82b17769e945e.tar.gz
googletest-a6b3a029f7edef0d171c5122bba82b17769e945e.tar.bz2
Export Test - Do Not Merge
Remove public buganizer reference from googletest cookbook. It also seems that this bug is obsolete. PiperOrigin-RevId: 298598298
Diffstat (limited to 'googlemock')
-rw-r--r--googlemock/docs/cook_book.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/googlemock/docs/cook_book.md b/googlemock/docs/cook_book.md
index 7209ea0..51eb94a 100644
--- a/googlemock/docs/cook_book.md
+++ b/googlemock/docs/cook_book.md
@@ -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