summaryrefslogtreecommitdiffstats
path: root/googletest/test
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #2453 from kuzkry:gtest-port-clean-up_kMaxBiggestIntXiaoyi Zhang2019-11-042-16/+15
|\ | | | | | | PiperOrigin-RevId: 278008286
* \ Merge pull request #2453 from kuzkry:gtest-port-clean-up_kMaxBiggestIntvslashg2019-11-012-15/+16
|\ \ | |/ | | | | PiperOrigin-RevId: 277979766
| * remove BiggestIntrefs/pull/2453/headKrystian Kuzniarek2019-10-242-11/+11
| |
* | replace autogenerated TypesX classes by variadic onesKrystian Kuzniarek2019-10-251-4/+5
| |
* | Merge pull request #2517 from snarkmaster:masterGennadiy Civil2019-10-223-1/+68
|\ \ | | | | | | | | | PiperOrigin-RevId: 275869169
| * | [googletest] Output skip messagerefs/pull/2517/headAlexey Spiridonov2019-10-173-1/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 #2507 from roblub:masterGennadiy Civil2019-10-171-2/+2
|\ \ \ | |/ / |/| | | | | PiperOrigin-RevId: 275076905
| * | Add more override keywordsrefs/pull/2507/headRobert Luberda2019-10-111-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Merge pull request #2421 from kuzkry:cleanup-for-regexAndy Soffer2019-10-161-1/+0
|\ \ \ | | | | | | | | | | | | PiperOrigin-RevId: 275058934
| * | | change usingsKrystian Kuzniarek2019-09-121-1/+0
| | | |
* | | | Googletest exportAbseil Team2019-10-162-14/+3
| |/ / |/| | | | | | | | | | | | | | | | | 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
* | | Googletest exportAbseil Team2019-10-111-1/+32
| | | | | | | | | | | | | | | | | | | | | | | | - 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-11/+6
| | | | | | | | | | | | | | | | | | | | | 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-103-5/+5
|/ / | | | | | | | | | | | | 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 #2387 from kuzkry:iffShaindel Schwartz2019-09-127-26/+27
|\ \ | | | | | | | | | PiperOrigin-RevId: 268693457
| * | restore mistakenly removed iffs in their explicit formrefs/pull/2387/headKrystian Kuzniarek2019-08-207-26/+26
| | | | | | | | | | | | | | | Due to confusion arisen from "iff" standing for "if and only if", this commit uses the latter.
* | | Googletest exportHosein Ghahremanzadeh2019-09-121-10/+4
| |/ |/| | | | | | | | | | | | | | | Merge 4c9ef099b29d2c840c04643cd9662fd7be712f7b into 565f1b848215b77c3732bca345fe76a0431d8b34 Closes #2403 COPYBARA_INTEGRATE_REVIEW=https://github.com/google/googletest/pull/2403 from IYP-Programer-Yeah:remove-compile-assert-type-equal 4c9ef099b29d2c840c04643cd9662fd7be712f7b PiperOrigin-RevId: 268681883
* | Googletest exportkuzkry2019-09-061-25/+0
| | | | | | | | | | | | | | | | | | Merge 7f4f58da20e1066a888d3e4bcbef541db798a605 into 90a443f9c2437ca8a682a1ac625eba64e1d74a8a Closes #2395 COPYBARA_INTEGRATE_REVIEW=https://github.com/google/googletest/pull/2395 from kuzkry:custom-type-traits-remove_reference 7f4f58da20e1066a888d3e4bcbef541db798a605 PiperOrigin-RevId: 266189044
* | Merge pull request #2398 from kuzkry:custom-type-traits-iterator_traitsGennadiy Civil2019-08-291-18/+0
|\ \ | | | | | | | | | PiperOrigin-RevId: 266136896
| * | remove a custom implementation of std::iterator_traitsKrystian Kuzniarek2019-08-131-18/+0
| | |
* | | Merge pull request #2401 from kuzkry:custom-type-traits-add_lvalue_referenceXiaoyi Zhang2019-08-231-25/+0
|\ \ \ | | | | | | | | | | | | PiperOrigin-RevId: 264842713
| * | | remove a custom implementation of std::add_lvalue_referencerefs/pull/2401/headKrystian Kuzniarek2019-08-131-25/+0
| |/ /
* | | Merge pull request #2393 from kuzkry:custom-type-traits-remove_constXiaoyi Zhang2019-08-211-29/+2
|\ \ \ | |_|/ |/| | | | | PiperOrigin-RevId: 264652890
| * | remove a custom implementation of std::remove_constrefs/pull/2393/headKrystian Kuzniarek2019-08-131-29/+2
| |/
* | Merge pull request #2381 from Yannic:fix_bazelGennadiy Civil2019-08-191-0/+3
|\ \ | | | | | | | | | PiperOrigin-RevId: 264186624
| * | Prepare for Bazel incompatible changesYannic Bonenberger2019-08-071-0/+3
| | | | | | | | | | | | | | | | | | Fixes googletest for upcoming `--incompatible_load_cc_rules_from_bzl` (https://github.com/bazelbuild/bazel/issues/8743) and `--incompatible_load_python_rules_from_bzl` (https://github.com/bazelbuild/bazel/issues/9006). This change was automatically generated with `buildifier -lint=fix -warnings=all $(find . -name "BUILD" -o -name "BUILD.bazel" -o -name "*.bzl")`.
* | | remove custom implementations of std::is_samerefs/pull/2399/headKrystian Kuzniarek2019-08-142-12/+13
| |/ |/|
* | Merge pull request #2372 from pitrou:issue2371-windows-crt-assertsGennadiy Civil2019-08-071-0/+56
|\ \ | | | | | | | | | PiperOrigin-RevId: 262040609
| * | Fix #2371: Redirect Windows CRT assertions to stderrrefs/pull/2372/headAntoine Pitrou2019-08-061-0/+56
| |/
* | Merge pull request #2111 from knuto:pr/remove_slashGennadiy Civil2019-08-062-3/+14
|\ \ | |/ |/| | | PiperOrigin-RevId: 261906004
| * Remove / from parameterized test names if base test name is emptyrefs/pull/2111/headKnut Omang2019-04-262-3/+18
| | | | | | | | | | | | | | This is useful to let a subsystem generate test names based on parameterized tests without exposing them as such to the user. Signed-off-by: Knut Omang <knut.omang@oracle.com>
* | Googletest exportmisterg2019-08-012-5/+119
| | | | | | | | | | | | Internal Change PiperOrigin-RevId: 260939845
* | fix typosrefs/pull/2356/headKrystian Kuzniarek2019-07-307-23/+23
| |
* | Googletest exportAbseil Team2019-07-265-481/+507
| | | | | | | | | | | | | | | | Adds ISO8601 timestamps to XML output and RFC3339 timestamps to JSON output. Adds timestamps to testsuites, testsuite and testcases structured JSON/XML output for better reporting how/where time is spent on tests. PiperOrigin-RevId: 260039817
* | Merge pull request #2254 from chaoran:masterGennadiy Civil2019-05-171-0/+59
|\ \ | | | | | | | | | PiperOrigin-RevId: 248759825
| * | add unit test for overload & operatorrefs/pull/2254/headChaoran Yang2019-05-131-0/+91
|/ /
* | Googletest exportAbseil Team2019-05-101-68/+73
|/ | | | | | Print the test output on assertion failure. PiperOrigin-RevId: 247283764
* Googletest exportAbseil Team2019-04-243-6/+32
| | | | | | | | Add GTEST_FAIL_AT, an equivalent to ADD_FAILURE_AT but that spawns a fatal failure rather than a non-fatal, eg. the equivalent of an ASSERT* failure rather than an EXPECT* failure. PiperOrigin-RevId: 244746609
* Merge pull request #2170 from ngie-eign:issue-2146-ver2Gennadiy Civil2019-04-183-22/+27
|\ | | | | | | PiperOrigin-RevId: 244069956
| * clang: fix `-Wsign-conversion` errorsEnji Cooper2019-04-063-22/+24
|/ | | | | | | | | | | 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>
* Merge pull request #2203 from ngie-eign:issue-2189Gennadiy Civil2019-04-033-0/+120
|\ | | | | | | PiperOrigin-RevId: 241803437
| * Handle GTEST_SKIP() when calling `Environment::SetUp()`refs/pull/2203/headEnji Cooper2019-03-302-0/+67
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gtest prior to this change would completely ignore `GTEST_SKIP()` if called in `Environment::SetUp()`, instead of bailing out early, unlike `Test::SetUp()`, which would cause the tests themselves to be skipped. The only way (prior to this change) to skip the tests would be to trigger a fatal error via `GTEST_FAIL()`. Desirable behavior, in this case, when dealing with `Environment::SetUp()` is to check for prerequisites on a system (example, kernel supports a particular featureset, e.g., capsicum), and skip the tests. The alternatives prior to this change would be undesirable: - Failing sends the wrong message to the test user, as the result of the tests is indeterminate, not failed. - Having to add per-test class abstractions that override `SetUp()` to test for the capsicum feature set, then skip all of the tests in their respective SetUp fixtures, would be a lot of human and computational work; checking for the feature would need to be done for all of the tests, instead of once for all of the tests. For those reasons, making `Environment::SetUp()` handle `GTEST_SKIP()`, by not executing the testcases, is the most desirable solution. In order to properly diagnose what happened when running the tests if they are skipped, print out the diagnostics in an ad hoc manner. Update the documentation to note this change and integrate a new test, gtest_skip_in_environment_setup_test, into the test suite. This change addresses #2189. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
* | Googletest exportAbseil Team2019-04-014-168/+2
|/ | | | | | | | 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
* Googletest exportAbseil Team2019-03-284-324/+478
| | | | | | Update XML and JSON output to be consistent with the standard. PiperOrigin-RevId: 239833242
* Googletest exportAbseil Team2019-03-211-3/+2
| | | | | | Remove mention of unused type ProtocolMessage. PiperOrigin-RevId: 239242706
* Googletest exportAbseil Team2019-03-051-18/+52
| | | | | | | | | | | | | | | | | | | | | | | | 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
* Don't hardcode the filename in ↵refs/pull/2147/headEnji Cooper2019-02-211-1/+1
| | | | | | | | | | | | | | | | | `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>
* Merge pull request #2121 from ngie-eign:add-dragonflybsd-and-kfreebsd-supportGennadiy Civil2019-02-131-1/+3
|\ | | | | | | PiperOrigin-RevId: 233789488
| * Import `patch-bsd-defines` from FreeBSD ports [1]Enji Cooper2019-02-131-1/+3
| | | | | | | | | | | | | | | | | | | | 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>
* | Fix -Wunused-private-field issues with clangrefs/pull/2119/headEnji Cooper2019-02-131-0/+2
|/ | | | | | | Provide dummy accessors for private values that are set in initializers, but not actually used. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
generated by cgit v0.12 at 2024-07-18 19:46:06 (GMT)