Add {ASSERT,EXPECT}_DCHECK macros for tests

net/test/gtest_util.h

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 //
 // Testing utilities that extend gtest.
 
 #ifndef NET_TEST_GTEST_UTIL_H_
 #define NET_TEST_GTEST_UTIL_H_
 
 #include "base/test/mock_log.h"
@@ skipping 20 matching lines @@
 // Usage: EXPECT_THAT(foo(), IsOk());
 MATCHER(IsOk,
         std::string(negation ? "not " : "") + net::ErrorToString(net::OK)) {
   if (arg <= 0)
     *result_listener << net::ErrorToString(arg);
   return arg == net::OK;
 }
 
 // Internal implementation for the EXPECT_DFATAL and ASSERT_DFATAL
 // macros.  Do not use this directly.
-#define GTEST_DFATAL_(statement, matcher, fail)                        \
-  GTEST_AMBIGUOUS_ELSE_BLOCKER_                                        \
-  if (true) {                                                          \
-    ::base::test::MockLog gtest_log;                                   \
-    ::net::test::ScopedDisableExitOnDFatal gtest_disable_exit;         \
-    using ::testing::_;                                                \
-    EXPECT_CALL(gtest_log, Log(_, _, _, _, _))                         \
-        .WillRepeatedly(::testing::Return(false));                     \
-    EXPECT_CALL(gtest_log, Log(logging::LOG_DFATAL, _, _, _, matcher)) \
-        .Times(::testing::AtLeast(1))                                  \
-        .WillOnce(::testing::Return(false));                           \
-    gtest_log.StartCapturingLogs();                                    \
-    { statement; }                                                     \
-    gtest_log.StopCapturingLogs();                                     \
-    if (!testing::Mock::VerifyAndClear(&gtest_log)) {                  \
-      goto GTEST_CONCAT_TOKEN_(gtest_label_dfatal_, __LINE__);         \
-    }                                                                  \
-  } else                                                               \
+#define GTEST_DFATAL_(statement, severity, matcher, fail)                    \
+  GTEST_AMBIGUOUS_ELSE_BLOCKER_                                              \
+  if (true) {                                                                \
+    ::base::test::MockLog gtest_log;                                         \
+    ::net::test::ScopedDisableExitOnDFatal gtest_disable_exit;               \
+    using ::testing::_;                                                      \
+    EXPECT_CALL(gtest_log, Log(_, _, _, _, _))                               \
+        .WillRepeatedly(::testing::Return(false));                           \
+    EXPECT_CALL(gtest_log, Log(::logging::LOG_##severity, _, _, _, matcher)) \
+        .Times(::testing::AtLeast(1))                                        \
+        .WillOnce(::testing::Return(false));                                 \
+    gtest_log.StartCapturingLogs();                                          \
+    { statement; }                                                           \
+    gtest_log.StopCapturingLogs();                                           \
+    if (!testing::Mock::VerifyAndClear(&gtest_log)) {                        \
+      goto GTEST_CONCAT_TOKEN_(gtest_label_dfatal_, __LINE__);               \
+    }                                                                        \
+  } else                                                                     \
   GTEST_CONCAT_TOKEN_(gtest_label_dfatal_, __LINE__) : fail("")
 
 // The EXPECT_DFATAL and ASSERT_DFATAL macros are lightweight
 // alternatives to EXPECT_DEBUG_DEATH and ASSERT_DEBUG_DEATH. They
 // are appropriate for testing that your code logs a message at the
 // DFATAL level.
 //
 // Unlike EXPECT_DEBUG_DEATH and ASSERT_DEBUG_DEATH, these macros
 // execute the given statement in the current process, not a forked
 // one.  This works because we disable exiting the program for
 // LOG(DFATAL).  This makes the tests run more quickly.
 //
 // The _WITH() variants allow one to specify any matcher for the
 // DFATAL log message, whereas the other variants assume a regex.
 
 #define EXPECT_DFATAL_WITH(statement, matcher) \
-  GTEST_DFATAL_(statement, matcher, GTEST_NONFATAL_FAILURE_)
+  GTEST_DFATAL_(statement, DFATAL, matcher, GTEST_NONFATAL_FAILURE_)
 
 #define ASSERT_DFATAL_WITH(statement, matcher) \
-  GTEST_DFATAL_(statement, matcher, GTEST_FATAL_FAILURE_)
+  GTEST_DFATAL_(statement, DFATAL, matcher, GTEST_FATAL_FAILURE_)
 
 #define EXPECT_DFATAL(statement, regex) \
   EXPECT_DFATAL_WITH(statement, ::testing::ContainsRegex(regex))
 
 #define ASSERT_DFATAL(statement, regex) \
   ASSERT_DFATAL_WITH(statement, ::testing::ContainsRegex(regex))
 
 // The EXPECT_DEBUG_DFATAL and ASSERT_DEBUG_DFATAL macros are similar to
 // EXPECT_DFATAL and ASSERT_DFATAL. Use them in conjunction with DLOG(DFATAL)
 // or similar macros that produce no-op in opt build and DFATAL in dbg build.
@@ skipping 17 matching lines @@
 #define ASSERT_DEBUG_DFATAL(statement, regex) \
   GTEST_AMBIGUOUS_ELSE_BLOCKER_               \
   if (true) {                                 \
     (void)(regex);                            \
     statement;                                \
   } else                                      \
     GTEST_NONFATAL_FAILURE_("")
 
 #endif  // NDEBUG
 
+// The EXPECT_DCHECK and ASSERT_DCHECK macros are similar to EXPECT_DFATAL and
+// ASSERT_DFATAL. Use them in conjunction with DCHECK that produces no-op in opt
+// build and LOG_DCHECK (FATAL) if DCHECK_IS_ON().
+
+#if DCHECK_IS_ON()
+
+#define EXPECT_DCHECK(statement, regex)                             \
+  GTEST_DFATAL_(statement, DCHECK, ::testing::ContainsRegex(regex), \
+                GTEST_NONFATAL_FAILURE_)
+#define ASSERT_DCHECK(statement, regex)                             \
+  GTEST_DFATAL_(statement, DCHECK, ::testing::ContainsRegex(regex), \
+                GTEST_FATAL_FAILURE_)
+
+#else  // DCHECK_IS_ON()
+
+#define EXPECT_DCHECK(statement, regex) \
+  GTEST_AMBIGUOUS_ELSE_BLOCKER_         \
+  if (true) {                           \

[Paweł Hajdan Jr., 2016/08/05 14:35:07]

Could you explain more this weird "if (true)" code? Is it already present
anywhere else?

[johnme, 2016/08/05 16:57:37]

I copy-pasted from EXPECT_DEBUG_DFATAL and ASSERT_DEBUG_DFATAL above. The
intention is to run |statement|, whilst preventing |regex| being considered
unused. The if (true) { ... } else is just a macro wrapper
(http://stackoverflow.com/questions/154136).

But I agree that it's problematic:
- it's unnecessarily complicated/confusing
- GTEST_AMBIGUOUS_ELSE_BLOCKER_ (to avoid a "dangling else") is documented as
being for use internal to gtest only
- it's unclear why there's an unreachable GTEST_NONFATAL_FAILURE_("") at the end

So I've updated both these and the ones above to use a more typical do { ... }
while(false) macro wrapper (which is more common in chrome).

+    (void)(regex);                      \
+    statement;                          \
+  } else                                \
+  GTEST_NONFATAL_FAILURE_("")
+#define ASSERT_DCHECK(statement, regex) \
+  GTEST_AMBIGUOUS_ELSE_BLOCKER_         \
+  if (true) {                           \
+    (void)(regex);                      \
+    statement;                          \
+  } else                                \
+  GTEST_NONFATAL_FAILURE_("")
+
+#endif  // DCHECK_IS_ON()
+
 }  // namespace test
 }  // namespace net
 
 #endif  // NET_TEST_GTEST_UTIL_H_