diff options
| author | Abseil Team <absl-team@google.com> | 2020-03-03 10:08:02 -0500 |
|---|---|---|
| committer | vslashg <gfalcon@google.com> | 2020-03-17 17:19:51 -0400 |
| commit | cfb5ef4e7dc032c71e3e3323b45962839331e399 (patch) | |
| tree | 8f14d6d3a281959bf6a0c71d4beb653ac276bbca | |
| parent | e588eb1ff9ff6598666279b737b27f983156ad85 (diff) | |
| download | googletest-cfb5ef4e7dc032c71e3e3323b45962839331e399.tar.gz googletest-cfb5ef4e7dc032c71e3e3323b45962839331e399.tar.bz2 googletest-cfb5ef4e7dc032c71e3e3323b45962839331e399.zip | |
Googletest export
Remove public buganizer reference from googletest cookbook.
It also seems that this bug is obsolete.
PiperOrigin-RevId: 298598298
| -rw-r--r-- | googlemock/docs/cook_book.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/googlemock/docs/cook_book.md b/googlemock/docs/cook_book.md index 7209ea05..51eb94a9 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 |