Spelling errors identified by spell scanning
This commit is contained in:
parent
cb7bb9821d
commit
4137a0ec07
@ -1454,7 +1454,7 @@ the pointer is copied. When the last matcher that references the implementation
|
|||||||
object dies, the implementation object will be deleted.
|
object dies, the implementation object will be deleted.
|
||||||
|
|
||||||
Therefore, if you have some complex matcher that you want to use again and
|
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,
|
variable and use that variable repeatedly! For example,
|
||||||
|
|
||||||
```cpp
|
```cpp
|
||||||
@ -2608,7 +2608,7 @@ efficient. When the last action that references the implementation object dies,
|
|||||||
the implementation object will be deleted.
|
the implementation object will be deleted.
|
||||||
|
|
||||||
If you have some complex action that you want to use again and again, you may
|
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
|
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
|
it has been called), you can assign it to an action variable and use that
|
||||||
variable repeatedly. For example:
|
variable repeatedly. For example:
|
||||||
|
|||||||
@ -1572,7 +1572,7 @@ TEST(PairTest, MatchesCorrectly) {
|
|||||||
EXPECT_THAT(p, Pair(25, "foo"));
|
EXPECT_THAT(p, Pair(25, "foo"));
|
||||||
EXPECT_THAT(p, Pair(Ge(20), HasSubstr("o")));
|
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(42, "foo")));
|
||||||
EXPECT_THAT(p, Not(Pair(Lt(25), "foo")));
|
EXPECT_THAT(p, Not(Pair(Lt(25), "foo")));
|
||||||
|
|
||||||
|
|||||||
@ -195,7 +195,7 @@ class GTEST_API_ FilePath {
|
|||||||
|
|
||||||
void Normalize();
|
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
|
// the FilePath. On Windows, for example, both '/' and '\' are valid path
|
||||||
// separators. Returns NULL if no path separator was found.
|
// separators. Returns NULL if no path separator was found.
|
||||||
const char* FindLastPathSeparator() const;
|
const char* FindLastPathSeparator() const;
|
||||||
|
|||||||
@ -1078,7 +1078,7 @@ auto dynamic_test = (
|
|||||||
"BadDynamicFixture1", "TestBase", nullptr, nullptr, __FILE__, __LINE__,
|
"BadDynamicFixture1", "TestBase", nullptr, nullptr, __FILE__, __LINE__,
|
||||||
[]() -> testing::Test* { return new DynamicTest<true>; }),
|
[]() -> testing::Test* { return new DynamicTest<true>; }),
|
||||||
|
|
||||||
// Register two tests with the same fixture incorrectly by ommiting the
|
// Register two tests with the same fixture incorrectly by omitting the
|
||||||
// return type.
|
// return type.
|
||||||
testing::RegisterTest(
|
testing::RegisterTest(
|
||||||
"BadDynamicFixture2", "FixtureBase", nullptr, nullptr, __FILE__,
|
"BadDynamicFixture2", "FixtureBase", nullptr, nullptr, __FILE__,
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user