- 13 Aug, 2021 1 commit
-
-
Abseil Team authored
Identify bad specs of the type (const something, ...). PiperOrigin-RevId: 390346843
-
- 04 Aug, 2021 1 commit
-
-
Abseil Team authored
Introduce a new matcher for unescaping Base-64 strings to gmock. PiperOrigin-RevId: 388471904
-
- 24 Jul, 2021 1 commit
-
-
slowy07 authored
-
- 22 Jul, 2021 1 commit
-
-
Abseil Team authored
Delete GOOGLETEST_CM.* tags from C++ code. PiperOrigin-RevId: 386268534
-
- 09 Jul, 2021 1 commit
-
-
Abseil Team authored
Suppress a clang-tidy warning in the MATCHER(name, description) macro. PiperOrigin-RevId: 383587271
-
- 07 Jul, 2021 1 commit
-
-
Abseil Team authored
Add `Conditional` wrapper to gtest This follows an initial proposal for an 'EqIff` matcher. `Conditional` was considered more precise as an EqIff() matcher may suffer from `Iff` not being universally understood. PiperOrigin-RevId: 383407665
-
- 30 Jun, 2021 1 commit
-
-
Abseil Team authored
Implement 'Contains(e).Times(n)' matcher modifier which allows to test for arbitrary occurrences including absence with Times(0). PiperOrigin-RevId: 382210276
-
- 15 Jun, 2021 1 commit
-
-
Vasilii Pochkaenko authored
-
- 13 May, 2021 1 commit
-
-
Abseil Team authored
Support templating MockFunction over function objects besides std::function. PiperOrigin-RevId: 373586967
-
- 15 Apr, 2021 1 commit
-
-
John Bampton authored
-
- 13 Apr, 2021 1 commit
-
-
Abseil Team authored
Update docs to point to the github.io pages. PiperOrigin-RevId: 367711335
-
- 17 Mar, 2021 1 commit
-
-
Austin Sullivan authored
An incorrect link is output to the user when these conditions are met.
-
- 16 Mar, 2021 1 commit
-
-
Abseil Team authored
Internal change PiperOrigin-RevId: 362040448
-
- 09 Mar, 2021 1 commit
-
-
Abseil Team authored
PiperOrigin-RevId: 361213113
-
- 18 Feb, 2021 2 commits
-
-
Abseil Team authored
Update stale links to `gmock_cook_book.md`. I'm a new googletest user and found these links broken when reading the documentation. PiperOrigin-RevId: 357786392
-
Abseil Team authored
Make include guards conform with https://google.github.io/styleguide/cppguide.html#The__define_Guard, attempt #2 PiperOrigin-RevId: 357056902
-
- 11 Feb, 2021 4 commits
-
-
Abseil Team authored
Mark move constructor noexcept PiperOrigin-RevId: 356772642
-
Abseil Team authored
Revert include guard fix PiperOrigin-RevId: 356588893
-
Abseil Team authored
Fix build for MinGW + clang In [1], empty_bases "is only supported when using the Microsoft C++ ABI." Disable it for MinGW. https://clang.llvm.org/docs/AttributeReference.html#empty-bases PiperOrigin-RevId: 356373782
-
Abseil Team authored
Make include guards conform with https://google.github.io/styleguide/cppguide.html#The__define_Guard PiperOrigin-RevId: 355882793
-
- 05 Feb, 2021 1 commit
-
-
Abseil Team authored
Remove uses of GTEST_HAS_TYPED_TEST_P and GTEST_HAS_TYPED_TEST. PiperOrigin-RevId: 353935996
-
- 26 Jan, 2021 4 commits
-
-
ofats authored
Remove scripts for code generating together with related files. PiperOrigin-RevId: 352805926
-
Abseil Team authored
Stop using pump for generating internal/custom/gmock-generated-actions.h PiperOrigin-RevId: 352660735
-
Abseil Team authored
Internal change PiperOrigin-RevId: 352607401
-
Abseil Team authored
Merge CONTRIBUTORS, delete LICENSEs in googletest/ and googlemock/ PiperOrigin-RevId: 352558822
-
- 14 Jan, 2021 1 commit
-
-
Abseil Team authored
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
-
- 22 Dec, 2020 1 commit
-
-
Abseil Team authored
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
-
- 12 Dec, 2020 1 commit
-
-
Abseil Team authored
Add static_asserts that verify that no class hierarchy contains more than one of {NiceMock, NaggyMock, StrictMock}. This sort of nesting has always been disallowed, but this CL adds a compile-time check to prevent it. PiperOrigin-RevId: 347037822
-
- 09 Dec, 2020 1 commit
-
-
Abseil Team authored
Introduce a new `Address` matcher to gmock. PiperOrigin-RevId: 346344591
-
- 07 Dec, 2020 1 commit
-
-
Abseil Team authored
Add a `Pointer` matcher as an analog to `Pointee`. Similar to `Pointee`, `Pointer` works with either raw or smart pointers and allows creating a matcher like Pointer(Eq(foo)) for smart pointers. PiperOrigin-RevId: 346164768
-
- 12 Nov, 2020 1 commit
-
-
Abseil Team authored
Use a tagged constructor for FlatTuple instead. Some versions of MSVC are getting confused with that constructor and generating invalid code. PiperOrigin-RevId: 342050957
-
- 09 Nov, 2020 2 commits
-
-
Abseil Team authored
Change ACTION{,_Pn,_TEMPLATE} macros to build functors rather than ActionInterface<> subclasses, thus changing the Action<> wrappers they create to use the modernized (non-const) argument tuple type, allowing these macros to mutate their arguments. Functor-based Action<>s deep-copy the implementing object, so have the functors use a shared_ptr to the non-trivial state of bound value parameters. No longer specialize that shared state to the particular action signature, encoding that information instead only in the instantiation of the implementation function. PiperOrigin-RevId: 341116208 -
Abseil Team authored
GMock: Make Truly explain when it fails I just wrote a test that had a matcher of the form Optional(AllOf( SomeMatcher, SomeOtherMatcher, Truly(SomePredicate))) The predicate failed, the other two matchers succeeded, and I got a hard-to-interpret message saying that the value in the optional "didn't match". Didn't match what? This change improves situations like that slightly by having Truly explain to its result listener when it fails. When there are multiple Trulys in an AllOf, there will be some ambiguity, but it will at least provide more information than right now. PiperOrigin-RevId: 341105141
-
- 06 Nov, 2020 1 commit
-
-
Abseil Team authored
Add support for ref qualifiers in MOCK_METHOD. PiperOrigin-RevId: 341047839
-
- 05 Nov, 2020 1 commit
-
-
ofats authored
Rewrite InvokeArgument action without using pump. PiperOrigin-RevId: 340861582
-
- 30 Oct, 2020 1 commit
-
-
Abseil Team authored
Remove obsolete comment about non-const references. They used to be banned by the C++ style guide, but positions shifted, and this comment is no longer up to date. There's another reference (heh) on lines 816-819 to how gmock is a "general framework", with the possible implication that support for non-const references was weird in some way and only there to be "general", but I left it alone because I don't really feel I understand what it's saying. PiperOrigin-RevId: 339323428
-
- 15 Oct, 2020 1 commit
-
-
dmauro authored
Fixes build warnings from previous CL Add CMake to internal presubmit to prevent these PiperOrigin-RevId: 337325504
-
- 14 Oct, 2020 1 commit
-
-
Abseil Team authored
Add ::testing::FieldsAre matcher for objects that support get<> and structured bindings. PiperOrigin-RevId: 337165285
-
- 07 Oct, 2020 1 commit
-
-
Aralox authored
Issue 2135: Change template args in NiceMock, NaggyMock and StrictMock from A1, A2, ... to TArg1, TArg2,... to avoid clash with legacy header files
-
- 29 Sep, 2020 1 commit
-
-
Abseil Team authored
Fix typo PiperOrigin-RevId: 333745750
-