@@ -106,7 +106,7 @@ Prefer having checks inside test code.
106106
107107Not only does having test logic outside, e.g. verification method,
108108depending on asserts in product code contradict with several items
109- above but also decreases test’ s readability and stability. It is much
109+ above but also decreases test' s readability and stability. It is much
110110easier to understand that a test is testing when all testing logic is
111111located inside a test or nearby in shared test libraries. As a rule of
112112thumb, the closer a check to a test, the better.
@@ -119,7 +119,7 @@ Prefer `EXPECT` over `ASSERT` if possible.
119119
120120This is related to the [ informativeness] ( #informativeness ) property of
121121tests, information for other checks can help to better localize a
122- defect’ s root-cause. One should use ` ASSERT ` if it is impossible to
122+ defect' s root-cause. One should use ` ASSERT ` if it is impossible to
123123continue test execution or if it does not make much sense. Later in
124124the text, ` EXPECT ` forms will be used to refer to both
125125` ASSERT/EXPECT ` .
@@ -160,7 +160,7 @@ value of the difference between `v1` and `v2` is not greater than `eps`.
160160
161161Use string special macros for C strings comparisons.
162162
163- ` EXPECT_EQ ` just compares pointers’ values, which is hardly what one
163+ ` EXPECT_EQ ` just compares pointers' values, which is hardly what one
164164wants comparing C strings. GoogleTest provides ` EXPECT_STREQ ` and
165165` EXPECT_STRNE ` macros to compare C string contents. There are also
166166case-insensitive versions ` EXPECT_STRCASEEQ ` , ` EXPECT_STRCASENE ` .
@@ -226,7 +226,7 @@ subsystem, etc.
226226
227227This naming scheme helps to find tests, filter them and simplifies
228228test failure analysis. For example, class ` Foo ` - test group ` Foo ` ,
229- compiler logging subsystem - test group ` CompilerLogging ` , G1 GC — test
229+ compiler logging subsystem - test group ` CompilerLogging ` , G1 GC - test
230230group ` G1GC ` , and so forth.
231231
232232### Filename
@@ -287,7 +287,7 @@ Fixture classes should be named after tested classes, subsystems, etc
287287
288288All test purpose friends should have either ` Test ` or ` Testable ` suffix.
289289
290- It greatly simplifies understanding of friendship’ s purpose and allows
290+ It greatly simplifies understanding of friendship' s purpose and allows
291291statically check that private members are not exposed unexpectedly.
292292Having ` FooTest ` as a friend of ` Foo ` without any comments will be
293293understood as a necessary evil to get testability.
@@ -397,7 +397,7 @@ and filter out inapplicable tests.
397397Restore changed flags.
398398
399399It is quite common for tests to configure JVM in a certain way
400- changing flags’ values. GoogleTest provides two ways to set up
400+ changing flags' values. GoogleTest provides two ways to set up
401401environment before a test and restore it afterward: using either
402402constructor and destructor or ` SetUp ` and ` TearDown ` functions. Both ways
403403require to use a test fixture class, which sometimes is too wordy. The
@@ -406,7 +406,7 @@ be used in such cases to restore/set values.
406406
407407Caveats:
408408
409- * Changing a flag’ s value could break the invariants between flags' values and hence could lead to unexpected/unsupported JVM state.
409+ * Changing a flag' s value could break the invariants between flags' values and hence could lead to unexpected/unsupported JVM state.
410410
411411* ` FLAG_SET_* ` macros can change more than one flag (in order to
412412maintain invariants) so it is hard to predict what flags will be
0 commit comments