1. 02 Jan, 2019 1 commit
  2. 05 Oct, 2018 1 commit
    • Abseil Team's avatar
      Apply clang-tidy modernize-use-nullptr to googletest. · 4bb49ed6
      Abseil Team authored
      Now that googletest has moved to C++11, it should no longer
      use NULL or 0 for the null pointer. This patch converts all
      such usages to nullptr using clang-tidy.
      
      This prevents LLVM from issuing -Wzero-as-null-pointer-constant
      warnings.
      
      PiperOrigin-RevId: 215814400
      4bb49ed6
  3. 14 Aug, 2018 2 commits
  4. 05 Mar, 2018 1 commit
  5. 10 Aug, 2017 1 commit
  6. 25 Aug, 2015 1 commit
  7. 27 Jul, 2015 1 commit
  8. 15 Nov, 2012 1 commit
    • jgm's avatar
      Unfortunately, the svn repo is a bit out of date. This commit contains 8 · 38513a8b
      jgm authored
      changes that haven't made it to svn. The descriptions of each change are listed
      below.
      
      - Fixes some python shebang lines.
      
      - Add ElementsAreArray overloads to gmock. ElementsAreArray now makes a copy of
        its input elements before the conversion to a Matcher. ElementsAreArray can
        now take a vector as input. ElementsAreArray can now take an iterator pair as
        input.
      
      - Templatize MatchAndExplain to allow independent string types for the matcher
        and matchee. I also templatized the ConstCharPointer version of
        MatchAndExplain to avoid calls with "char*" from using the new templated
        MatchAndExplain.
      
      - Fixes the bug where the constructor of the return type of ElementsAre() saves
        a reference instead of a copy of the arguments.
      
      - Extends ElementsAre() to accept arrays whose sizes aren't known.
      
      - Switches gTest's internal FilePath class from testing::internal::String to
        std::string. testing::internal::String was introduced when gTest couldn't
        depend on std::string.  It's now deprecated.
      
      - Switches gTest & gMock from using testing::internal::String objects to
        std::string. Some static methods of String are still in use.  We may be able
        to remove some but not all of them.  In particular, String::Format() should
        eventually be removed as it truncates the result at 4096 characters, often
        causing problems.
      38513a8b
  9. 20 May, 2011 1 commit
  10. 14 Sep, 2010 1 commit
  11. 01 Sep, 2009 1 commit
  12. 29 Apr, 2009 1 commit
  13. 22 Apr, 2009 1 commit
  14. 19 Feb, 2009 1 commit
  15. 10 Dec, 2008 1 commit