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

	Commit message (Collapse)	Author	Age	Files	Lines
*	cmake fixes	Gennadiy Civil	2018-08-02	1	-2/+2
\|
*	fixes tests	Gennadiy Civil	2018-08-02	1	-2/+2
\|
*	cleaning up and adding test changes to CMake	Gennadiy Civil	2018-08-02	1	-1/+1
\|
*	various changes to tests	Gennadiy Civil	2018-08-01	1	-7/+49
\|
*	more test changes	Gennadiy Civil	2018-08-01	1	-3/+3
\|
*	adding googletest-json-output unitest	Gennadiy Civil	2018-08-01	1	-0/+21
\|
*	more test changes	Gennadiy Civil	2018-08-01	1	-0/+14
\|
*	more tests changes	Gennadiy Civil	2018-08-01	1	-5/+25
\|
*	googletest list tests unitest	Gennadiy Civil	2018-08-01	1	-5/+5
\|
*	gtest catch exceptions test and gtest shuffle test	Gennadiy Civil	2018-08-01	1	-20/+16
\|
*	changes to googletest break on failure and googletest filter unittests	Gennadiy Civil	2018-08-01	1	-16/+23
\|
*	changes for googletest env var test	Gennadiy Civil	2018-08-01	1	-6/+6
\|
*	googltest-color-test changes	Gennadiy Civil	2018-08-01	1	-5/+5
\|
*	googletest-output-test changes	Gennadiy Civil	2018-08-01	1	-6/+7
\|
*	Formatting changes and upstreaming one test	Gennadiy Civil	2018-08-01	1	-0/+8
\|
*	Adds stacktrace support from Abseil to Google Test	Derek Mauro	2018-07-10	1	-20/+42
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This change adds the ability to generate stacktraces in Google Test on both failures of assertions/expectations and on crashes. The stacktrace support is conditionally available only when using Abseil with Google Test. To use this support, run the test under Bazel with a command like this: bazel test --define absl=1 --test_env=GTEST_INSTALL_FAILURE_SIGNAL_HANDLER=1 //path/to/your:test The "--define absl=1" part enables stacktraces on assertion/expectation failures. The "--test_env=GTEST_INSTALL_FAILURE_SIGNAL_HANDLER=1" part enables the signal handler that logs a stacktrace in the event of a crash (this also requires the "--define absl=1" part). This is not the default since it may interfere with existing tests.
*	Eliminate GTEST_TEST_FILTER_ENV_VAR_.refs/pull/1622/head	Rohan Joyce	2018-06-14	1	-0/+16
\| \| \| \| \| \| \| \|	GTEST_TEST_FILTER_ENV_VAR_ was used to specify an environment variable to obtain the default test filter from. By default it was unset which broke "--test_filter" for bazel. This CL eliminates GTEST_TEST_FILTER_ENV_VAR_ and explicitly obtains the default test filter from the environment variable TESTBRIDGE_TEST_ONLY if it exists.
*	mergesrefs/pull/1469/head	Gennadiy Civil	2018-02-22	1	-0/+10
\|
*	Add ability to throw from ASSERT	Alexey Sokolov	2018-02-08	1	-0/+7
\| \| \| \| \| \| \|	while not losing benefits of EXPECT, and not killing the whole test, as with --gtest_throw_on_failure. 183822976
*	Adding python tests to Bazel build file. refs/pull/1412/head	Gennadiy Civil	2018-01-18	1	-1/+243
\|
*	[Bazel] Detect Windows with cpu value x64_windows and x64_windows_msvcrefs/pull/1388/head	Loo Rong Jie	2018-01-09	1	-3/+6
\| \| \| \|	and x64_windows_msvc
*	Addressing Commentsrefs/pull/1191/head	misterg	2017-08-10	1	-46/+22
\|
*	Added Copyright	misterg	2017-08-10	1	-4/+32
\|
*	Initial Revision, review 164634031	misterg	2017-08-10	1	-2/+0
\|
*	WIP	misterg	2017-08-09	1	-29/+3
\|
*	WIP, win testing	misterg	2017-08-08	1	-4/+7
\|
*	WIP, windows testing	misterg	2017-08-08	1	-2/+2
\|
*	WIP, windows testing	misterg	2017-08-08	1	-2/+2
\|
*	WIP, windows testing	misterg	2017-08-08	1	-3/+9
\|
*	WIP	misterg	2017-08-08	1	-0/+133