summaryrefslogtreecommitdiffstats
path: root/googletest/include/gtest/gtest-param-test.h
Commit message (Collapse)AuthorAgeFilesLines
* Re-generate gtest-param-test.h from gtest-param-test.h.pumpDominic Sacré2018-08-311-20/+17
| | | | | | | | | Commit 6a26e47cfcc174cc85651cbde0b0158d03321e2f changed the formatting of INSTANTIATE_TEST_CASE_P() in the generated header file only. This commit reverts to the formatting produced by running "pump gtest-param-test.h.pump", which seems to be more consistent with the rest of the file.
* Comments changes, no functionality changesrefs/pull/1740/headGennadiy Civil2018-08-141-2/+0
|
* Formatting changes for automatic code managementGennadiy Civil2018-07-271-0/+1
|
* Formatting changes refs/pull/1607/headGennadiy Civil2018-05-231-1/+1
|
* Allow macros inside of parametrized test names.Bernhard Bauer2018-03-121-4/+2
| | | | | | | | | | This allows doing things like TEST_P(TestFixture, MAYBE(TestName)) for nicer conditional test disabling. Upstream of cr/188748737. Tested: Added unit tests MacroNamingTest and MacroNamingTestNonParametrized.
* Code merge, upstreaming accumulated changes, cleanupGennadiy Civil2018-01-101-19/+22
|
* Pass the -Wmissing-declarations warning.David Benjamin2018-01-031-6/+6
| | | | | | This makes it easier to use GTest in projects that build with the -Wmissing-declarations warning. This fixes the warning in headers and source files, though not GTest's own tests as it is rather noisy there.
* remove GTEST_HAS_PARAM_TESTSHerbert Thielen2017-09-041-7/+0
| | | | | | | | As mentioned in issue #360: "Now that all the platforms gtest supports work with value-parameterized tests, we should remove the uses of the GTEST_HAS_PARAM_TESTS macro from the codebase everywhere." https://github.com/google/googletest/issues/360
* Move everything in googletest into googletest/googletestBilly Donahue2015-08-251-0/+1444