Gets the message associated with the test part.

Returns the text streamed into this AssertionResult. Test assertions use it when they fail (i.e., the predicate's outcome doesn't match the assertion'

User-defined monitor function */

* Evaluate the given arguments. These can be passed either as a string or as an array. * If nothing is passed, the running script's command line

* Processes an option array. The array elements can either be Option objects or arrays conforming to the format * (short, long, mode [, descripti

* Sets the argument object directly. * * @param Argument $arg * @return Option this object (for chaining calls) */

* Set the default value * * @param scalar $value * @return Argument this object (for chaining calls) * @throws \InvalidArgumentEx

* Set a validation function. * The function must take a string and return true if it is valid, false otherwise. * * @param callable $c

We call this function to set the type of failure SetUp() should generate.

Was SetUp() run?

STL-style container methods.

STL-style container methods.

* Split the string into individual characters, * * @param string $string string to split * @return array */

Gets the number of successful test cases.

Gets the number of successful tests.

Returns the number of the test properties.

Gets the number of all test parts. This is the sum of the number of successful test parts and the number of failed test parts.

* Check if an argument validates according to the specification. * * @param string $arg * @return bool */

The constructor of SingleFailureChecker remembers where to look up test part results, what type of failure we expect, and what substring the failure m

The constructor of SingleFailureChecker remembers where to look up test part results, what type of failure we expect, and what substring the failure m

A convenient wrapper for adding an environment for the test program. You should call this before RUN_ALL_TESTS() is called, probably in main(). If y

INSTANTIATE_TEST_CASE_P macro uses AddGenerator() to record information about a generator.

INSTANTIATE_TEST_CASE_P macro uses AddGenerator() to record information about a generator.

Adds a TestInfo to the unit test. Arguments: set_up_tc: pointer to the function that sets up the test case tear_down_tc: pointer to the function

Adds a TestInfo to the unit test. Arguments: set_up_tc: pointer to the function that sets up the test case tear_down_tc: pointer to the function

TEST_P macro uses AddTestPattern() to record information about a single test in a LocalTestInfo structure. test_case_name is the base name of the test

TEST_P macro uses AddTestPattern() to record information about a single test in a LocalTestInfo structure. test_case_name is the base name of the test

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Advance should not be called on beyond-of-range iterators so no component iterators must be beyond end of range, either.

Creates a Flags struct where the gtest_also_run_disabled_tests flag has the given value.

Creates a UTF-16 wide string from the given ANSI string, allocating memory using new. The caller is responsible for deleting the return value using de

Creates a UTF-16 wide string from the given ANSI string, allocating memory using new. The caller is responsible for deleting the return value using de

Appends a TestPartResult to the array.

Does nothing if the current thread holds the mutex. Otherwise, crashes with high probability.