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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Running clang-format over all of GoogleTest	Abseil Team	2022-03-15	1	-7/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	A few tests are examining code locations and looking af the resulting line numbers to verify that GoogleTest shows those to users correctly. Some of those locations change when clang-format is run. For those locations, I've wrapped portions in: // clang-format off ... // clang-format on There may be other locations that are currently not tickled by running clang-format. PiperOrigin-RevId: 434844712 Change-Id: I3a9f0a6f39eff741c576b6de389bef9b1d11139d
*	Googletest export	Abseil Team	2018-12-03	1	-1/+1
\| \| \| \| \| \|	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	-5/+5
\| \| \| \| \| \| \| \| \| \| \|	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	-3/+0
\|
*	Merge pull request #1191 from gennadiycivil/master	Gennadiy Civil	2017-08-11	1	-5/+6
\|\ \| \| \| \|	Adding Bazel build to googletest (initial version )
\| *	Initial Revision, review 164634031	misterg	2017-08-10	1	-1/+1
\| \|
\| *	Samples changes upstreaming	misterg	2017-08-07	1	-1/+2
\| \|
\| *	WIP	misterg	2017-08-01	1	-4/+4
\| \|
* \|	fix small typo in commentrefs/pull/1176/head	Herbert Thielen	2017-08-05	1	-1/+1
\|/
*	Move everything in googletest into googletest/googletest	Billy Donahue	2015-08-25	1	-0/+151