summaryrefslogtreecommitdiffstats
path: root/googletest
Commit message (Collapse)AuthorAgeFilesLines
...
* | Setting CMP0054 policy to NEW. This allows to use the string "SHARED" ↵refs/pull/2283/headMatthias Walter2019-06-121-0/+4
| | | | | | | | without interpreting it as a variable.
* | Formatting ChangesGennadiy Civil2019-06-121-2/+2
| |
* | remove obsolete codegear filesGennadiy Civil2019-06-106-440/+0
| |
* | removing obsolete language from docs, CMake and Bazel is the only supporeted ↵Gennadiy Civil2019-06-103-159/+66
| | | | | | | | build methods
* | removing xcode files , as CMake and Bazel is the only supporeted build methodsGennadiy Civil2019-06-1016-2248/+0
| |
* | removing msvc solution, as CMake and Bazel is the only supporeted build methodsGennadiy Civil2019-06-1018-1642/+0
| |
* | Merge pull request #2268 from kalaxy/fuse_spi_in_headerGennadiy Civil2019-06-071-14/+10
|\ \ | | | | | | Fuse gtest-spi.h into the resulting header.
| * | Fuse gtest-spi.h into the resulting header.refs/pull/2268/headKalon Mills2019-06-041-14/+10
| | | | | | | | | | | | | | | Previously this was fused into the source file, but this prevents users of the fused file from using those utilities directly.
* | | Googletest exportAbseil Team2019-06-051-1/+1
| | | | | | | | | | | | | | | | | | fdio_pipe_half is now the same as fdio_pipe_half2. We can switch back to the cleaner name. PiperOrigin-RevId: 251633832
* | | Googletest exportmisterg2019-06-051-1/+1
|/ / | | | | | | | | | | comment change PiperOrigin-RevId: 251231524
* | Googletest exportAbseil Team2019-05-301-0/+9
| | | | | | | | | | | | Add a safety nullptr check to catch the case where the /tmp file used for capturing a stream cannot be created. PiperOrigin-RevId: 250523012
* | Merge pull request #2260 from 741g:mastergennadiycivil2019-05-231-1/+1
|\ \ | | | | | | | | | PiperOrigin-RevId: 249660276
| * | unbreak windows buildrefs/pull/2260/headLingfeng Yang2019-05-221-1/+1
| | | | | | | | | | | | | | | windows msvc toolchain with werror and wconversion will break if converting long to DWORD.
* | | Fix typo introduced in 63be3dcc245 (maintaners -> maintainers)refs/pull/2259/headEnji Cooper2019-05-203-3/+3
|/ / | | | | | | Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
* | Update advanced.mdGennadiy Civil2019-05-171-0/+61
| | | | | | Adding back section that was lost in merge
* | Merge pull request #2254 from chaoran:masterGennadiy Civil2019-05-173-75/+63
|\ \ | | | | | | | | | PiperOrigin-RevId: 248759825
| * | add unit test for overload & operatorrefs/pull/2254/headChaoran Yang2019-05-131-0/+91
| | |
| * | Use std::addressof to instead of plain '&'.Chaoran Yang2019-05-121-2/+2
| | | | | | | | | | | | | | | Otherwise the code won't compile if the '&' operater is overloaded and return something that cannot be casted to void *.
* | | Added docs for testing::RegisterTestGennadiy Civil2019-05-131-0/+72
|/ /
* | Googletest exportAbseil Team2019-05-101-68/+73
| | | | | | | | | | | | Print the test output on assertion failure. PiperOrigin-RevId: 247283764
* | Merge pull request #2245 from daquexian:fix_wsign_conversiongennadiycivil2019-05-031-1/+1
|\ \ | | | | | | | | | PiperOrigin-RevId: 246550729
| * | Fix -Wsign-conversion error by adding static_castrefs/pull/2245/headdaquexian2019-05-021-1/+1
| | |
* | | Googletest exportmisterg2019-05-033-0/+9
|/ / | | | | | | | | | | Clarify build system support - CMake and automake community supported PiperOrigin-RevId: 245821927
* | Merge pull request #2242 from SylvestreG:masterGennadiy Civil2019-04-2925-1/+2083
|\ \ | | | | | | | | | PiperOrigin-RevId: 245798478
| * | Fix compilation on CentOS 7refs/pull/2242/headSylvestre Gallon2019-04-261-1/+1
| |/
* | Removing obsolete codegear and msvc 2010Gennadiy Civil2019-04-2924-2082/+0
| |
* | Googletest exportmisterg2019-04-291-10/+0
| | | | | | | | | | | | Internal Change PiperOrigin-RevId: 245788057
* | Address fallout from -Wsign-conversion work on Windowsrefs/pull/2241/headEnji Cooper2019-04-262-3/+4
|/ | | | | | | | Some Windows users builds were broken after a0d60be. This change addresses the lingering -Wsign-conversion issues with those platforms by adding some missing `static_cast` calls as needed. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
* Googletest exportAbseil Team2019-04-244-6/+37
| | | | | | | | 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
* Googletest exportmisterg2019-04-181-2/+2
| | | | | | Fixes https://github.com/google/googletest/issues/2232 PiperOrigin-RevId: 244237560
* Googletest exportmisterg2019-04-183-12/+18
| | | | | | Expose more information in SuiteApiResolver diagnostic output PiperOrigin-RevId: 244179347
* Merge pull request #2170 from ngie-eign:issue-2146-ver2Gennadiy Civil2019-04-1812-68/+90
|\ | | | | | | PiperOrigin-RevId: 244069956
| * clang: fix `-Wsign-conversion` errorsEnji Cooper2019-04-0612-60/+78
| | | | | | | | | | | | | | | | | | | | | | 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>
* | Googletest exportAbseil Team2019-04-161-1/+1
| | | | | | | | | | | | [googletest] Fix death test condition. PiperOrigin-RevId: 243742424
* | Googletest exportAbseil Team2019-04-161-2/+6
| | | | | | | | | | | | | | | | | | Migrate ZX_WAIT_ASYNC_REPEATING to ZX_WAIT_ASYNC_ONCE ZX_WAIT_ASYNC_REPEATING is deprecated so convert code to use ZX_WAIT_ASYNC_ONCE instead. PiperOrigin-RevId: 243707147
* | Sort Haiku platform definition alphabetically.refs/pull/2230/headCalvin Hill2019-04-121-2/+2
| | | | | | | | | | Fixes a minor ordering issue when defining the platform macro. Also fixes a minor typo: 'Max OS X' -> 'Mac OS X'.
* | Merge pull request #2226 from davidben:msvc-5046Gennadiy Civil2019-04-111-2/+9
|\ \ | | | | | | | | | PiperOrigin-RevId: 243121568
| * | MSVC C5046 warning is unavailable in MSVC 2015.refs/pull/2226/headDavid Benjamin2019-04-091-2/+9
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Merge pull request #2229 from return:haiku-supportGennadiy Civil2019-04-113-32/+36
|\ \ | | | | | | | | | PiperOrigin-RevId: 243104604
| * | Add Haiku platform support.refs/pull/2229/headCalvin Hill2019-04-112-3/+7
| |/ | | | | | | | | This allows googletest to recognize the Haiku operating system when running tests in other projects.
* | replace test case with test suite in the primerrefs/pull/2228/headRong Ou2019-04-111-19/+19
| |
* | add missing periodrefs/pull/2225/headRong Ou2019-04-091-1/+1
|/
* Merge pull request #2148 from ngie-eign:clang-add-explicit-c++11-rtti-flagGennadiy Civil2019-04-051-0/+1
|\ | | | | | | PiperOrigin-RevId: 242038269
| * clang: explicitly enable/disable RTTI support with the compilerEnji Cooper2019-04-041-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add `-frtti` to the compiler with the base flags case so that RTTI is enabled by default with clang. Add its inverse analog, `cxx_no_rtti_flags` in order to test the case with RTTI off, similar to gcc. This reduces the amount of testing/support overhead needed in the non-RTTI case with clang, as the tests currently fail when these two features are off with version 1.8.1. This something I used in when investigating test failures on FreeBSD, as the tests that rely on RTTI were failing with googletest 1.8.1 on the OS platform. More investigation is being done to determine how this should be fixed on FreeBSD 11.2-RELEASE with ports, as the package doesn't currently compile the tests, and when enabled (based on my WIP diff), the tests fail in similar ways. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
* | Googletest exportAbseil Team2019-04-051-5/+5
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [fdio] Improve fdio_pipe_half signature, step 3. The return value on fdio_pipe_half conflated two things: the error code on failure (as a zx_status_t) or a file descriptor on success. This technically worked, because they're both ints, the error code was always negative, and the file descriptor always positive. However, the stated return type of zx_status_t was misleading. This changes the signature such that it always returns an actual zx_status_t, and the file descriptor is returned through a pointer argument. Also remove the last argument, since it was always given the same value. This needs to be done as a soft transition because it's called from the Dart runtime, from googletest, and from Crashpad, and Crashpad and Chromium both depend on googletest on Fuchsia. The steps are as follows: 1) Add fdio_pipe_half2. 2) Update Dart to use fdio_pipe_half2. 3) Update googletest to use fdio_pipe_half2. 4) Roll updated googletest into Chronium. 5) Update Crashpad to use fdio_pipe_half2 and roll updated googletest into it. 6) Update fdio_pipe_half to match fdio_pipe_half2. 7) Update Dart to use fdio_pipe_half again. 8) Update googletest to use fdio_pipe_half again. 9) Roll updated googletest into Chronium. 10) Update Crashpad to use fdio_pipe_half again and roll updated googletest into it. 11) Remove fdio_pipe_half2. This is step 3. PiperOrigin-RevId: 241957137
* Merge pull request #2203 from ngie-eign:issue-2189Gennadiy Civil2019-04-037-5/+150
|\ | | | | | | PiperOrigin-RevId: 241803437
| * Handle GTEST_SKIP() when calling `Environment::SetUp()`refs/pull/2203/headEnji Cooper2019-03-306-5/+95
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-032-4/+4
| | | | | | | | | | Typos: "more then" -> "more than". PiperOrigin-RevId: 241483698
* | Googletest exportAbseil Team2019-04-013-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add HWASan annotations. These mirror existing ASan annotations. HWASan uses memory (address) tagging to detect memory errors: https://clang.llvm.org/docs/HardwareAssistedAddressSanitizerDesign.html It inserts a random tag in the MSB of heap and stack allocation addresses. This tag dominates pointer comparison in StackGrowsDown(), making the result non-deterministic, and entirely unrelated to the actual stack growth direction. The function attribute disables this behavior. The annotations in gtest-printers are there because the printers are used to basically dump memory. The sanitizers may have ideas why this memory should not be accessed, and that is counter productive. In particular, the test may access only part of an array, but in case of a test failure gtest will dump the entire array which may contain uninitialized bytes - that's what SANITIZE_MEMORY annotation is for. There are similar reasons for ADDRESS and THREAD annotations. HWADDRESS in its current implementation can not cause issues there, I believe, but it falls under the same umbrella of tools whose checking should not apply to test printers because it is not the code under test. PiperOrigin-RevId: 241379822
* | Googletest exportAbseil Team2019-04-0114-442/+8
|/ | | | | | | | 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
generated by cgit v0.12 at 2025-04-09 16:37:37 (GMT)