]> git-server-git.apps.pok.os.sepia.ceph.com Git - googletest.git/commitdiff
Adjust includes to use <> instead of "", consistent with quickstart pages.
authorAbseil Team <absl-team@google.com>
Fri, 28 Jul 2023 16:50:50 +0000 (09:50 -0700)
committerCopybara-Service <copybara-worker@google.com>
Fri, 28 Jul 2023 16:51:41 +0000 (09:51 -0700)
Right now, gtest documentation uses different #include syntax. The quickstart
pages (e.g., http://google.github.io/googletest/quickstart-bazel.html#create-and-run-a-binary) are checked in with `#include <gtest/gtest.h>` However, other
documentation (such as the primer) uses `#include "gtest/gtest.h"` (e.g.,
https://google.github.io/googletest/primer.html#writing-the-main-function).

PiperOrigin-RevId: 551878641
Change-Id: Iab93cc1da3ef4870a07b624071b75d6e9d3568c1

docs/gmock_cheat_sheet.md
docs/gmock_cook_book.md
docs/gmock_for_dummies.md
docs/primer.md
docs/reference/assertions.md
googletest/README.md

index 2fb0403e616a79a46294a6dd5c8489f1f1dd2a78..ddafaaa2206cd618225109c6e422803a214e6b94 100644 (file)
@@ -20,7 +20,7 @@ class Foo {
 (note that `~Foo()` **must** be virtual) we can define its mock as
 
 ```cpp
-#include "gmock/gmock.h"
+#include <gmock/gmock.h>
 
 class MockFoo : public Foo {
  public:
index e319bf636b5da9c994e284c9ef1bd9fc73db54d7..da10918c9659fd5d0d40f62039d03d8f5e15e0b0 100644 (file)
@@ -3194,7 +3194,7 @@ You can unlock this power by running your test with the `--gmock_verbose=info`
 flag. For example, given the test program:
 
 ```cpp
-#include "gmock/gmock.h"
+#include <gmock/gmock.h>
 
 using ::testing::_;
 using ::testing::HasSubstr;
index b7264d3587f71ada659741bd6c47ac015ff46e99..43f907aaa5da1e25e9dc5cc3544dc7137314cdc4 100644 (file)
@@ -164,7 +164,7 @@ follow:
 After the process, you should have something like:
 
 ```cpp
-#include "gmock/gmock.h"  // Brings in gMock.
+#include <gmock/gmock.h>  // Brings in gMock.
 
 class MockTurtle : public Turtle {
  public:
@@ -224,8 +224,8 @@ Here's an example:
 
 ```cpp
 #include "path/to/mock-turtle.h"
-#include "gmock/gmock.h"
-#include "gtest/gtest.h"
+#include <gmock/gmock.h>
+#include <gtest/gtest.h>
 
 using ::testing::AtLeast;                         // #1
 
index c3aee3cc644b0dc79390126b730a269b57f2251e..f2a97a7269b79fd1124ed15f3f1efb8687f80ca0 100644 (file)
@@ -395,7 +395,7 @@ You can start from this boilerplate:
 ```c++
 #include "this/package/foo.h"
 
-#include "gtest/gtest.h"
+#include <gtest/gtest.h>
 
 namespace my {
 namespace project {
index 1cdff266e284f4f9f5496944a98a865753364d71..aa1dbc04bd19bba2bad65fbc5453c8c5b9af71ed 100644 (file)
@@ -88,7 +88,7 @@ For example, the following code verifies that the string `value1` starts with
 10:
 
 ```cpp
-#include "gmock/gmock.h"
+#include <gmock/gmock.h>
 
 using ::testing::AllOf;
 using ::testing::Gt;
index 6bbd7f875f7ba3e7339cf8193a630ccdbfe0ae94..815f3fc02bab9cabe7040520af9baa4263e1ad03 100644 (file)
@@ -145,7 +145,7 @@ We list the most frequently used macros below. For a complete list, see file
 ### Multi-threaded Tests
 
 GoogleTest is thread-safe where the pthread library is available. After
-`#include "gtest/gtest.h"`, you can check the
+`#include <gtest/gtest.h>`, you can check the
 `GTEST_IS_THREADSAFE` macro to see whether this is the case (yes if the macro is
 `#defined` to 1, no if it's undefined.).