- 14 Oct, 2020 5 commits
-
-
Abseil Team authored
Add ::testing::FieldsAre matcher for objects that support get<> and structured bindings. PiperOrigin-RevId: 337165285
-
Abseil Team authored
Removing a semicolon that triggers a lint error in sample code. PiperOrigin-RevId: 337095451
-
Abseil Team authored
Use absl::StrCat in MATCHER_P example for consistency with https://abseil.io/tips/3 PiperOrigin-RevId: 336878481
-
Abseil Team authored
Suggest using generic lambdas for composing macros. Long chains of macros hurt legibility; generic lambdas are an easy way to abbreviate them, but are not an obvious solution to casual users. Compare: EXPECT_THAT(f(), ElementsAre( Property(&MyClass::foo, Property(&OtherClass::bar, Contains("x"))), Property(&MyClass::foo, Property(&OtherClass::bar, Contains("y")))); to: EXPECT_THAT(f(), ElementsAre(HasFooBar("x"), HasFooBar("y"))); PiperOrigin-RevId: 336870137 -
Abseil Team authored
Make the code Python3 compliant. PiperOrigin-RevId: 336144198
-
- 12 Oct, 2020 1 commit
-
-
Peter Newman authored
-
- 29 Sep, 2020 1 commit
-
-
Abseil Team authored
Fix typo PiperOrigin-RevId: 333745750
-
- 27 Sep, 2020 1 commit
-
-
keshavgbpecdelhi authored
Please note that changing the default value for a type can make [you]* test..... Here "you" word doesn't make sense.. rather "your" seems to make it understandable.
-
- 24 Sep, 2020 1 commit
-
-
Abseil Team authored
Address OSS Issue #2463 https://github.com/google/googletest/issues/2463 PiperOrigin-RevId: 333289989
-
- 20 Sep, 2020 2 commits
-
-
Abseil Team authored
Simplify FooConcrete static calls in googlemock cookbook. PiperOrigin-RevId: 332437041
-
Abseil Team authored
Reduce the demangled name bloat of the Action constructor. PiperOrigin-RevId: 332234887
-
- 10 Sep, 2020 1 commit
-
-
Abseil Team authored
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: 330614454
-
- 27 Aug, 2020 1 commit
-
-
Abseil Team authored
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
-
- 25 Aug, 2020 1 commit
-
-
xerus2000 authored
-
- 24 Aug, 2020 2 commits
-
-
Abseil Team authored
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
-
Abseil Team authored
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
-
- 12 Aug, 2020 1 commit
-
-
Abseil Team authored
internal change PiperOrigin-RevId: 326080000
-
- 07 Aug, 2020 3 commits
-
-
Abseil Team authored
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
-
Abseil Team authored
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
-
Abseil Team authored
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
-
- 03 Aug, 2020 10 commits
-
-
Vladimir Goncharov authored
-
Vladimir Goncharov authored
-
Vladimir Goncharov authored
-
Vladimir Goncharov authored
-
Vladimir Goncharov authored
-
Vladimir Goncharov authored
-
Vladimir Goncharov authored
-
Vladimir Goncharov authored
-
Vladimir Goncharov authored
-
Vladimir Goncharov authored
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
-
- 28 Jul, 2020 2 commits
-
-
Abseil Team authored
Internal documentation change. PiperOrigin-RevId: 323612305
-
ofats authored
Stop using ADL for InvokeArgument action. PiperOrigin-RevId: 323234396
-
- 15 Jul, 2020 1 commit
-
-
ofats authored
Move matchers' tests from *generated* to common files. PiperOrigin-RevId: 320954068
-
- 09 Jul, 2020 3 commits
-
-
ofats authored
Replace ByRef with std::ref everywhere in docs. PiperOrigin-RevId: 320002303
-
Abseil Team authored
Cleanup: Error message grammar fix. PiperOrigin-RevId: 319992912
-
Abseil Team authored
Fix mismatch between `int` and `int32_t` in the parse function. On some platforms, those are different types. PiperOrigin-RevId: 319991862
-
- 05 Jul, 2020 1 commit
-
-
Abseil Team authored
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
-
- 26 Jun, 2020 2 commits
-
-
Abseil Team authored
Normalize headers in gMock docs Increasing Header levels on two pages, to better match other pages in the same directory. PiperOrigin-RevId: 318280892
-
Abseil Team authored
Update auto_mock to support C++17 nested namespaces PiperOrigin-RevId: 318192214
-
- 15 Jun, 2020 1 commit
-
-
Abseil Team authored
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
-