summaryrefslogtreecommitdiffstats
path: root/googlemock/test/gmock-more-actions_test.cc
Commit message (Collapse)AuthorAgeFilesLines
* Add qualifier to avoid argument dependent lookupTom Hughes2023-04-281-1/+1
| | | | | PiperOrigin-RevId: 527740306 Change-Id: I61308cc232c346d5ff8b0548d4c552a59633fffc
* Add missing std includesTom Hughes2023-04-201-0/+4
| | | | | PiperOrigin-RevId: 525850646 Change-Id: I64387f5b933beb79cd05636dca81b7a75213383e
* Use GTEST_DISABLE_MSC_WARNINGS macros to disable warningsTom Hughes2023-01-301-10/+6
| | | | | | | | | Prior to this change we had a mixture of pragmas and GTEST_DISABLE_MSC_WARNINGS; this change consolidates all instances to use the macros. PiperOrigin-RevId: 505786926 Change-Id: I2be8f6304387393995081af42ed32c2ad1bba5a7
* Running clang-format over all of GoogleTestAbseil Team2022-03-151-18/+15
| | | | | | | | | | | | | | | | 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
* Change `ReturnArg` to use perfect forwarding of arguments (#3733)Dino Radakovic2022-01-261-0/+6
| | | | | PiperOrigin-RevId: 424355706 Change-Id: I618e5574b4b2c56a343905c20d8cc6d2a70cbcd1
* Googletest exportofats2021-01-261-47/+869
| | | | | | Remove scripts for code generating together with related files. PiperOrigin-RevId: 352805926
* Googletest exportAbseil Team2020-08-271-4/+2
| | | | | | | | Replace uses of ACTION_TEMPLATE and ACTION_P with manually written functors. The latter provide better error diagnostics. This fixes https://github.com/google/googletest/issues/2729. PiperOrigin-RevId: 328573022
* Googletest exportAbseil Team2020-08-071-0/+29
| | | | | | | | | | Fixing exception-safety bug in googletest. Previously, if an exception was thrown during a call to a mock that would have triggered an error, the error was discarded. Fixes #2890 PiperOrigin-RevId: 325017806
* Googletest exportkuzkry2019-09-161-1/+0
| | | | | | | | | Merge 3bdefdb473d304803d2a38e2a2cd5cdc1827c3bd into fb49e6c164490a227bbb7cf5223b846c836a0305 Closes #2407 COPYBARA_INTEGRATE_REVIEW=https://github.com/google/googletest/pull/2407 from kuzkry:StaticAssertTypeEq 3bdefdb473d304803d2a38e2a2cd5cdc1827c3bd PiperOrigin-RevId: 269255328
* Googletest exportmisterg2018-10-291-10/+1
| | | | | | Remove linked_ptr and use std::shared_ptr instead PiperOrigin-RevId: 219129336
* Googletest exportAbseil Team2018-10-261-1/+10
| | | | | | Remove linked_ptr and use std::shared_ptr instead PiperOrigin-RevId: 218618184
* Googletest exportmisterg2018-10-261-10/+1
| | | | | | Remove linked_ptr and use std::shared_ptr instead PiperOrigin-RevId: 218571466
* Unconditionally use std::tuple.Abseil Team2018-10-091-82/+80
| | | | | | Remove all mention of TR1 tuple and our own implementation of tuple. PiperOrigin-RevId: 216395043
* Apply clang-tidy modernize-use-nullptr to googletest.Abseil Team2018-10-051-1/+2
| | | | | | | | | | | Now that googletest has moved to C++11, it should no longer use NULL or 0 for the null pointer. This patch converts all such usages to nullptr using clang-tidy. This prevents LLVM from issuing -Wzero-as-null-pointer-constant warnings. PiperOrigin-RevId: 215814400
* Comments changes, no functionality changesrefs/pull/1740/headGennadiy Civil2018-08-141-2/+1
|
* mergingGennadiy Civil2018-04-131-1/+2
|
* more fixing osx libstd++ bugsrefs/pull/1568/headGennadiy Civil2018-04-121-1/+2
|
* merging, fix OSX issueGennadiy Civil2018-04-121-1/+2
|
* mergingGennadiy Civil2018-04-121-9/+5
|
* Use std::string and ::string explicitly in gtest and gmock code.refs/pull/1089/headNico Weber2017-05-151-74/+77
| | | | | | | | | 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.
* Googlemock has some tuples containing lvalue refs in its unit tests.refs/pull/583/headBilly Donahue2015-09-081-2/+5
| | | | | | | | | | | | | | | These tuples are created with make_tuple, which is given temporaries. The make_tuple is in a function argument list. A possibly overzealous static_assert in libc++'s std::tuple ctor is firing in our 'Perform(make_tuple("hi"))' calls, so we can't use its make_tuple here. Instead we will use explicitly-constructed tuples constructed from non-temporary strings. Workaround for llvm bug: https://llvm.org/bugs/show_bug.cgi?id=20855 An alternative to https://github.com/google/googletest/pull/580 .
* move googlemock files into googlemock/ subdirBilly Donahue2015-08-251-0/+705
generated by cgit v0.12 at 2024-09-03 14:53:35 (GMT)