1. 05 Mar, 2019 1 commit
  2. 01 Mar, 2019 2 commits
  3. 20 Feb, 2019 1 commit
  4. 13 Feb, 2019 4 commits
  5. 12 Feb, 2019 3 commits
    • misterg's avatar
      Googletest export · c4ccab33
      misterg authored
      Internal Change
      
      PiperOrigin-RevId: 233614147
      c4ccab33
    • Abseil Team's avatar
      Googletest export · 28a96d18
      Abseil Team authored
      Fix matcher comparisons for std::reference_wrapper.
      
      The googletest docs indicate that std::reference_wrapper should be used to for
      objects that should not be copied by the matcher (in fact, the ByRef() function
      is basically the same as a call to std::cref).
      
      However, for many types (such as std::string), the overloaded operator== will
      not resolve correctly. Specifically, this is problematic if operator== depends
      on template argument deduction, where the same type is named on LHS and RHS.
      
      Because template argument deduction happens before any implict conversions for
      purposes of overload resolution, attempting to compare T with
      std::reference_wrapper<T> simply looks like a comparison of unlike types.
      
      For exapmle, std::reference_wrapper<std::string> is implicitly convertible to
      'const std::string&', which would be able to choose an overload specialization
      of operator==. However, the implicit conversion can only happen after template
      argument deduction for operator==, so a specialization that would other be an
      applicable overload is never considered.
      
      Note also that this change only affects matchers. There are good reasons that
      matchers may need to transparently hold a std::reference_wrapper. Other
      comparisons (like EXPECT_EQ, et. al.) don't need to capture a reference: they
      don't need to defer evaluation (as in googlemock), and they don't need to avoid
      copies (as the call chain of matchers does).
      
      PiperOrigin-RevId: 232499175
      28a96d18
    • Abseil Team's avatar
      Googletest export · dda0df3b
      Abseil Team authored
      Internal change
      
      PiperOrigin-RevId: 232362580
      dda0df3b
  6. 04 Feb, 2019 1 commit
    • misterg's avatar
      Googletest export · 52ea4f7b
      misterg authored
      Mark legacy _TEST_CASE_ macros as deprecated
      
      PiperOrigin-RevId: 232303251
      52ea4f7b
  7. 01 Feb, 2019 1 commit
    • Abseil Team's avatar
      Googletest export · 0ea2d8f8
      Abseil Team authored
      Fix stack overflow in AnyOfArray tests.
      
      PiperOrigin-RevId: 231881125
      0ea2d8f8
  8. 24 Jan, 2019 1 commit
    • Adam Cozzette's avatar
      Fixed "make dist" · 46b81732
      Adam Cozzette authored
      I made a few updates to the Makefile.am files so that "make dist"
      succeeds and produces a usable tarball. We need this for protobuf
      because the protobuf tarballs include a bundled copy of googletest.
      46b81732
  9. 23 Jan, 2019 1 commit
    • Abseil Team's avatar
      Googletest export · fdc59ffd
      Abseil Team authored
      Add AllOfArray matcher that verifies a value matches all member of some array/container/list/set/..., e.g:
      EXPECT_THAT(1, AnyOfArray({1, 2, 3}))
      In the simplest form this is identical to AnyOf(1, 2, 3). But unlike that one it works on containers.
      
      Add AnyOfArray matcher that verifies a value matches any member of some
      array/container/list/set/...
      
      PiperOrigin-RevId: 230403653
      fdc59ffd
  10. 22 Jan, 2019 1 commit
    • Abseil Team's avatar
      Googletest export · 569fba4d
      Abseil Team authored
      Make internal FunctionMocker class final
      
      PiperOrigin-RevId: 230332778
      569fba4d
  11. 18 Jan, 2019 1 commit
    • Abseil Team's avatar
      Googletest export · 9518a574
      Abseil Team authored
      Fix mocking method arguments with templated copy constructors.
      
      A previous change removed workarounds for old compilers from googletest and googlemock. Unfortunately, a bit of code that started as a workaround for Symbian's C++ compiler is still needed to avoid copy/move constructor ambiguity when mocking functions with certain argument types.
      
      The test case added by this CL is extracted from Chrome's codebase, and was discovered while attempting to roll googletest.
      
      PiperOrigin-RevId: 229801765
      9518a574
  12. 17 Jan, 2019 1 commit
    • Abseil Team's avatar
      Googletest export · 0adeadd2
      Abseil Team authored
      Refactor the `Invoke` and `InvokeWithoutArgs` actions:
       - Replace pump'd classes and functions with templates.
       - Make the polymorphic actions be polymorphic functors instead.
       - Fix Invoke(Callback*) to work with subclasses of the callbacks, instead of trying to diagnose that in gmock_doctor.
      
      PiperOrigin-RevId: 229604112
      0adeadd2
  13. 14 Jan, 2019 2 commits
    • Abseil Team's avatar
      Googletest export · 9acd065a
      Abseil Team authored
      Add move-only argument support to almost all remaining matchers.
      
      PiperOrigin-RevId: 229030728
      9acd065a
    • Abseil Team's avatar
      Googletest export · 097407fd
      Abseil Team authored
      Deduplicate testing::ReferenceWrapper with std::reference_wrapper.
      Minor cleanups in matchers_test.
      
      PiperOrigin-RevId: 229022872
      097407fd
  14. 08 Jan, 2019 2 commits
    • misterg's avatar
      Googletest export · f31bf1d3
      misterg authored
      Replace testing::internal::ImplicitlyConvertible with std::is_convertible
      Fixes #2054
      
      PiperOrigin-RevId: 228334305
      f31bf1d3
    • Abseil Team's avatar
      Googletest export · 216c37f0
      Abseil Team authored
      Drop generated file gmock-generated-internal-utils.h.
      
      PiperOrigin-RevId: 228232195
      216c37f0
  15. 07 Jan, 2019 1 commit
  16. 03 Jan, 2019 2 commits
    • misterg's avatar
      Googletest export · 3a460a26
      misterg authored
      TestCase->TestSuite refactoring
      
      PiperOrigin-RevId: 227702164
      3a460a26
    • Chris's avatar
      fix: Remove Arduino entry points · 4d62b5b9
      Chris authored
      Improved flexibility by removing the Arduino entry points in favor of manual calls to setup/loop that the user can call from their entry point.  This is the more common use case for Arudino.
      
      Also added the gtest/gmock_main files to the PlatformIO ignore list since we are not supporting that feature.
      4d62b5b9
  17. 02 Jan, 2019 2 commits
    • misterg's avatar
      Googletest export · 14c2fba7
      misterg authored
      Internal Change
      
      PiperOrigin-RevId: 227575279
      14c2fba7
    • Abseil Team's avatar
      Googletest export · f8b1c1af
      Abseil Team authored
      Remove the #ifs for old, unsupported and buggy compilers:
      * old versions of GCC & MSVC
      * Symbian
      
      PiperOrigin-RevId: 227116941
      f8b1c1af
  18. 21 Dec, 2018 2 commits
  19. 20 Dec, 2018 2 commits
    • Abseil Team's avatar
      Googletest export · 9494c45e
      Abseil Team authored
      Use std::function to implement type erasure in Action, wrapping the legacy
      ActionInterface if necessary.
      
      This makes functors / std::function the primary way to implement Action; the
      existing ActionInterface implementations are handled through ActionAdaptor.
      The existing actions are not (yet) migrated though; they'll pay the cost of one
      additional indirection - but that should be negligible.
      
      PiperOrigin-RevId: 226126137
      9494c45e
    • Abseil Team's avatar
      Googletest export · e26a3fa1
      Abseil Team authored
      Unifdef c++11-related macros from googletest now that it requires C++11.
      
      PiperOrigin-RevId: 225905601
      e26a3fa1
  20. 17 Dec, 2018 5 commits
    • misterg's avatar
      Googletest export · 9ab640ce
      misterg authored
      Suppress C4503 for MCVS , again
      
      PiperOrigin-RevId: 225895719
      9ab640ce
    • misterg's avatar
      Googletest export · 7515e399
      misterg authored
      Suppress C4503 for MCVS
      
      PiperOrigin-RevId: 225871050
      7515e399
    • Abseil Team's avatar
      Googletest export · b7dd6651
      Abseil Team authored
      Remove GTEST_REFERENCE_TO_CONST_ usage from GMock. In C++11, it's redundant.
      
      PiperOrigin-RevId: 225719210
      b7dd6651
    • Abseil Team's avatar
      Googletest export · 1ec20f87
      Abseil Team authored
      Allow container matchers to accept move-only containers.
      
      PiperOrigin-RevId: 225667441
      1ec20f87
    • Abseil Team's avatar
      Googletest export · 096fb37a
      Abseil Team authored
      Replace pump'd code for DoAll with variadic templates.
      
      PiperOrigin-RevId: 225584656
      096fb37a
  21. 13 Dec, 2018 1 commit
  22. 12 Dec, 2018 1 commit
    • Abseil Team's avatar
      Googletest export · 6ef59138
      Abseil Team authored
      The gmock matchers have a concept of MatchAndExpain; where the details of the
      matching are written to a "result listener". A matcher can avoid creating
      expensive debug info by checking result_listener->IsInterested(); but,
      unfortunately, the default matcher code (called from EXPECT_THAT) is always
      "interested".
      
      This change implements EXPECT_THAT matching to first run the matcher in a "not
      interested" mode; and then run it a second time ("interested") only if the
      match fails.
      
      PiperOrigin-RevId: 225036073
      6ef59138
  23. 11 Dec, 2018 2 commits
    • misterg's avatar
      Googletest export · 6cbd3753
      misterg authored
      rollback of 224929783
      
      PiperOrigin-RevId: 225008559
      6cbd3753
    • Abseil Team's avatar
      Googletest export · 06bb8d4d
      Abseil Team authored
      The gmock matchers have a concept of MatchAndExpain; where the details of the
      matching are written to a "result listener". A matcher can avoid creating
      expensive debug info by checking result_listener->IsInterested(); but,
      unfortunately, the default matcher code (called from EXPECT_THAT) is always
      "interested".
      
      This change implements EXPECT_THAT matching to first run the matcher in a "not
      interested" mode; and then run it a second time ("interested") only if the
      match fails.
      
      PiperOrigin-RevId: 224929783
      06bb8d4d