| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|\
| |
| | |
Update Xcode project file
|
|/
|
|
|
| |
- Remove files which no longer exists
- Add newer file
|
|\
| |
| | |
Note about INSTANTIATE_TEST_SUITE_P / INSTANTIATE_TEST_CASE_P
|
| |
| |
| | |
Co-Authored-By: antismap <michael.thenault@gmail.com>
|
| |
| |
| | |
See https://github.com/google/googletest/issues/2065
|
|\ \
| | |
| | |
| | | |
PiperOrigin-RevId: 239404016
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Remove mention of unused type ProtocolMessage.
PiperOrigin-RevId: 239242706
|
| |/
|/|
| |
| |
| |
| | |
Action helpers need to pass by const& so that they can work with unique_ptr.
PiperOrigin-RevId: 239062671
|
|\ \
| |/
|/| |
DesignDoc Markdown table was broken
|
|/
|
| |
Added a missing newline
|
|\
| |
| |
| | |
PiperOrigin-RevId: 236716851
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Build gmock cleanly with clang -Wextra-semi and -Wextra-semi-stmt
Extends 56ef07a20308 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
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|/
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
Replace more pump'd code with variadic templates.
PiperOrigin-RevId: 235584585
|
|\
| |
| | |
Fix grammatical error in primer.md
|
|/ |
|
|\
| |
| |
| |
| |
| | |
ngie-eign:gtest-test-death-test-dont-hardcode-test-name
PiperOrigin-RevId: 235248114
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`CxxExceptionDeathTest.PrintsMessageForStdException`
Due to some caveats in the FreeBSD build system and the fact that the
source file is used to compile 2 different death tests with different
flags, I needed (as a shortterm workaround) to copy the test to 2
differently named files.
While this works for compiling the test, as I discovered, this doesn't
work with running `CxxExceptionDeathTest.PrintsMessageForStdException`,
as the testcase hardcodes `googletest-death-test_ex_test.cc`. Use `__FILE__`
when looking for failures, as opposed to looking for the hardcoded name
as it can vary depending on how the test was built.
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
|
|\ \
| |/
|/|
| | |
PiperOrigin-RevId: 235220570
|
| |
| |
| |
| | |
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
|
|\ \
| | |
| | |
| | | |
PiperOrigin-RevId: 235012245
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
clang++ compilation when `-Wsign-conversion` is currently broken and the
issues within the code are varied and widespread. For the time being
ignore `-Wsign-conversion` issues, even though some of them are valid
and bleed over into issues that would be found with
`-Wtautological-compare`, et al.
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
|
|\ \
| | |
| | |
| | | |
PiperOrigin-RevId: 234845565
|
| | |
| | |
| | |
| | | |
Signed-off-by: Pavel Samolysov <samolisov@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
While the google test library is being built as a shared library using Bazel,
so that there is a rule like
cc_test(
name = "iterator_traits_test",
linkstatic = 0,
deps = ["@gtest//:gtest_main"],
...
)
in a BUILD file, the following error appears on Windows:
INFO: Found 1 test target...
ERROR: C:/../external/gtest/BUILD.bazel:55:1: output 'external/gtest/gtest.if.lib' was not created
ERROR: C:/../external/gtest/BUILD.bazel:55:1: not all outputs were created or valid
Target //test:iterator_traits_test failed to build
The reason is a missing "win_def_file" attribute of the "gtest" and
"gtest_main" rules in the BUILD.bazel inside the google test library
package.
The "windows_export_all_symbols" feature is added to the rules, this
feature forces Bazel to export all symbols from the google test library
to linker. I believe exporting all symbols from a testing library makes
no problem for the application from a point of view on encapsulation.
Signed-off-by: Pavel Samolysov <samolisov@gmail.com>
|
|\ \ \
| | | |
| | | |
| | | | |
PiperOrigin-RevId: 234844287
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Comment out unused method parameters in their relevant definitions.
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
`DescribeTo(..)` and `MatchAndExplain(..)` in `gmock-matchers_test` both
override virtual methods. Remove the `virtual` keyword and apply `override` to
them instead.
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
|
|\ \ \
| | | |
| | | |
| | | | |
PiperOrigin-RevId: 234840107
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`DescribeTo(..)` and `MatchAndExplain(..)` in `gmock-matchers_test` both
override virtual methods. Remove the `virtual` keyword and apply `override` to
them instead.
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Internal Change
PiperOrigin-RevId: 234823465
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Update gtest-death-test to use new Fuchsia API
Fuchsia has renamed this API and removed the need for several parameters. We now use the newer, simpler API.
PiperOrigin-RevId: 234617715
|
|\ \ \
| |/ /
|/| | |
Avoid array index out of range
|
|/ /
| |
| |
| | |
Issue: #2140
|
|\ \
| | |
| | |
| | | |
PiperOrigin-RevId: 233825166
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the object was never created then trying to call &Test::DeleteSelf_
will dereference a null pointer, with undefined behaviour.
Fixes #845
|
|\ \ \
| | | |
| | | |
| | | | |
PiperOrigin-RevId: 233789488
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As noted in the patch description:
* Add DragonFly and GNU/kFreeBSD support.
* Implement GetThreadCount() for BSDs.
1. https://svnweb.freebsd.org/ports/head/devel/googletest/files/patch-bsd-defines?revision=488934
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
PiperOrigin-RevId: 233773676
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When building and using googletest from an install tree
we want libtool to generate rpath in the dependent binaries
to allow them to be executed from a build without a need
for LD_LIBRARY_PATH or similar.
For libtool based project this happens automatically
as projects generates .la files and install them.
Provide such a file for gtest as well to allow it to
work smoothly with libtool based projects.
Signed-off-by: Knut Omang <knut.omang@oracle.com>
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
PiperOrigin-RevId: 233762751
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
Provide dummy accessors for private values that are set in initializers,
but not actually used.
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
PiperOrigin-RevId: 233762520
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
It was not compiling any of the code with warnings prior to this.
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
|