summaryrefslogtreecommitdiffstats
path: root/googlemock/src/gmock-matchers.cc
Commit message (Collapse)AuthorAgeFilesLines
* Print mismatches for UnorderedElements() of different sizes.Abseil Team2024-05-201-14/+13
| | | | | | | Changes the behavior of UnorderedElements()/UnorderedElementsAreArray() to print items-without-matchers and matchers-without-items in the case where the actual and expected are different sizes. PiperOrigin-RevId: 635451316 Change-Id: I2181bb28a14c14cdb577af9268d403e12e942bea
* changed http to httpsrefs/pull/4349/headsthd2023-08-221-1/+1
|
* Internal Code ChangeAbseil Team2023-03-031-1/+1
| | | | | PiperOrigin-RevId: 513770561 Change-Id: I82fbed177c6ba4e2e5b776ae3e0255c868e32e25
* Refactor matrix verification into VerifyMatchMatrix.refs/pull/4082/headAbseil Team2022-12-121-0/+17
| | | | | PiperOrigin-RevId: 494786543 Change-Id: I7769558dd2ca046d8957bf352dc04cfb48ff7c3a
* Running clang-format over all of GoogleTestAbseil Team2022-03-151-1/+0
| | | | | | | | | | | | | | | | A few tests are examining code locations and looking af the resulting line numbers to verify that GoogleTest shows those to users correctly. Some of those locations change when clang-format is run. For those locations, I've wrapped portions in: // clang-format off ... // clang-format on There may be other locations that are currently not tickled by running clang-format. PiperOrigin-RevId: 434844712 Change-Id: I3a9f0a6f39eff741c576b6de389bef9b1d11139d
* Include the param names in the generated description of the MATCHER_P matchers.Abseil Team2021-12-271-4/+8
| | | | | PiperOrigin-RevId: 418497526 Change-Id: Ie53c3c0810c10a32cbcb941e3ca1ee8fb1ddd9f9
* Remove all uses of GTEST_DISALLOW_{MOVE_,}ASSIGN_.Arthur O'Dwyer2020-04-241-2/+0
| | | | | | | | | | | | | | | | | | | | | | None of these are strictly needed for correctness. A large number of them (maybe all of them?) trigger `-Wdeprecated` warnings on Clang trunk as soon as you try to use the implicitly defaulted (but deprecated) copy constructor of a class that has deleted its copy assignment operator. By declaring a deleted copy assignment operator, the old code also caused the move constructor and move assignment operator to be non-declared. This means that the old code never got move semantics -- "move-construction" would simply call the defaulted (but deprecated) copy constructor instead. With the new code, "move-construction" calls the defaulted move constructor, which I believe is what we want to happen. So this is a runtime performance optimization. Unfortunately we can't yet physically remove the definitions of these macros from gtest-port.h, because they are being used by other code internally at Google (according to zhangxy988). But no new uses should be added going forward.
* Googletest exportAbseil Team2020-02-071-1/+0
| | | | | | | | Get rid of gmock-generated-matchers.h and gmock-generated-matchers.h.pump. Stop using pump for MATCHER* macroses generation. PiperOrigin-RevId: 293878808
* Googletest exportdurandal2018-11-201-110/+0
| | | | | | Move the Matcher<T> interface to googletest so I can use it to extend death test regex matching in a subsequent change. PiperOrigin-RevId: 221675910
* Comments changes, no functionality changesrefs/pull/1740/headGennadiy Civil2018-08-141-2/+1
|
* merging gmock matchers 1Gennadiy Civil2018-04-041-6/+52
|
* merging, gmock -1Gennadiy Civil2018-03-221-35/+42
|
* gmock merging -2Gennadiy Civil2018-02-271-77/+119
|
* moving JoinAsTuple to internalGennadiy Civil2018-02-121-19/+0
|
* Merge pull request #764 from flyd1005/wip-fix-typoGennadiy Civil2017-08-021-1/+1
|\ | | | | remove duplicated words
| * remove duplicated wordsrefs/pull/764/headLi Peng2016-04-271-1/+1
| | | | | | | | Signed-off-by: Li Peng <lip@dtdream.com>
* | Use std::string and ::string explicitly in gtest and gmock code.refs/pull/1089/headNico Weber2017-05-151-5/+4
|/ | | | | | | | | This merges a Google-internal change (117235625). Original CL description: This CL was created manually in about an hour with sed, a Python script to find all the places unqualified 'string' was mentioned, and some help from Emacs to add the "std::" qualifications, plus a few manual tweaks.
* move googlemock files into googlemock/ subdirBilly Donahue2015-08-251-0/+498