Docs: Add examples for `FieldsAre` matcher
PiperOrigin-RevId: 367263024

Migrate away from deprecated --heap_check=strict

PiperOrigin-RevId: 367226846

This is part of a soft transition over to having ZX_INFO_PROCESS
populate a new struct. See fxbug.dev/30751 for more details.

PiperOrigin-RevId: 367083068

Docs: Clarifying matcher in `Pointwise` and `UnorderedPointwise`
PiperOrigin-RevId: 367059198

Disable blank issue template, delete question template

PiperOrigin-RevId: 366874747

Add macros to omit {EXPECT,ASSERT}_{TRUE,FALSE}

PiperOrigin-RevId: 366455905

PiperOrigin-RevId: 365572439

Delete extra whitespace in gtest_xml_test_utils.py

PiperOrigin-RevId: 365140844

Clarify explanation of mocking free functions

PiperOrigin-RevId: 364943561

Minor formatting updates

PiperOrigin-RevId: 364935205

Code style cleanup in docs

PiperOrigin-RevId: 364907938

Update advanced.md

PiperOrigin-RevId: 364839958

Update explanation of `EXPECT_EQ(NULL, ptr)` in FAQ

PiperOrigin-RevId: 364626422

Code style cleanups in cheat sheet

PiperOrigin-RevId: 364465553

Add CMake quickstart

PiperOrigin-RevId: 364437779

Add Bazel quickstart

PiperOrigin-RevId: 364419540

Print std::u8string, std::u16string, and std::u32string as string literals

Previously, these types were printed as "{ U+123, U+456, U+789 }". However,
printed output in that form is difficult to compare against any literals that
might be defined in code. Instead, just treat these types like std::string
and std::wstring, escaping non-ASCII characters with a hexadecimal escape
sequence.

The tests have also been updated to cover the new functionality: as a bonus,
the tests now also pass with the MSVC toolchain.

Internally, the code has been reorganized to primarily operate in terms of
char32_t, under the assumption that char32_t will always be at least as big
as wchar_t. While that assumption is currently true, perhaps it won't be in
the future...

PiperOrigin-RevId: 364033132

PiperOrigin-RevId: 363176008

PiperOrigin-RevId: 363063211

gtest: Output a canned test suite for environment failures in XML/JSON

This surfaces useful information about the environment failure in a structured form.

As we can see from the updated test, previously unsurfaced information is now present.

PiperOrigin-RevId: 362292322

PiperOrigin-RevId: 362216935

Update CONTRIBUTING link in README

PiperOrigin-RevId: 362141000

Internal change

PiperOrigin-RevId: 362040448

Add missing period and use "that" in restrictive clause.

PiperOrigin-RevId: 361941663

Update READMEs and issue template

PiperOrigin-RevId: 361931644

Use monotonic time to measure test duration

System time may be updated while a test is running. When this occurs a
duration measured using system time may appear to move backwards, or
jump far forwards.
This change updates the duration measurement to use monotonic time
instead. Timestamps for the test start still use system time.

PiperOrigin-RevId: 361700881

gtest.cc: Split out functions for printing `TestResult` objects

This will make it possible to reuse this code for outputting the "ad_hoc" `TestResult` objects in structured form in XML/JSON.

PiperOrigin-RevId: 361604860

PiperOrigin-RevId: 361213113

PiperOrigin-RevId: 361175466

Add CI test scripts

PiperOrigin-RevId: 360931988

Format WORKSPACE and googlemock/test/BUILD.bazel using buildifier

PiperOrigin-RevId: 360913861

Fix enum names in a value-parameterized test example.

PiperOrigin-RevId: 360559723

Add Supported Platforms page to docs

PiperOrigin-RevId: 360307129

Update gtest doc link

PiperOrigin-RevId: 359622286

Update links in index.md

PiperOrigin-RevId: 358956598

This is incompatible with compiler caches such as sccache and
clcache. If a project including Google Test specifies /Z7 instead,
building fails with:

sccache C:\PROGRA~2\MICROS~1\2019\ENTERP~1\VC\Tools\MSVC\1428~1.293\bin\Hostx64\x64\cl.exe  /nologo /TP -D__SSE2__ -D__SSE__ -I..\lib\googletest-1.10.x\googlemock\include -I..\lib\googletest-1.10.x\googlemock -I..\lib\googletest-1.10.x\googletest\include -I..\lib\googletest-1.10.x\googletest /DWIN32 /D_WINDOWS /W4 /GR  /MD /Z7 /O2 /Ob1 /DNDEBUG -GS -W4 -WX -wd4251 -wd4275 -nologo -J -Zi -D_UNICODE -DUNICODE -DWIN32 -D_WIN32 -DSTRICT -DWIN32_LEAN_AND_MEAN -wd4702 -DGTEST_HAS_PTHREAD=0 -EHsc -D_HAS_EXCEPTIONS=1  /Gy /showIncludes /Folib\googletest-1.10.x\googlemock\CMakeFiles\gmock_main.dir\src\gmock-all.cc.obj /Fdbin\gmock_main.pdb /FS -c ..\lib\googletest-1.10.x\googlemock\src\gmock-all.cc
FAILED: lib/googletest-1.10.x/googlemock/CMakeFiles/gmock_main.dir/src/gmock-all.cc.obj
..\lib\googletest-1.10.x\googletest\src\gtest-all.cc: fatal error C1041: cannot open program database 'D:\a\mixxx\mixxx\build\bin\gmock_main.pdb'; if multiple CL.EXE write to the same .PDB file, please use /FS
cl : Command line warning D9025 : overriding '/Z7' with '/Zi'

Included the string returned by their `name()` member function with the output of `PrintTo`.

Typical use case:

    std::unique_ptr<AbstractProduct> product = FactoryMethod();
    // Assert that the product is of type X:
    ASSERT_EQ(std::type_index{typeid(*product)},
              std::type_index{typeid(ProductX)});

Possible output in case of a test assert failure, now including the names of the compared type indices:

> error: Expected equality of these values:
>  std::type_index(typeid(*product))
>    Which is: 8-byte object <D0-65 54-8C F6-7F 00-00> ("class ProductY")
>  std::type_index(typeid(ProductX))
>    Which is: 8-byte object <40-64 54-8C F6-7F 00-00> ("class ProductX")

With help from Krystian Kuzniarek.

Remove anchors from page titles in docs

PiperOrigin-RevId: 358474917

Add files for GitHub Pages

PiperOrigin-RevId: 358289110