Update primer.md
This commit is contained in:
parent
baf2115a59
commit
7abf99d941
@ -219,18 +219,18 @@ as `ASSERT_EQ(expected, actual)`, so lots of existing code uses this order. Now
|
||||
The assertions in this group compare two **C strings**. If you want to compare
|
||||
two `string` objects, use `EXPECT_EQ`, `EXPECT_NE`, and etc instead.
|
||||
|
||||
| Fatal assertion | Nonfatal assertion | Verifies |
|
||||
| ----------------------- | ----------------------- | ---------------------- |
|
||||
| `ASSERT_STREQ(str1, | `EXPECT_STREQ(str1, | the two C strings have |
|
||||
| str2);` | str2);` | the same content |
|
||||
| `ASSERT_STRNE(str1, | `EXPECT_STRNE(str1, | the two C strings have |
|
||||
| str2);` | str2);` | different contents |
|
||||
| `ASSERT_STRCASEEQ(str1, | `EXPECT_STRCASEEQ(str1, | the two C strings have |
|
||||
| str2);` | str2);` | the same content, |
|
||||
| | | ignoring case |
|
||||
| `ASSERT_STRCASENE(str1, | `EXPECT_STRCASENE(str1, | the two C strings have |
|
||||
| str2);` | str2);` | different contents, |
|
||||
| | | ignoring case |
|
||||
| Fatal assertion | Nonfatal assertion | Verifies |
|
||||
| ------------------------ | ------------------------ | ---------------------- |
|
||||
| `ASSERT_STREQ(str1,` | `EXPECT_STREQ(str1,` | the two C strings have |
|
||||
| `str2);` | `str2);` | the same content |
|
||||
| `ASSERT_STRNE(str1,` | `EXPECT_STRNE(str1,` | the two C strings have |
|
||||
| `str2);` | `str2);` | different contents |
|
||||
| `ASSERT_STRCASEEQ(str1,` | `EXPECT_STRCASEEQ(str1,` | the two C strings have |
|
||||
| `str2);` | `str2);` | the same content, |
|
||||
| | | ignoring case |
|
||||
| `ASSERT_STRCASENE(str1,` | `EXPECT_STRCASENE(str1,` | the two C strings have |
|
||||
| `str2);` | `str2);` | different contents, |
|
||||
| | | ignoring case |
|
||||
|
||||
Note that "CASE" in an assertion name means that case is ignored. A `NULL`
|
||||
pointer and an empty string are considered *different*.
|
||||
|
Loading…
Reference in New Issue
Block a user