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
baf2115a
Unverified
Commit
baf2115a
authored
Jul 21, 2018
by
Stian Valle
Committed by
GitHub
Jul 21, 2018
Browse files
Update primer.md
parent
2a151c93
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
7 deletions
+7
-7
googletest/docs/primer.md
googletest/docs/primer.md
+7
-7
No files found.
googletest/docs/primer.md
View file @
baf2115a
...
@@ -203,7 +203,7 @@ for more details.
...
@@ -203,7 +203,7 @@ for more details.
If you're working with floating point numbers, you may want to use the floating
If you're working with floating point numbers, you may want to use the floating
point variations of some of these macros in order to avoid problems caused by
point variations of some of these macros in order to avoid problems caused by
rounding. See
[
Advanced googletest Topics
](
advanced
)
for details.
rounding. See
[
Advanced googletest Topics
](
advanced
.md
)
for details.
Macros in this section work with both narrow and wide string objects (
`string`
Macros in this section work with both narrow and wide string objects (
`string`
and
`wstring`
).
and
`wstring`
).
...
@@ -222,15 +222,15 @@ two `string` objects, use `EXPECT_EQ`, `EXPECT_NE`, and etc instead.
...
@@ -222,15 +222,15 @@ 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, | `
EXPECT_STREQ(str1, | the two C strings have |
:
str2);
`
:
str2);`
:
the same content
:
|
str2);
`
|
str2);`
|
the same content
|
|
`ASSERT_STRNE(str1, | `
EXPECT_STRNE(str1, | the two C strings have |
|
`ASSERT_STRNE(str1, | `
EXPECT_STRNE(str1, | the two C strings have |
:
str2);
`
:
str2);`
:
different contents
:
|
str2);
`
|
str2);`
|
different contents
|
|
`ASSERT_STRCASEEQ(str1, | `
EXPECT_STRCASEEQ(str1, | the two C strings have |
|
`ASSERT_STRCASEEQ(str1, | `
EXPECT_STRCASEEQ(str1, | the two C strings have |
:
str2);
`
:
str2);`
:
the same content,
:
|
str2);
`
|
str2);`
|
the same content,
|
:
:
:
ignoring case
:
|
|
|
ignoring case
|
|
`ASSERT_STRCASENE(str1, | `
EXPECT_STRCASENE(str1, | the two C strings have |
|
`ASSERT_STRCASENE(str1, | `
EXPECT_STRCASENE(str1, | the two C strings have |
:
str2);
`
:
str2);`
:
different contents,
:
|
str2);
`
|
str2);`
|
different contents,
|
:
:
:
ignoring case
:
|
|
|
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