| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Address `-Wpedantic` issue introduced in https://github.com/google/googletest/pull/3204
Raised via https://github.com/google/googletest/commit/4898cdacfec11e71fa3083cdbc935852ad8162e9#commitcomment-46413996
PiperOrigin-RevId: 354198931
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Document the fact that MatchAndExplain(T, MatchResultListener*) is supported.
PiperOrigin-RevId: 354172275
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Remove uses of GTEST_HAS_TYPED_TEST_P and GTEST_HAS_TYPED_TEST.
PiperOrigin-RevId: 353935996
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Add missing `is_gtest_matcher` to the polymorphic matcher example.
PiperOrigin-RevId: 353881883
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Delete internal tags from docs
PiperOrigin-RevId: 353769887
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Delete obsolete comment, gtest-param-test.h isn't generated by pump anymore
PiperOrigin-RevId: 353680589
|
| |\ \ \
| | | |
| | | |
| | | | |
PiperOrigin-RevId: 353327372
|
| | | | |
| | | |
| | | |
| | | | |
Markdown file was moved to a different directory. When googling for
"gtest primer", the result is 404 page.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Updates the gMock cheat sheet to include the versions of the Field and Property matchers which take an additional name parameter.
PiperOrigin-RevId: 353273968
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
| `IsEmpty()` | `argument` is an empty string. |
PiperOrigin-RevId: 352880252
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove scripts for code generating together with related files.
PiperOrigin-RevId: 352805926
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Stop using pump for generating internal/custom/gmock-generated-actions.h
PiperOrigin-RevId: 352660735
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
PiperOrigin-RevId: 352626267
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Affects macros {ASSERT|EXPECT}_{EQ|NE|LE|LT|GE|GT}.
According to removed comments, these overloads were supposed to reduce
code bloat and allow anonymous enums on GCC 4.
However, the way it works on GCC 4 and the latest GCC (10.2 by now) is
that having:
template <typename T1, typename T2>
void foo(T1, T2);
using BiggestInt = long long;
void foo(BiggestInt, BiggestInt);
the template version takes precedence for almost every combination of
integral types except for two long long integers - i.e. implicit
promotion to long long is a worse match than generating a specific
template function.
Tested on GCC 4.8.1 (as GoogleTest requires C++11 and this was
the first C++11 feature-complete release of GCC),
GCC 4.8.5 (last of 4.8.x series) and the latest GCC (10.2.0).
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Internal change
PiperOrigin-RevId: 352607401
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove obsolete argument limit documentation.
Combine uses variadic templates now, so there is no inherent limit on the number of arguments.
PiperOrigin-RevId: 352580160
|
| | |/ /
|/| |
| | |
| | |
| | |
| | | |
Merge CONTRIBUTORS, delete LICENSEs in googletest/ and googlemock/
PiperOrigin-RevId: 352558822
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Fixes #3222, fixes #3225, closes #3223
PiperOrigin-RevId: 352066131
|
| |\ \ \
| | | |
| | | |
| | | | |
PiperOrigin-RevId: 352044381
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Internal change
PiperOrigin-RevId: 352002166
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Internal change
PiperOrigin-RevId: 351864506
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
PiperOrigin-RevId: 351812507
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes build issues with GoogleTest when built with
-Wformat-nonliteral and unblocks updating GoogleTest in BoringSSL.
It was added in 53c478d639b8eebd2942e88266610ebc79c541f6, which caught
some bugs. Then it was moved to the header and accidentally dropped in
482ac6ee63429af2aa9c44f4e6427873fb68fb1f.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add "using is_gtest_matcher = void" to the DivisibleBy7Matcher example.
PiperOrigin-RevId: 351797821
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove platformio tests. This currently uses gcc 4.8.2 which is no
longer supported.
PiperOrigin-RevId: 351667999
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix build under GCC 5
PiperOrigin-RevId: 351607537
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Print unique_ptr/shared_ptr recursively.
Given that they are smart pointers, it is unlikely that the inner object is
invalid.
PiperOrigin-RevId: 351586888
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Launder buffer before reference
In GCC, directly casting the Buffer reference to another type results in
strict-aliasing violation errors. This launders the reference using an
intermediate pointer prior to creating the new reference.
PiperOrigin-RevId: 350809323
|
| | |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Change Matcher<T> to allow binding an implementation by value directly:
- Drop the requirement of MatcherInterface. Doing manual type erasure avoid
extra layers in many cases.
- Avoid the adaptor for `MatcherInterface<T>` and `MatcherInterface<const T&>` mismatch.
- Use a small object optimization when possible. This makes things like
`_` and `Eq(1)` really cheap and do not require memory allocations.
- Migrate some matchers to the new model to speed them up and to test the new framework. More matchers to come in future changes.
PiperOrigin-RevId: 350580998
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Move all docs into top-level docs/ directory
PiperOrigin-RevId: 350211277
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Fix Objective-C++ compatibility
PiperOrigin-RevId: 350192165
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Add support for printing incomplete types in the universal printer.
PiperOrigin-RevId: 350154637
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use an OrderedDict to store templated_types in the AST so that gmock knows how to properly construct the templated Mock class.
This is necessary for functions that make use of the templated typename as an argument or return type.
PiperOrigin-RevId: 349405731
|
| |\ \ \
| |/ /
|/| |
| | | |
PiperOrigin-RevId: 349349288
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | | |
PiperOrigin-RevId: 349296827
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Give each of Naggy/Nice/StrictMock a base class whose constructor runs before
the mocked class's constructor, and a destructor that runs after the mocked
class's destructor, so that any mock methods run in either the constructor or
destructor use the same strictness as other calls.
PiperOrigin-RevId: 348511612
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Internal Change
PiperOrigin-RevId: 347631521
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add static_asserts that verify that no class hierarchy contains more than one
of {NiceMock, NaggyMock, StrictMock}. This sort of nesting has always been
disallowed, but this CL adds a compile-time check to prevent it.
PiperOrigin-RevId: 347037822
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Remove ZX_WAIT_ASYNC_ONCE flag
It is deprecated and will soon be removed in fuchsia source.
It's currently defined as 0 and references should be changed to 0.
PiperOrigin-RevId: 346787585
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Fix a missing Bazel build dependency
PiperOrigin-RevId: 346783462
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Introduce a new `Address` matcher to gmock.
PiperOrigin-RevId: 346344591
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Fix errata in gmock cook_book.md ON_CALL example
PiperOrigin-RevId: 346165890
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add a `Pointer` matcher as an analog to `Pointee`.
Similar to `Pointee`, `Pointer` works with either raw or smart pointers and
allows creating a matcher like Pointer(Eq(foo)) for smart pointers.
PiperOrigin-RevId: 346164768
|
| |\ \ \
| | | |
| | | |
| | | | |
PiperOrigin-RevId: 346160291
|
| | | |/
| |/| |
|
| |/ /
| |
| |
| |
| |
| | |
Update README to clarify supported platforms
PiperOrigin-RevId: 346140983
|
| | |
| |
| |
| |
| |
| | |
Disable a gmock matcher test under MSVC 2015 (version 14) and earlier. It interacts badly with Windows structured exceptions in a way we do not have the resources to investigate. This test passes under MSVC 2017 and SEH.
PiperOrigin-RevId: 345496734
|
