@ -107,7 +107,7 @@ assertion* to get the function arguments printed for free:
| `ASSERT_PRED2(pred2, val1, val2)` | `EXPECT_PRED2(pred2, val1, val2)` | `pred2(val1, val2)` is true |
| `...` | `...` | `...` |
<!-- mdformat on -->
<!-- mdformat on -->
In the above, `predn` is an `n` -ary predicate function or functor, where `val1` ,
`val2` , ..., and `valn` are its arguments. The assertion succeeds if the
predicate returns `true` when applied to the given arguments, and fails
@ -336,7 +336,7 @@ want to learn more, see
| `ASSERT_FLOAT_EQ(val1, val2);` | `EXPECT_FLOAT_EQ(val1, val2);` | the two `float` values are almost equal |
| `ASSERT_DOUBLE_EQ(val1, val2);` | `EXPECT_DOUBLE_EQ(val1, val2);` | the two `double` values are almost equal |
<!-- mdformat on -->
<!-- mdformat on -->
By "almost equal" we mean the values are within 4 ULP's from each other.
@ -348,7 +348,7 @@ The following assertions allow you to choose the acceptable error bound:
| ------------------------------------- | ------------------------------------- | -------------------------------------------------------------------------------- |
| `ASSERT_NEAR(val1, val2, abs_error);` | `EXPECT_NEAR(val1, val2, abs_error);` | the difference between `val1` and `val2` doesn't exceed the given absolute error |
<!-- mdformat on -->
<!-- mdformat on -->
#### Floating-Point Predicate-Format Functions
@ -379,7 +379,7 @@ macros:
| ------------------------------ | ------------------------------ | --------------------- |
| `ASSERT_THAT(value, matcher);` | `EXPECT_THAT(value, matcher);` | value matches matcher |
<!-- mdformat on -->
<!-- mdformat on -->
For example, `StartsWith(prefix)` is a matcher that matches a string starting
with `prefix` , and you can write:
@ -1365,7 +1365,7 @@ namespace:
| `Bool()` | Yields sequence `{false, true}` . |
| `Combine(g1, g2, ..., gN)` | Yields all combinations (Cartesian product) as std\:\:tuples of the values generated by the `N` generators. |
<!-- mdformat on -->
<!-- mdformat on -->
For more details, see the comments at the definitions of these functions.
@ -2155,9 +2155,9 @@ NOTE: This feature should only be used for temporary pain-relief. You still have
to fix the disabled tests at a later date. As a reminder, googletest will print
a banner warning you if a test program contains any disabled tests.
TIP: You can easily count the number of disabled tests you have using `gsearch`
and/or `grep` . This number can be used as a metric for improving your test
quality.
TIP: You can easily count the number of disabled tests you have using
`grep` . This number can be used as a metric for
improving your test quality.
#### Temporarily Enabling Disabled Tests