googletest.git - Google's C++ test framework: https://github.com/google/googletest

	Commit message (Collapse)	Author	Age	Files	Lines
*	Googletest export	misterg	2019-01-14	1	-3/+3
\| \| \| \| \| \|	Change remaining samples to use new Test Suite API PiperOrigin-RevId: 229231566
*	Googletest export	Abseil Team	2018-12-03	1	-3/+3
\| \| \| \| \| \|	Applied fixes for ClangTidy modernize-use-override and modernize-use-using. PiperOrigin-RevId: 223800219
*	Apply clang-tidy modernize-use-nullptr to googletest.	Abseil Team	2018-10-05	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \|	Now that googletest has moved to C++11, it should no longer use NULL or 0 for the null pointer. This patch converts all such usages to nullptr using clang-tidy. This prevents LLVM from issuing -Wzero-as-null-pointer-constant warnings. PiperOrigin-RevId: 215814400
*	Comments changes, no functionality changesrefs/pull/1740/head	Gennadiy Civil	2018-08-14	1	-2/+1
\|
*	remove GTEST_HAS_PARAM_TESTS	Herbert Thielen	2017-09-04	1	-12/+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
*	Samples changes upstreaming	misterg	2017-08-07	1	-1/+1
\|
*	WIP	misterg	2017-08-01	1	-10/+10
\|
*	Move everything in googletest into googletest/googletest	Billy Donahue	2015-08-25	1	-0/+130