diff options
| author | Abseil Team <absl-team@google.com> | 2021-06-10 09:52:12 -0700 |
|---|---|---|
| committer | Dino Radaković <dinor@google.com> | 2021-06-11 10:42:17 -0700 |
| commit | b050d6c4b00f3d641f6da6d598199591944f2065 (patch) | |
| tree | 46257f9522b624a08709c139abd2378b42d5ad1b | |
| parent | 3c4b3a039ec7493721ca1336bf9c64b02a8c5e11 (diff) | |
| download | googletest-git-b050d6c4b00f3d641f6da6d598199591944f2065.tar.gz | |
Googletest export
Internal change
PiperOrigin-RevId: 378672633
| -rw-r--r-- | docs/primer.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/primer.md b/docs/primer.md index dc718b41..6d8fdf44 100644 --- a/docs/primer.md +++ b/docs/primer.md @@ -319,7 +319,7 @@ The above uses both `ASSERT_*` and `EXPECT_*` assertions. The rule of thumb is to use `EXPECT_*` when you want the test to continue to reveal more errors after the assertion failure, and use `ASSERT_*` when continuing after failure doesn't make sense. For example, the second assertion in the `Dequeue` test is -`ASSERT_NE(nullptr, n)`, as we need to dereference the pointer `n` later, which +`ASSERT_NE(n, nullptr)`, as we need to dereference the pointer `n` later, which would lead to a segfault when `n` is `NULL`. When these tests run, the following happens: |