%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµùÕ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream
Name: Google Test: Google's C++ Testing Framework Short Name: googletest URL: https://github.com/google/googletest.git Version: 1.8.0.git-9518a57428ae0a7ed450c1361768e84a2a38af5a License: BSD Security critical: no Google Test is imported as-is, to facilitate version bumping. However, the file/directory layout of Google Test is not yet considered stable. Therefore, until Google Test's layout stabilizes, Chromium code MUST NOT depend on it directly. Instead, Chromium code MUST: * #include the headers in testing/gtest and testing/gmock * use //testing/gtest(:gtest_main) and //testing/gmock(:gmock_main) in BUILD.gn deps This will allow us to adapt to Google Test changes with minimal disruption.