Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
yangql
googletest
Commits
bb9fc6f6
"git@developer.sourcefind.cn:yangql/googletest.git" did not exist on "a1dd07786b9a780a10be9dd643096b28f5a266d2"
Unverified
Commit
bb9fc6f6
authored
Jul 21, 2018
by
Stian Valle
Committed by
GitHub
Jul 21, 2018
Browse files
Update primer.md
parent
7abf99d9
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
12 deletions
+6
-12
googletest/docs/primer.md
googletest/docs/primer.md
+6
-12
No files found.
googletest/docs/primer.md
View file @
bb9fc6f6
...
@@ -219,18 +219,12 @@ as `ASSERT_EQ(expected, actual)`, so lots of existing code uses this order. Now
...
@@ -219,18 +219,12 @@ 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
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.
two
`string`
objects, use
`EXPECT_EQ`
,
`EXPECT_NE`
, and etc instead.
| Fatal assertion | Nonfatal assertion | Verifies |
| Fatal assertion | Nonfatal assertion | Verifies |
| ------------------------ | ------------------------ | ---------------------- |
| ------------------------------- | ------------------------------- | -------------------------------------------------------- |
|
`ASSERT_STREQ(str1,`
|
`EXPECT_STREQ(str1,`
| the two C strings have |
|
`ASSERT_STREQ(str1, str2);`
|
`EXPECT_STREQ(str1, str2);`
| the two C strings have the same content |
|
`str2);`
|
`str2);`
| the same content |
|
`ASSERT_STRNE(str1, str2);`
|
`EXPECT_STRNE(str1, str2);`
| the two C strings have different contents |
|
`ASSERT_STRNE(str1,`
|
`EXPECT_STRNE(str1,`
| the two C strings have |
|
`ASSERT_STRCASEEQ(str1, str2);`
|
`EXPECT_STRCASEEQ(str1, str2);`
| the two C strings have the same content, ignoring case |
|
`str2);`
|
`str2);`
| different contents |
|
`ASSERT_STRCASENE(str1, str2);`
|
`EXPECT_STRCASENE(str1, str2);`
| the two C strings have different contents, ignoring case |
|
`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`
Note that "CASE" in an assertion name means that case is ignored. A
`NULL`
pointer and an empty string are considered
*different*
.
pointer and an empty string are considered
*different*
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment