Skip to content

G
googletest
Switch branch/tag
  1. 29 Mar, 2019 1 commit
    • Prefix googletest binaries under its own subtree instead of `gtest` · 9b6de41b
      Enji Cooper authored 
      Building all test binaries under their respective subtrees makes
building the project via cmake easier to grok without additional hacks.
In particular, when dealing with the conversion I proposed in
https://reviews.freebsd.org/D19430 (switching from autotools to cmake),
I ran into unexpected gtest prefixing under the googlemock directory, as
opposed to the googletest directory. Example:

Before: `googlemock/gtest/googletest-break-on-failure-unittest_`
After:  `googletest/googletest-break-on-failure-unittest_`

The latter form is easier to translate to packaging manifests when
building googlemock is disabled, as well as enabled, as the path remains
consistent when the feature flag is disabled.
Signed-off-by: 's avatarEnji Cooper <yaneurabeya@gmail.com>
  3. 28 Mar, 2019 3 commits
  5. 26 Mar, 2019 2 commits
  7. 21 Mar, 2019 6 commits
  9. 20 Mar, 2019 1 commit
  11. 19 Mar, 2019 1 commit
  13. 15 Mar, 2019 1 commit
  15. 05 Mar, 2019 3 commits
    • Merge pull request #2158 from CarloWood:master · 8b6d3f9c
      Gennadiy Civil authored 
      PiperOrigin-RevId: 236716851
    • Googletest export · 3dd2e841
      Abseil Team authored 
      Fix emission of -Wzero-as-null-pointer-constant when comparing integers.

The following code fails to compile:

#pragma clang diagnostic error "-Wzero-as-null-pointer-constant"
void foo() {
  EXPECT_EQ(0, 0);
}

This happens because gtest checks the first argument to EXPECT_EQ and
ASSERT_EQ is a null pointer constant. The magic it does to do this causes the
warning to be emitted.

This patch removes that check. It replaces the explicit check with a Compare
overload that can only be selected when 0 or nullptr is passed on the LHS
with a pointer on the right.

This patch does not suppress -Wzero-as-null-pointer-constant when users
are actually using it as NULL.

PiperOrigin-RevId: 236654634
    • Googletest export · a1dd0778
      Abseil Team authored 
      Build gmock cleanly with clang -Wextra-semi and -Wextra-semi-stmt

Extends 56ef07a2 to take -Wc++98-compat-extra-semi
(https://reviews.llvm.org/D43162) and -Wextra-semi-stmt
(https://reviews.llvm.org/D52695) into account.

For https://crbug.com/926235.

PiperOrigin-RevId: 236643095
  17. 01 Mar, 2019 3 commits
    • Googletest export · db9b85e2
      Abseil Team authored 
      Let embedders customize GTEST_INTERNAL_DEPRECATED().

GTEST_INTERNAL_DEPRECATED is currently used to nudge googletest users to migrate off old TEST_CASE macros to the new TEST_SUITE macros. This move is non-trivial for Chromium (see https://crbug.com/925652), and might be difficult for other big projects with many dependencies.

This CL facilitates moving off of deprecated APIs by making it possible for an embedder to define GTEST_INTERNAL_DEPRECATED() in gtest/internal/custom/gtest-port.h. Example usage:

1) #define GTEST_INTERNAL_DEPRECATED() to nothing, to disable deprecation warnings while migrating off googletest's deprecated APIs. This can be preferable to having to disable all deprecation warnings (-Wno-error=deprecated or -Wno-deprecated-declarations).

2) #define GTEST_INTERNAL_DEPRECATED() for an unsupported compiler.

PiperOrigin-RevId: 236171043
    • Googletest export · 56ef07a2
      Abseil Team authored 
      Build gmock cleanly with clang -Wextra-semi

For https://crbug.com/926235.
From https://github.com/google/googletest/pull/2139.
Fixes https://github.com/google/googletest/issues/2138.

PiperOrigin-RevId: 235832527
    • Minor build system fixes. · fc979623
      Carlo Wood authored
  19. 25 Feb, 2019 3 commits
  21. 22 Feb, 2019 2 commits
  23. 21 Feb, 2019 2 commits
  25. 20 Feb, 2019 6 commits
  27. 19 Feb, 2019 2 commits
  29. 13 Feb, 2019 4 commits