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	-14/+10
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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	misterg	2019-01-02	1	-1/+0
\| \| \| \| \| \|	Internal Change PiperOrigin-RevId: 227575279
*	Apply clang-tidy modernize-use-nullptr to googletest.	Abseil Team	2018-10-05	1	-2/+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 changes.	Gennadiy Civil	2018-08-14	1	-1/+1
\|
*	Comments changes, no functionality changesrefs/pull/1740/head	Gennadiy Civil	2018-08-14	1	-2/+1
\|
*	Add ability to throw from ASSERT	Alexey Sokolov	2018-02-08	1	-0/+119
	while not losing benefits of EXPECT, and not killing the whole test, as with --gtest_throw_on_failure. 183822976