| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| | |
Fix include guards in gen_pred_test.py
PiperOrigin-RevId: 386052814
|
|\ \
| | |
| | |
| | | |
PiperOrigin-RevId: 385627491
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The documentation is clear that the FOO we'll be guarding always matches
the spelling of the DONT macro. A single guard macro should not toggle
more than one implementation macro.
This fixes a regression in 7413280c52c1f759395572a384165023d24eeb57.
Relatedly, improve the documentation of the DONT macros to bring the
list of valid FOO values up to date.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Run buildifier on WORKSPACE
Fixes #3483
PiperOrigin-RevId: 385610473
|
|\ \ \
| | | |
| | | |
| | | | |
PiperOrigin-RevId: 384913062
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
According to the 2nd point on [1], -lregex is required on QNX.
[1] https://www.qnx.com/developers/docs/7.1/#com.qnx.doc.ide.userguide/topic/writing_test_programs.html
|
| | |
| | |
| | |
| | |
| | |
| | | |
Remove unneeded using ::std::get;
PiperOrigin-RevId: 383688097
|
| | |
| | |
| | |
| | |
| | |
| | | |
Suppress a clang-tidy warning in the MATCHER(name, description) macro.
PiperOrigin-RevId: 383587271
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add `Conditional` wrapper to gtest
This follows an initial proposal for an 'EqIff` matcher. `Conditional` was considered more precise as an EqIff() matcher may suffer from `Iff` not being universally understood.
PiperOrigin-RevId: 383407665
|
| | |
| | |
| | |
| | |
| | |
| | | |
Introduce GTEST_FLAG_GET and GTEST_FLAG_SET macros.
PiperOrigin-RevId: 382808313
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
gtest: Add a flag to only set up/tear down test environments once when repeating
Currently when running a test multiple times using `--gtest_repeat` the global
test environment(s) are set up and torn down for each iteration of the test.
When checking for flakes in tests that have expensive dependencies that are set
up in the test environment (subprocesses, external dependencies, etc) this can
become expensive.
To support finding flakes in tests that fit into this category, where the setup
phase is expensive but each test case is fast, allow callers to specify via
`--gtest_recreate_environments_when_repeating=false` that the test environments
should only be set up once, for the first iteration, and only torn down once, on
the last iteration. This makes running a test with `--gtest_repeat=1000` a much
faster and more pleasant experience.
PiperOrigin-RevId: 382748942
|
| |
| |
| |
| |
| |
| | |
Implement 'Contains(e).Times(n)' matcher modifier which allows to test for arbitrary occurrences including absence with Times(0).
PiperOrigin-RevId: 382210276
|
|\ \
| | |
| | |
| | | |
PiperOrigin-RevId: 382189077
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On QNX, pthread is part of libc [1]. There's no separate pthread library
to link.
[1] https://www.qnx.com/developers/docs/7.1/index.html#com.qnx.doc.neutrino.lib_ref/topic/p/pthread_create.html
|
|\ \ \
| | | |
| | | |
| | | | |
PiperOrigin-RevId: 382188112
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
EXPECT_DEATH() and ASSERT_DEATH() have a switch case where every
possible case is covered. This makes the default case unnecessary
and triggers -Wcovered-switch-default.
Due to these being macros, the lines are expanded in user code and
are thus subject to warnings of the target codebase.
Fixes #3456
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Make multiple attempts to verify GetThreadCount()
Testing GetThreadCount() is inheritently noisy, as other threads can be started
or destroyed between two calls to GetThreadCount(). This is especially true
under certain analyzer configurations, such as TSAN.
PiperOrigin-RevId: 381951799
|
|/ /
| |
| |
| |
| |
| | |
Deleting deprecated file.
PiperOrigin-RevId: 381938709
|
|\ \
| | |
| | |
| | | |
PiperOrigin-RevId: 380705469
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Remove -Werror from the CMake compiler flags
We should not force warnings as errors on users.
Sometimes compilers introduce new warnings which
will break builds.
Instead, we manually turn this flag on in our continuous integration
scripts so we can catch these errors, but not force them on our users.
Fixes #3447
PiperOrigin-RevId: 380241852
|
|\ \ \
| | | |
| | | |
| | | | |
PiperOrigin-RevId: 379625931
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
PiperOrigin-RevId: 379383941
|
| | | | | |
|
|\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | | |
PiperOrigin-RevId: 378915968
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Reference is here: https://en.cppreference.com/w/cpp/feature_test
This PR fixes the weird case of compiling with `clang++ -std=c++17 -fchar8_t`
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Release GoogleTest 1.11.0
PiperOrigin-RevId: 378861756
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Internal change
PiperOrigin-RevId: 378672633
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add feature request issue template
PiperOrigin-RevId: 378552571
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Delete Travis config file
PiperOrigin-RevId: 378483262
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
cleanup: fix spurious MSAN warnings with Clang 12
PiperOrigin-RevId: 378430614
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add CNAME file for custom domain
PiperOrigin-RevId: 378384525
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Update broken link
PiperOrigin-RevId: 378272186
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add CNAME file for custom domain
PiperOrigin-RevId: 377604116
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
PiperOrigin-RevId: 377367006
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This was causing the following linker error on Microsoft Visual C++ when compiling as a DLL:
```
googletest-param-test-test.cc.obj : error LNK2019: unresolved external symbol "public: __cdecl testing::internal::MarkAsIgnored::MarkAsIgnored(char const *)" (??0MarkAsIgnored@internal@testing@@QEAA@PEBD@Z) referenced in function "void __cdecl works_here::`dynamic initializer for 'gtest_allow_ignore_NotInstantiatedTest''(void)" (??__Egtest_allow_ignore_NotInstantiatedTest@works_here@@YAXXZ)
```
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
exports
This was causing the following linker error on Microsoft Visual C++ when compiling as a DLL:
```
googletest-printers-test.cc.obj : error LNK2019: unresolved external symbol "void __cdecl testing::internal::PrintTo(char16_t const *,class std::basic_ostream<char,struct std::char_traits<char> > *)" (?PrintTo@internal@testing@@YAXPEB_SPEAV?$basic_ostream@DU?$char_traits@D@std@@@std@@@Z) referenced in function "public: static void __cdecl testing::internal::UniversalPrinter<char16_t const *>::Print(char16_t const * const &,class std::basic_ostream<char,struct std::char_traits<char> > *)" (?Print@?$UniversalPrinter@PEB_S@internal@testing@@SAXAEBQEB_SPEAV?$basic_ostream@DU?$char_traits@D@std@@@std@@@Z)
googletest-printers-test.cc.obj : error LNK2019: unresolved external symbol "void __cdecl testing::internal::PrintTo(char32_t const *,class std::basic_ostream<char,struct std::char_traits<char> > *)" (?PrintTo@internal@testing@@YAXPEB_UPEAV?$basic_ostream@DU?$char_traits@D@std@@@std@@@Z) referenced in function "public: static void __cdecl testing::internal::UniversalPrinter<char32_t const *>::Print(char32_t const * const &,class std::basic_ostream<char,struct std::char_traits<char> > *)" (?Print@?$UniversalPrinter@PEB_U@internal@testing@@SAXAEBQEB_UPEAV?$basic_ostream@DU?$char_traits@D@std@@@std@@@Z)
```
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fix MSVC warning C4275: non dll-interface class
'testing::MatcherDescriberInterface' used as base for dll-interface
class 'testing::internal::MatcherBase<std::string>'
Fixes #3415
PiperOrigin-RevId: 377352684
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | | |
PiperOrigin-RevId: 377289133
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
I spotted this in https://github.com/assimp/assimp/pull/3880/commits/7dd7a053a91322fad88cdf958c6d0b3b7b91cb90 and figured I'd fix it here, too.
If this is not the right thing to do, please lmk so I can undo it in assimp, too. Seems right, though. It's the only spot in gtest where a ctype call was made directly.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Create new Testing API reference
PiperOrigin-RevId: 376969148
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Create new Mocking Reference
PiperOrigin-RevId: 376951575
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fix broken link
PiperOrigin-RevId: 375995669
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Create Assertions Reference
PiperOrigin-RevId: 375824718
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Updates Linux docker image to use Bazel 4.1.0 and GCC 11.1
Updates Bazel dependencies
Removes the last usage of the deprecated and removed Python2
PiperOrigin-RevId: 375759184
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add Google Analytics & footer
PiperOrigin-RevId: 375539689
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Remove the dependency on Objective C++ in iOS builds.
252ce9c52d304659eff6be558209c811b7191963 introduced the use of
NSTemporaryDirectory() on iOS, which requires Core Foundation, and
Objective C++.
This CL replaces NSTemporaryDirectory() with an equivalent solution
(according to Apple's documentation at [1]) available to C/C++ code.
Avoiding Objective C++ and Core Foundation makes it easier to integrate
googletest in projects that can't use the supplied Bazel build files.
[1] https://developer.apple.com/library/archive/documentation/Security/Conceptual/SecureCodingGuide/Articles/RaceConditions.html#//apple_ref/doc/uid/TP40002585-SW10
PiperOrigin-RevId: 375474990
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add missing link
PiperOrigin-RevId: 374774097
|