summaryrefslogtreecommitdiffstats
path: root/googletest/include/gtest
Commit message (Collapse)AuthorAgeFilesLines
...
| * Revert "Googletest export": disallow empty prefixShahbaz Youssefi2019-12-161-15/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 20b5b8ecc7a81d23b4716e22a2b35fd53379c8c6. Reason for revert: Breaks existing applications, such as ANGLE (angleproject.org), requires adding an extra prefix that needs to be typed for no reason (when testing from command line) and increases the logs' sizes by a non-trivial amount due to the very large number of tests ANGLE runs. Original commit message: Add a compile time check to ensure that the parameters to TEST_P and INSTANTIATE_TEST_SUITE_P are not empty. Some compilers already fail in that case and, even where it works, it's likely to result in technically invalid code by virtue of creating reserved identifiers: https://en.cppreference.com/w/cpp/language/identifiers First, every project is perfectly capable of adding a prefix if they want to support such a compiler. This change penalizes every project. Second, using a prefix such as `_p` also results in reserved identifiers, so this change is not really solving the problem. For that matter, instead of generating `gtest_##prefix##...`, you can generate `gtest_x##prefix##...` to correctly fix the issue, including when empty prefixes are used.
| * Revert "Googletest export": Remove test for empty prefixShahbaz Youssefi2019-12-161-1/+4
| | | | | | | | | | | | | | | | | | | | This reverts commit 4c25e2b87fcb78abcfdee2739db9ed7a19754cd3. Reason for revert: Reverting the commit that disallows empty prefixes. Original commit message: Remove a test case rendered obsolete by disallowing empty argument for INSTANTIATE_TEST_SUITE_P. Remove the code that it was testing.
| * Workaround VS bug w.r.t empty arguments to macrosShahbaz Youssefi2019-12-161-1/+10
|/ | | | | | | | | | | | | | | | Empty arguments can be passed to macros per C99 and C++11 specs, which can then be forwarded to other macros. Visual Studio's compiler has a bug in the following situation: #define A(x) #x #define B(x, y) A(x) B(, b) In the above case, Visual Studio first expands x to nothing, then complains that A is not invoked with the right amount of arguments. However, x in A(x) is still one argument, even if it expands to no preprocessing tokens. See also https://stackoverflow.com/a/7674214.
* Googletest exportAbseil Team2019-12-131-1/+2
| | | | | | Add GTEST_API_ to correct a build failure under MSCV. PiperOrigin-RevId: 285208464
* Googletest exportAbseil Team2019-12-131-1/+14
| | | | | | | | | | | Detect when C++ parametric tests (TEST_P) are not instantiated. When an un-instantiated TEST_P is found, a new test will be inserted that will emit a warning message. This can be made to error with minor code edits. In the future, that is intended to be the default. PiperOrigin-RevId: 284901666
* Googletest exportAbseil Team2019-12-061-5/+3
| | | | | | | | | | Change googletest to notice failures during SetUpTestSuite() and TearDownTestSuite(). Previously, errors that occurred during those functions were logged but otherwise ignored. After this change, such failures will cause the test to fail and a brief summary will be printed at the bottom of the test log. See https://github.com/google/googletest/issues/2330. PiperOrigin-RevId: 284033342
* Googletest exportAbseil Team2019-11-261-1/+1
| | | | | | | | Wrap call to std::numeric_limits<>::max into round braces to appease MSVC. Closes #2589 PiperOrigin-RevId: 282581361
* Merge pull request #2591 from kuzkry:remove-workaround_g++-using-on-operator<<Gennadiy Rozental2019-11-261-4/+2
|\ | | | | | | PiperOrigin-RevId: 282575040
| * remove g++ 3.3 workaround: using on operator<<Krystian Kuzniarek2019-11-221-4/+2
| |
* | Googletest exportAbseil Team2019-11-223-44/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | Use standard C++11 integer types in gtest-port.h. Remove testing::internal::{Int,Uint}{32,64} in favor of types guaranteed to be in <cstdint> since C++11. Tests for built-in integer type coverage are switched from {Int,Uint}64 to [unsigned] long long, which is guaranteed by C++11 to exist and be at least 64-bit wide. PiperOrigin-RevId: 281565263
* | Merge pull request #2569 from bgianfo:masterGennadiy Civil2019-11-201-2/+3
|\ \ | | | | | | | | | PiperOrigin-RevId: 281321427
| * | Fix FlatTuple compilation on older msvc.Brian Gianforcaro2019-11-151-2/+4
|/ / | | | | | | | | | | | | | | | | | | | | | | googletest 1.10.0 fails to compile on msvc version 19.00.23917 with one compilation error: src\googletest\include\gtest\internal\gtest-internal.h(1188) : error C2039: 'FlatTupleBase<testing::internal::FlatTuple<bool,bool>,testing::internal::IndexSequence<0,1> >': is not a member of 'testing::internal::FlatTuple<bool,bool>' This PR fixes the compilation error by explicitly specifying the full type that Indices is located in the base type.
* | Googletest exportAbseil Team2019-11-081-4/+13
| | | | | | | | | | | | | | | | Correctly deal with stringification, and forbid empty arguments where they could slip thought, in the type parameterized test API. Note: even where empty args work, it's likely to result in technically invalid code by virtue of creating reserved identifiers: https://en.cppreference.com/w/cpp/language/identifiers PiperOrigin-RevId: 279330971
* | Merge pull request #2373 from Youw:masterXiaoyi Zhang2019-11-051-3/+33
|\ \ | |/ |/| | | PiperOrigin-RevId: 278601074
| * Added special catch for std::exception in GTEST_TEST_NO_THROW_Ihor Dutchak2019-10-301-3/+31
| |
* | Merge pull request #2453 from kuzkry:gtest-port-clean-up_kMaxBiggestIntXiaoyi Zhang2019-11-043-39/+58
|\ \ | | | | | | | | | PiperOrigin-RevId: 278008286
* | | Merge pull request #2453 from kuzkry:gtest-port-clean-up_kMaxBiggestIntvslashg2019-11-013-58/+39
|\| | | | | | | | | | | PiperOrigin-RevId: 277979766
| * | remove BiggestIntKrystian Kuzniarek2019-10-243-36/+19
| | |
* | | Merge pull request #2388 from kuzkry:remove-gtest-type-util.pumpvslashg2019-10-294-3515/+59
|\ \ \ | | | | | | | | | | | | PiperOrigin-RevId: 276944601
| * | | remove gtest-type-util.h.pumpKrystian Kuzniarek2019-10-252-192/+1
| | | |
| * | | replace autogenerated TemplatesX classes by variadic onesKrystian Kuzniarek2019-10-254-1743/+28
| | | |
| * | | replace autogenerated TypesX classes by variadic onesKrystian Kuzniarek2019-10-254-1647/+97
| | | |
* | | | Merge pull request #2515 from ciband:feat/support_esp8266vslashg2019-10-252-4/+26
|\ \ \ \ | |/ / / |/| | | | | | | PiperOrigin-RevId: 276333426
| * | | feat: Add ESP8266 supportChris2019-10-132-3/+23
| |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Added support for ESP8266 * Removed previous Arduino defines in favor of GTEST_OS_* syntax * Improved PlatformIO library file to be more stable when consumed in client applications.
| | * | | Update to distinguish prelease purpose of this fork.Chris Johnson2019-10-111-5/+5
| | | | |
| | * | | Add ESP8266 configs to PlatformIO buildChris Johnson2019-10-111-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | | Added various conditional compliations for ESP8266 to stub out missing functionality.
| | * | | feat: Add support for ESP8266 platformChris Johnson2019-10-111-0/+4
| |/ / / | | | | | | | | | | | | | | | | | | | | Added support for ESP8266 Arduino platform. Refactored Arduino defines to use the GTEST_OS_* model.
* | | | Merge pull request #2517 from snarkmaster:masterGennadiy Civil2019-10-221-1/+1
|\ \ \ \ | | | | | | | | | | | | | | | PiperOrigin-RevId: 275869169
| * | | | [googletest] Output skip messageAlexey Spiridonov2019-10-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Closes #2208 Previously, skip messages were invisible, so debugging skips was hard. Now we have this: ``` $ ./googletest/gtest_skip_test Running main() from /home/lesha/github/snarkmaster/googletest/googletest/src/gtest_main.cc [==========] Running 3 tests from 2 test suites. [----------] Global test environment set-up. [----------] 1 test from SkipTest [ RUN ] SkipTest.DoesSkip /home/lesha/github/snarkmaster/googletest/googletest/test/gtest_skip_test.cc:38: Skipped skipping single test [ SKIPPED ] SkipTest.DoesSkip (0 ms) [----------] 1 test from SkipTest (1 ms total) ... ```
* | | | | Merge pull request #2444 from kuzkry:remove-GTEST_ARRAY_SIZE_Gennadiy Civil2019-10-221-3/+0
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | PiperOrigin-RevId: 275842505
| * | | | | remove GTEST_ARRAY_SIZE_Krystian Kuzniarek2019-09-231-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This macro didn't work when an array was passed to a function by pointer, in which case the information about its size was lost. Better alternatives are: * std::extent<T>::value (compile-time) * std::array<T, N>::size() (compile-time) * std::distance(std::begin(array), std::end(array)) (run-time)
* | | | | | Googletest exportAbseil Team2019-10-222-5/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove bool_constant in favor of std::integral_constant<bool, ...>; The one non-trivial use of bool_constant has been changed to have significantly fewer template specializations. PiperOrigin-RevId: 275842490
* | | | | | Merge pull request #2454 from kuzkry:gtest-port-clean-up_dead-functionGennadiy Civil2019-10-222-11/+5
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | PiperOrigin-RevId: 275838743
| * | | | | | change includes in gtest-port.hKrystian Kuzniarek2019-09-112-4/+2
| | | | | | |
| * | | | | | remove a dead functionKrystian Kuzniarek2019-09-101-4/+0
| | |_|_|/ / | |/| | | |
* | | | | | Merge pull request #2507 from roblub:masterGennadiy Civil2019-10-172-4/+4
|\ \ \ \ \ \ | |_|_|/ / / |/| | | | | | | | | | | PiperOrigin-RevId: 275076905
| * | | | | Add more override keywordsRobert Luberda2019-10-112-4/+4
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Mark more functions with "override" keyword, just like it was done in commit 2460f97152c. This should prevent compiler from complaining while compiling both user code, and the googletest code itself with the -Wsuggest-override option turned on; with the exception of: * calls to new MOCK_METHOD() in test/gmock-function-mocker_test.cc * calls to old MOCK_METHODx()/MOCK_CONST_METHODx() in other unit test files. Closes #2493
* / | | | Googletest exportAbseil Team2019-10-161-4/+1
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | Remove a test case rendered obsolete by disallowing empty argument for INSTANTIATE_TEST_SUITE_P. Remove the code that it was testing. PiperOrigin-RevId: 275040108
* | | | Merge pull request #2456 from kuzkry:gtest-port-clean-up_breaking-changesGennadiy Civil2019-10-111-9/+0
|\ \ \ \ | | | | | | | | | | | | | | | PiperOrigin-RevId: 274100752
| * | | | remove GTEST_HAS_STD_STRINGKrystian Kuzniarek2019-09-101-9/+0
| |/ / /
* | | | Googletest exportAbseil Team2019-10-111-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Fix a bug in dealing with paramaterized tests where the name is it self a macro expansion. - Add a compile time check to ensure that the parameters to TEST_P and INSTANTIATE_TEST_SUITE_P are not empty. The above fix causes some compilers to fail in that case and even where it works, it's likely to result in technically invalid code by virtue of creating reserved identifiers: https://en.cppreference.com/w/cpp/language/identifiers PiperOrigin-RevId: 274047249
* | | | Googletest exportAbseil Team2019-10-111-21/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix the O(n^2) number of instantiations in ElemFromList. It is now O(n). It still has O(1) instantiation depth. PiperOrigin-RevId: 273980821
* | | | Googletest exportAbseil Team2019-10-101-5/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a compile time check to ensure that the parameters to TEST_P and INSTANTIATE_TEST_SUITE_P are not empty. Some compilers already fail in that case and, even where it works, it's likely to result in technically invalid code by virtue of creating reserved identifiers: https://en.cppreference.com/w/cpp/language/identifiers PiperOrigin-RevId: 273832263
* | | | Merge pull request #2448 from kuzkry:bad-googletest-exportGennadiy Civil2019-10-101-2/+1
|\ \ \ \ | | | | | | | | | | | | | | | PiperOrigin-RevId: 273585026
| * | | | square away the stuff that hasn't been merged in a manual reviewKrystian Kuzniarek2019-09-161-2/+1
| | |/ / | |/| | | | | | | | | | | | | | This fixes up f2fb48c3 (a manual merge) that has abandoned some things from PR #2407.
* | | | Merge pull request #2475 from peterbarker:pr/google-add-overrideGennadiy Civil2019-10-084-7/+7
|\ \ \ \ | | | | | | | | | | | | | | | PiperOrigin-RevId: 273379796
| * | | | Add many missing override keywordsPeter Barker2019-09-254-7/+7
| |/ / / | | | | | | | | | | | | This helps corrects builds with -Werror=suggest-overrides
* / / / Googletest exportAbseil Team2019-10-031-0/+4
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | Add a compile time check to ensure that the parameters to TEST and TEST_F are not empty Some compilers may already fail in that case and even where it works, it's likely to result in technically invalid code by virtue of creating reserved identifiers: https://en.cppreference.com/w/cpp/language/identifiers PiperOrigin-RevId: 272543242
* | | Googletest exportkuzkry2019-09-163-17/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | Merge 3bdefdb473d304803d2a38e2a2cd5cdc1827c3bd into fb49e6c164490a227bbb7cf5223b846c836a0305 Closes #2407 COPYBARA_INTEGRATE_REVIEW=https://github.com/google/googletest/pull/2407 from kuzkry:StaticAssertTypeEq 3bdefdb473d304803d2a38e2a2cd5cdc1827c3bd PiperOrigin-RevId: 269255328
* | | Merge pull request #2387 from kuzkry:iffShaindel Schwartz2019-09-128-87/+93
|\ \ \ | | | | | | | | | | | | PiperOrigin-RevId: 268693457
OpenPOWER on IntegriCloud