From 4137a0ec074be4872931e6656039f59dd892a6cf Mon Sep 17 00:00:00 2001 From: dota17 Date: Tue, 26 May 2020 19:40:32 +0800 Subject: [PATCH] Spelling errors identified by spell scanning --- test/gtest-1.10.0/googlemock/docs/cook_book.md | 4 ++-- test/gtest-1.10.0/googlemock/test/gmock-matchers_test.cc | 2 +- .../googletest/include/gtest/internal/gtest-filepath.h | 2 +- test/gtest-1.10.0/googletest/test/googletest-output-test_.cc | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/test/gtest-1.10.0/googlemock/docs/cook_book.md b/test/gtest-1.10.0/googlemock/docs/cook_book.md index ea55ab3..14dbbf7 100644 --- a/test/gtest-1.10.0/googlemock/docs/cook_book.md +++ b/test/gtest-1.10.0/googlemock/docs/cook_book.md @@ -1454,7 +1454,7 @@ the pointer is copied. When the last matcher that references the implementation object dies, the implementation object will be deleted. Therefore, if you have some complex matcher that you want to use again and -again, there is no need to build it everytime. Just assign it to a matcher +again, there is no need to build it every time. Just assign it to a matcher variable and use that variable repeatedly! For example, ```cpp @@ -2608,7 +2608,7 @@ efficient. When the last action that references the implementation object dies, the implementation object will be deleted. If you have some complex action that you want to use again and again, you may -not have to build it from scratch everytime. If the action doesn't have an +not have to build it from scratch every time. If the action doesn't have an internal state (i.e. if it always does the same thing no matter how many times it has been called), you can assign it to an action variable and use that variable repeatedly. For example: diff --git a/test/gtest-1.10.0/googlemock/test/gmock-matchers_test.cc b/test/gtest-1.10.0/googlemock/test/gmock-matchers_test.cc index 0373526..5bf4d7a 100644 --- a/test/gtest-1.10.0/googlemock/test/gmock-matchers_test.cc +++ b/test/gtest-1.10.0/googlemock/test/gmock-matchers_test.cc @@ -1572,7 +1572,7 @@ TEST(PairTest, MatchesCorrectly) { EXPECT_THAT(p, Pair(25, "foo")); EXPECT_THAT(p, Pair(Ge(20), HasSubstr("o"))); - // 'first' doesnt' match, but 'second' matches. + // 'first' doesn't match, but 'second' matches. EXPECT_THAT(p, Not(Pair(42, "foo"))); EXPECT_THAT(p, Not(Pair(Lt(25), "foo"))); diff --git a/test/gtest-1.10.0/googletest/include/gtest/internal/gtest-filepath.h b/test/gtest-1.10.0/googletest/include/gtest/internal/gtest-filepath.h index c11b101..57fe57f 100644 --- a/test/gtest-1.10.0/googletest/include/gtest/internal/gtest-filepath.h +++ b/test/gtest-1.10.0/googletest/include/gtest/internal/gtest-filepath.h @@ -195,7 +195,7 @@ class GTEST_API_ FilePath { void Normalize(); - // Returns a pointer to the last occurence of a valid path separator in + // Returns a pointer to the last occurrence of a valid path separator in // the FilePath. On Windows, for example, both '/' and '\' are valid path // separators. Returns NULL if no path separator was found. const char* FindLastPathSeparator() const; diff --git a/test/gtest-1.10.0/googletest/test/googletest-output-test_.cc b/test/gtest-1.10.0/googletest/test/googletest-output-test_.cc index 4f716d8..8101675 100644 --- a/test/gtest-1.10.0/googletest/test/googletest-output-test_.cc +++ b/test/gtest-1.10.0/googletest/test/googletest-output-test_.cc @@ -1078,7 +1078,7 @@ auto dynamic_test = ( "BadDynamicFixture1", "TestBase", nullptr, nullptr, __FILE__, __LINE__, []() -> testing::Test* { return new DynamicTest; }), - // Register two tests with the same fixture incorrectly by ommiting the + // Register two tests with the same fixture incorrectly by omitting the // return type. testing::RegisterTest( "BadDynamicFixture2", "FixtureBase", nullptr, nullptr, __FILE__,