1. 12 Dec, 2022 1 commit
  2. 15 Mar, 2022 1 commit
    • Abseil Team's avatar
      Running clang-format over all of GoogleTest · b007c54f
      Abseil Team authored
      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
      b007c54f
  3. 27 Dec, 2021 1 commit
  4. 24 Apr, 2020 1 commit
    • Arthur O'Dwyer's avatar
      Remove all uses of GTEST_DISALLOW_{MOVE_,}ASSIGN_. · 766ac2e1
      Arthur O'Dwyer authored
      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.
      766ac2e1
  5. 07 Feb, 2020 1 commit
    • Abseil Team's avatar
      Googletest export · 41b5f149
      Abseil Team authored
      Get rid of gmock-generated-matchers.h and gmock-generated-matchers.h.pump.
      
      Stop using pump for MATCHER* macroses generation.
      
      PiperOrigin-RevId: 293878808
      41b5f149
  6. 20 Nov, 2018 1 commit
    • durandal's avatar
      Googletest export · 8e86f672
      durandal authored
      Move the Matcher<T> interface to googletest so I can use it to extend death test regex matching in a subsequent change.
      
      PiperOrigin-RevId: 221675910
      8e86f672
  7. 14 Aug, 2018 1 commit
    • Gennadiy Civil's avatar
      · a3c0dd0f
      Gennadiy Civil authored
      Comments changes, no functionality changes
      a3c0dd0f
  8. 04 Apr, 2018 1 commit
    • Gennadiy Civil's avatar
      · e55089ec
      Gennadiy Civil authored
      merging gmock matchers 1
      e55089ec
  9. 22 Mar, 2018 1 commit
  10. 27 Feb, 2018 1 commit
  11. 12 Feb, 2018 1 commit
  12. 15 May, 2017 1 commit
    • Nico Weber's avatar
      Use std::string and ::string explicitly in gtest and gmock code. · 09fd5b3e
      Nico Weber authored
      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.
      09fd5b3e
  13. 27 Apr, 2016 1 commit
  14. 25 Aug, 2015 1 commit
  15. 24 Mar, 2014 1 commit
  16. 28 Jul, 2013 1 commit
  17. 25 Mar, 2013 1 commit
  18. 20 May, 2011 1 commit
  19. 14 Sep, 2010 1 commit
  20. 08 Jun, 2010 1 commit
  21. 01 Dec, 2009 1 commit
  22. 19 Feb, 2009 1 commit
  23. 10 Dec, 2008 1 commit