| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
for including documentation in sync process
|
| |
|
|
|
|
|
|
| |
gmock_output_test has to run under python2. Bazel 0.27.0 causes this test to break. Fixing it.
PiperOrigin-RevId: 253820111
|
|
|
|
|
|
| |
Project import generated by Copybara.
PiperOrigin-RevId: 253600369
|
|
|
|
|
|
| |
Internal Change
PiperOrigin-RevId: 253581166
|
|\
| |
| | |
Removing make and automake.
|
| |\ |
|
| | | |
|
| | |
| | |
| | |
| | | |
internally and CMake community supported
|
| |/
|/| |
|
| |
| |
| |
| | |
removal to make sure that people who are interested will notice
|
|/ |
|
|
|
|
| |
build methods
|
|
|
|
| |
build methods
|
|
|
|
| |
methods
|
|\
| |
| | |
fix typo
|
| | |
|
|/ |
|
|
|
|
| |
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
|
|
|
|
|
|
| |
Remove special case for protocol buffers. It is no longer needed.
PiperOrigin-RevId: 246550795
|
|
|
|
|
|
| |
Clarify build system support - CMake and automake community supported
PiperOrigin-RevId: 245821927
|
|
|
|
|
|
|
|
|
| |
Remove GMock Doctor.
It has not been actively supported for a while.
We also now have better techniques to improve compiler errors where needed
instead of requiring a separate tool to diagnose them.
PiperOrigin-RevId: 244196068
|
|
|
|
|
|
| |
Expose more information in SuiteApiResolver diagnostic output
PiperOrigin-RevId: 244179347
|
|\
| |
| |
| | |
PiperOrigin-RevId: 244069956
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Cast some values as their unsigned equivalents or `size_t` to match the
parameter type used for the template object under test. Also, provide
UInt32 equivalent delegate methods for some callers (with
int-equivalents for backwards compatibility).
This closes #2146.
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Per the MSVC documentation the warning is new as of Visual Studio 2017,
version 15.8.
https://docs.microsoft.com/en-us/cpp/error-messages/compiler-warnings/c5046?view=vs-2019
GTest users building on MSVC 2015 or older versions of 2017 will, when
C4616 is enabled, see a warning like:
[...]gtest-matchers.h(53): error C2220: warning treated as error - no 'object' file generated
[...]gtest-matchers.h(53): warning C4619: #pragma warning: there is no warning number '5046'
Guard the mention of 5046 by an _MSC_VER check. VS2017 15.8 corresponds
to an _MSC_VER of 1915.
https://docs.microsoft.com/en-us/cpp/preprocessor/predefined-macros?view=vs-2019
|
|/ |
|
|\
| |
| |
| |
| |
| | |
ngie-eign:cmake-fix-gtest-binary-prefixing-when-gmock-enabled
PiperOrigin-RevId: 241376090
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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: Enji Cooper <yaneurabeya@gmail.com>
|
|/
|
|
|
|
|
|
| |
Remove support for "global" ::string and ::wstring types.
This support existed for legacy codebases that existed from before namespaces
where a thing. It is no longer necessary.
PiperOrigin-RevId: 241335738
|
|\
| |
| |
| | |
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
|
|/
|
| |
Added a missing newline
|
|\
| |
| |
| | |
PiperOrigin-RevId: 236716851
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|/
|
|
|
|
|
|
|
|
| |
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
|
|\
| |
| |
| | |
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
|
|
|
|
|
|
|
| |
Provide dummy accessors for private values that are set in initializers,
but not actually used.
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
|
|
|
|
|
|
| |
Internal Change
PiperOrigin-RevId: 233614147
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
Internal change
PiperOrigin-RevId: 232362580
|
|
|
|
|
|
| |
Mark legacy _TEST_CASE_ macros as deprecated
PiperOrigin-RevId: 232303251
|
|
|
|
|
|
| |
Fix stack overflow in AnyOfArray tests.
PiperOrigin-RevId: 231881125
|