summaryrefslogtreecommitdiffstats
path: root/googlemock
Commit message (Collapse)AuthorAgeFilesLines
...
* Merge pull request #2994 from xerus2000:gmock-docsDerek Mauro2020-09-101-4/+6
|\ | | | | | | PiperOrigin-RevId: 330545489
| * Add timestamp to in old method mock macro guiderefs/pull/2994/headxerus20002020-08-251-4/+5
| |
* | Googletest exportAbseil Team2020-08-274-183/+162
|/ | | | | | | | 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-241-2/+3
| | | | | | | | | | | Workaround static assert in early versions libc++ The error is "Attempted to construct a reference element in a tuple with an rvalue". We can fix this by putting everything into a non temporary tuple_args and implitly convert to the other tuple types. This avoids binding an rvalue reference to an lvalue reference inside the tuple. PiperOrigin-RevId: 327624990
* Merge pull request #2904 from AmatanHead:throw-matchersvslashg2020-08-242-0/+353
|\ | | | | | | PiperOrigin-RevId: 327294137
| * Remove ThrowsMessageHasSubstr and fix some nits after reviewrefs/pull/2904/headVladimir Goncharov2020-08-032-68/+22
| |
| * Cleanup a bulky expression, document implementation detailsVladimir Goncharov2020-08-031-8/+30
| |
| * Fix build under msvcVladimir Goncharov2020-08-031-5/+5
| |
| * Update tests after changing an error messageVladimir Goncharov2020-08-031-2/+2
| |
| * Fix build under msvcVladimir Goncharov2020-08-031-1/+15
| |
| * Add a test to ensure that the `Throws` matcher only invokes its argument once.Vladimir Goncharov2020-08-031-0/+30
| |
| * Add a test for duplicate catch clauses in throw matchers, fix a couple of ↵Vladimir Goncharov2020-08-032-2/+7
| | | | | | | | nitpicks.
| * Add missing documentation pieceVladimir Goncharov2020-08-032-1/+22
| |
| * Small improvements: code style and property nameVladimir Goncharov2020-08-032-6/+4
| |
| * Add matchers for testing exception propertiesVladimir Goncharov2020-08-032-0/+316
| | | | | | | | | | | | This PR adds matchers that accept a callable and verify that when invoked, it throws an exception with the given type and properties. Fixes #952
* | Googletest exportAbseil Team2020-08-243-10/+42
| | | | | | | | | | | | | | | | | | Fix DoAll to work with move-only sink arguments. This changes types of the first n - 1 actions so that they only get a readonly view of the arguments. The last action will accept move only objects. PiperOrigin-RevId: 327031893
* | Googletest exportAbseil Team2020-08-125-0/+10
| | | | | | | | | | | | internal change PiperOrigin-RevId: 326080000
* | Googletest exportAbseil Team2020-08-072-21/+66
| | | | | | | | | | | | | | | | | | | | 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 exportAbseil Team2020-08-073-21/+7
| | | | | | | | | | | | | | | | | | Fix DoAll to work with move-only sink arguments. This changes types of the first n - 1 actions so that they only get a readonly view of the arguments. The last action will accept move only objects. PiperOrigin-RevId: 324619666
* | Googletest exportAbseil Team2020-08-073-7/+21
|/ | | | | | | | | Fix DoAll to work with move-only sink arguments. This changes types of the first n - 1 actions so that they only get a readonly view of the arguments. The last action will accept move only objects. PiperOrigin-RevId: 324600664
* Googletest exportAbseil Team2020-07-281-1/+1
| | | | | | Internal documentation change. PiperOrigin-RevId: 323612305
* Googletest exportofats2020-07-284-59/+24
| | | | | | Stop using ADL for InvokeArgument action. PiperOrigin-RevId: 323234396
* Googletest exportofats2020-07-156-1483/+1167
| | | | | | Move matchers' tests from *generated* to common files. PiperOrigin-RevId: 320954068
* Merge pull request #2903 from AmatanHead:informative-exception-assertsvslashg2020-07-152-0/+160
|\ | | | | | | PiperOrigin-RevId: 320425648
* | Googletest exportofats2020-07-092-21/+18
| | | | | | | | | | | | Replace ByRef with std::ref everywhere in docs. PiperOrigin-RevId: 320002303
* | Googletest exportAbseil Team2020-07-092-2/+2
| | | | | | | | | | Cleanup: Error message grammar fix. PiperOrigin-RevId: 319992912
* | Googletest exportAbseil Team2020-07-091-1/+1
| | | | | | | | | | | | | | Fix mismatch between `int` and `int32_t` in the parse function. On some platforms, those are different types. PiperOrigin-RevId: 319991862
* | Googletest exportAbseil Team2020-07-051-1/+1
| | | | | | | | | | | | | | | | Improve compatibility with strict compilers targeting Windows Remove an unnecessary ##, which could result in warnings about invalid preprocessor tokens when pasting to an initial '(' PiperOrigin-RevId: 319277617
* | Googletest exportAbseil Team2020-06-262-54/+54
| | | | | | | | | | | | | | | | Normalize headers in gMock docs Increasing Header levels on two pages, to better match other pages in the same directory. PiperOrigin-RevId: 318280892
* | Googletest exportAbseil Team2020-06-262-8/+7
|/ | | | | | Update auto_mock to support C++17 nested namespaces PiperOrigin-RevId: 318192214
* Googletest exportAbseil Team2020-06-151-5/+5
| | | | | | | | gMock Cookbook: Fix incorrect comment about EXPECT priority order It's actually the last matching expectation that's used, not the first. PiperOrigin-RevId: 316490770
* Googletest exportAbseil Team2020-06-102-34/+70
| | | | | | Change string matchers, like HasSubstr, to accept `string_view` input if available. PiperOrigin-RevId: 315726484
* Googletest exportAbseil Team2020-06-051-2/+2
| | | | | | | | gMock Cookbook: Slight rewording Remove "I" because documentation can have multiple authors. And remove unnecessary "guy". PiperOrigin-RevId: 314533746
* Merge pull request #2755 from Conan-Kudo:set-version-for-libsGennadiy Rozental2020-06-031-0/+2
|\ | | | | | | PiperOrigin-RevId: 314427570
| * Set the version for the librariesrefs/pull/2755/headNeal Gompa2020-03-211-0/+2
| | | | | | | | | | | | | | | | | | When building packaged shared libraries for use, having the version set makes it so that the soname is set correctly for parallel installation. This change is derived from the one used for the Fedora gtest package. Signed-off-by: Neal Gompa <ngompa13@gmail.com>
* | Googletest exportAbseil Team2020-06-031-0/+5
| | | | | | | | | | | | Note that EXPECT_EQ(actual_value, expected_value) or EXPECT_THAT(actual_value, Eq(expected_value)) is preferred over EXPECT_THAT(actual_value, expected_value). PiperOrigin-RevId: 314350852
* | Googletest exportdmauro2020-05-283-15/+2
| | | | | | | | | | | | Rollback of warning on unused ACTION result change PiperOrigin-RevId: 313380971
* | Googletest exportAbseil Team2020-05-281-1/+1
| | | | | | | | | | | | Spell out namespace for absl::Notification. PiperOrigin-RevId: 312300192
* | Googletest exportdurandal2020-05-281-3/+5
| | | | | | | | | | | | Silence MSVC C4100 (unused formal parameter) to fix breakage from recently added testcase. This warning is silenced in many files throughout googletest, but was not needed here until this testcase was added. PiperOrigin-RevId: 312121200
* | Googletest exportAbseil Team2020-05-283-2/+15
| | | | | | | | | | | | | | | | | | | | | | | | Mark ACTION_Pn()-generated functions as must-use-result. This catches when a client creates an action and discards it, thinking that the action has actually been applied to something. This will help people who make the mistake of defining, for example, both `void Use(Foo*)` and `ACTION(Use) { Use(arg); }` for later application to a Foo. With such an overload, a client may then write `Use();`, forgetting the param and being confused why nothing happens. This also catches when a client defines their own action in terms of an ACTION()-generated one, invokes the ACTION's builder, and then fails to invoke the resulting action, thinking it's operating on the outer action's parameters. PiperOrigin-RevId: 312108101
* | Googletest exportAbseil Team2020-05-282-3/+25
| | | | | | | | | | | | | | | | Fix the ACTION* macros to allow for more than 10 arguments in the action. Only the first 10 will be passed as individual arguments as `argN`, but the rest can be accessed from the `args` tuple. PiperOrigin-RevId: 311542098
* | Googletest exportAbseil Team2020-05-131-0/+9
| | | | | | | | | | | | Addresses https://github.com/google/googletest/pull/2784 PiperOrigin-RevId: 310902202
* | Googletest exportAbseil Team2020-05-071-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix `-Wgnu-zero-variadic-macro-arguments` in GMock Passing zero arguments to the variadic part of a macro is a GNU extension and triggers warnings when build projects using GMock with `-pedantic`. - Fix uses of `GMOCK_PP_INTERNAL_16TH` to always receive at least 17 arguments. (this was triggered when `GMOCK_PP_NARG` or `GMOCK_PP_HAS_COMMA` were used with an argument containing no commas). - Fix `GMOCK_PP_HEAD` to append a dummy unused argument so that `GMOCK_PP_INTERNAL_HEAD` always has two arguments. PiperOrigin-RevId: 310414611
* | Merge pull request #2830 from keshavgbpecdelhi:patch-1vslashg2020-05-051-16/+16
|\ \ | | | | | | | | | PiperOrigin-RevId: 309951872
| * | Removed a typo in README.md refs/pull/2830/headkeshavgbpecdelhi2020-05-011-1/+1
| | | | | | | | | There is an unnecessary comma before 'and'
* | | Googletest exportAbseil Team2020-05-011-1/+1
| | | | | | | | | | | | | | | | | | Fix link to "high-perf dependency injection technique". PiperOrigin-RevId: 308893893
* | | Googletest exportAbseil Team2020-05-011-2/+2
| | | | | | | | | | | | | | | | | | internal change PiperOrigin-RevId: 308648034
* | | Merge pull request #2815 from Quuxplusone:simpleGennadiy Rozental2020-05-018-157/+7
|\ \ \ | | | | | | | | | | | | PiperOrigin-RevId: 308625388
| * | | Fix a -Wdeprecated warning.Arthur O'Dwyer2020-04-241-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gmock-spec-builders.h:503:3: error: definition of implicit copy constructor for 'Expectation' is deprecated because it has a user-declared destructor [-Werror,-Wdeprecated] ~Expectation(); ^
| * | | Remove all uses of GTEST_DISALLOW_{MOVE_,}ASSIGN_.Arthur O'Dwyer2020-04-248-154/+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.
generated by cgit v0.12 at 2024-11-01 13:56:23 (GMT)