GitLab

PiperOrigin-RevId: 524868227
Change-Id: I702ede27570e3d3f06d534d6ccf8b39689105d07

PiperOrigin-RevId: 502901538
Change-Id: I0cf351b9ad1411ae9c45e09550c24e006a24e179

PiperOrigin-RevId: 496679950
Change-Id: I2842050902876231d49a142165bcbb88d737505d

It is good practice to specify a name for the `testing::Property` matcher's use in diagnostics, and we should do so in our examples.

PiperOrigin-RevId: 496406309
Change-Id: Ibb4d1ba63771b5d6855442b91564027cda8ddaca

EXPECT_CALL doesn't seem to make much sense here. I think the intent was to use EXPECT_THAT instead.

PiperOrigin-RevId: 495427663
Change-Id: I39a16ea37282729d34017c6bcd331a60cedf1fbe

PiperOrigin-RevId: 490601453
Change-Id: I733b2ed8740b1c809dddb166a42993b869198469

PiperOrigin-RevId: 473353707
Change-Id: Ief5bdbd2b8e28bac8f47be9aaeac4bb93875a793

PiperOrigin-RevId: 454677195
Change-Id: I7a1419e22d617db41a5c310bc6f6158ba4cec1ab

So that it can be referenced in conversion operators for actions that need to
know the concrete return type.

PiperOrigin-RevId: 447889344
Change-Id: I643d3298bc8effd08741282a956c221f9d67d378

Rewrite "Testing a Certain Property of an Object" as "Defining a Custom Matcher Class", and fix the code examples.

PiperOrigin-RevId: 445252626
Change-Id: I9f038cb669d3da6743606343c2341fc59725d722

PiperOrigin-RevId: 413674665
Change-Id: I466f87348390f42434a70f183efdf0557be9dddd

add missing using ::testing::DoAll when DoAll used in example

PiperOrigin-RevId: 402416497

Create new Mocking Reference

PiperOrigin-RevId: 376951575

Create Assertions Reference

PiperOrigin-RevId: 375824718

Fix a comment in a code snippet.

PiperOrigin-RevId: 374504337

Docs: Clarify that expectations must be set before mocks are exercised
PiperOrigin-RevId: 373644072

Clean up links to Matchers Reference

PiperOrigin-RevId: 370821457

Move matchers reference from cheat sheet into its own document

PiperOrigin-RevId: 370749693

Update the `DescribeTo` signature in the code example at the Writing New Polymorphic Matchers section in gmock_cook_book.

`os` should be a pointer to be consistent with the implementation, which dereference it as `*os`.

PiperOrigin-RevId: 370693387

Update the example for Notify to use a lambda.
It is much less boilerplate and easier to remember.

PiperOrigin-RevId: 367284222

Clarify explanation of mocking free functions

PiperOrigin-RevId: 364943561

Code style cleanup in docs

PiperOrigin-RevId: 364907938

Add files for GitHub Pages

PiperOrigin-RevId: 358289110

Add files for GitHub Pages

PiperOrigin-RevId: 357096486

Internal change

PiperOrigin-RevId: 356867746

Fix table formatting in cookbook

PiperOrigin-RevId: 355659722

Add a note to recommend against using `Property()` for functions that the test author does not own.

PiperOrigin-RevId: 355295183

Document the fact that MatchAndExplain(T, MatchResultListener*) is supported.

PiperOrigin-RevId: 354172275

Add missing `is_gtest_matcher` to the polymorphic matcher example.

PiperOrigin-RevId: 353881883

Delete internal tags from docs

PiperOrigin-RevId: 353769887

Merge CONTRIBUTORS, delete LICENSEs in googletest/ and googlemock/

PiperOrigin-RevId: 352558822

Fixes #3222, fixes #3225, closes #3223

PiperOrigin-RevId: 352066131

Add "using is_gtest_matcher = void" to the DivisibleBy7Matcher example.

PiperOrigin-RevId: 351797821

Change Matcher<T> to allow binding an implementation by value directly:
 - Drop the requirement of MatcherInterface. Doing manual type erasure avoid
   extra layers in many cases.
 - Avoid the adaptor for `MatcherInterface<T>` and `MatcherInterface<const T&>` mismatch.
 - Use a small object optimization when possible. This makes things like
   `_` and `Eq(1)` really cheap and do not require memory allocations.
 - Migrate some matchers to the new model to speed them up and to test the new framework. More matchers to come in future changes.

PiperOrigin-RevId: 350580998

Move all docs into top-level docs/ directory

PiperOrigin-RevId: 350211277

Give each of Naggy/Nice/StrictMock a base class whose constructor runs before
the mocked class's constructor, and a destructor that runs after the mocked
class's destructor, so that any mock methods run in either the constructor or
destructor use the same strictness as other calls.

PiperOrigin-RevId: 348511612