Searched defs:ADD_FAILURE (Results 1 - 10 of 10) sorted by relevance
/external/chromium/sdch/open-vcdiff/src/gtest/ |
H A D | gtest.h | 105 // explicit SUCCEED(), FAIL(), or ADD_FAILURE()). 904 // ADD_FAILURE unconditionally adds a failure to the current test. 910 // it behaves like ADD_FAILURE. In particular: 915 // FAIL and ASSERT_* are similar to ADD_FAILURE and EXPECT_*, except 918 // writing data-driven tests often find themselves using ADD_FAILURE 928 #define ADD_FAILURE() GTEST_NONFATAL_FAILURE("Failed") macro
|
/external/chromium/testing/gtest/include/gtest/ |
H A D | gtest.h | 1708 // ADD_FAILURE unconditionally adds a failure to the current test. 1714 // it behaves like ADD_FAILURE. In particular: 1719 // FAIL and ASSERT_* are similar to ADD_FAILURE and EXPECT_*, except 1722 // writing data-driven tests often find themselves using ADD_FAILURE 1732 #define ADD_FAILURE() GTEST_NONFATAL_FAILURE_("Failed") macro
|
/external/chromium_org/testing/gtest/include/gtest/ |
H A D | gtest.h | 1788 // ADD_FAILURE unconditionally adds a failure to the current test. 1794 // it behaves like ADD_FAILURE. In particular: 1799 // FAIL and ASSERT_* are similar to ADD_FAILURE and EXPECT_*, except 1802 // writing data-driven tests often find themselves using ADD_FAILURE 1806 #define ADD_FAILURE() GTEST_NONFATAL_FAILURE_("Failed") macro
|
/external/chromium_org/third_party/mesa/src/src/gtest/include/gtest/ |
H A D | gtest.h | 1708 // ADD_FAILURE unconditionally adds a failure to the current test. 1714 // it behaves like ADD_FAILURE. In particular: 1719 // FAIL and ASSERT_* are similar to ADD_FAILURE and EXPECT_*, except 1722 // writing data-driven tests often find themselves using ADD_FAILURE 1732 #define ADD_FAILURE() GTEST_NONFATAL_FAILURE_("Failed") macro
|
/external/gtest/include/gtest/ |
H A D | gtest.h | 1708 // ADD_FAILURE unconditionally adds a failure to the current test. 1714 // it behaves like ADD_FAILURE. In particular: 1719 // FAIL and ASSERT_* are similar to ADD_FAILURE and EXPECT_*, except 1722 // writing data-driven tests often find themselves using ADD_FAILURE 1732 #define ADD_FAILURE() GTEST_NONFATAL_FAILURE_("Failed") macro
|
/external/llvm/utils/unittest/googletest/include/gtest/ |
H A D | gtest.h | 1710 // ADD_FAILURE unconditionally adds a failure to the current test. 1716 // it behaves like ADD_FAILURE. In particular: 1721 // FAIL and ASSERT_* are similar to ADD_FAILURE and EXPECT_*, except 1724 // writing data-driven tests often find themselves using ADD_FAILURE 1734 #define ADD_FAILURE() GTEST_NONFATAL_FAILURE_("Failed") macro
|
/external/mesa3d/src/gtest/include/gtest/ |
H A D | gtest.h | 1708 // ADD_FAILURE unconditionally adds a failure to the current test. 1714 // it behaves like ADD_FAILURE. In particular: 1719 // FAIL and ASSERT_* are similar to ADD_FAILURE and EXPECT_*, except 1722 // writing data-driven tests often find themselves using ADD_FAILURE 1732 #define ADD_FAILURE() GTEST_NONFATAL_FAILURE_("Failed") macro
|
/external/open-vcdiff/gtest/include/gtest/ |
H A D | gtest.h | 1634 // ADD_FAILURE unconditionally adds a failure to the current test. 1640 // it behaves like ADD_FAILURE. In particular: 1645 // FAIL and ASSERT_* are similar to ADD_FAILURE and EXPECT_*, except 1648 // writing data-driven tests often find themselves using ADD_FAILURE 1658 #define ADD_FAILURE() GTEST_NONFATAL_FAILURE_("Failed") macro
|
/external/protobuf/gtest/include/gtest/ |
H A D | gtest.h | 1552 // ADD_FAILURE unconditionally adds a failure to the current test. 1558 // it behaves like ADD_FAILURE. In particular: 1563 // FAIL and ASSERT_* are similar to ADD_FAILURE and EXPECT_*, except 1566 // writing data-driven tests often find themselves using ADD_FAILURE 1576 #define ADD_FAILURE() GTEST_NONFATAL_FAILURE_("Failed") macro
|
/external/libvpx/libvpx/third_party/googletest/src/include/gtest/ |
H A D | gtest.h | 17087 // assertion or an explicit FAIL(), ADD_FAILURE(), or SUCCESS()). 17093 // explicit SUCCEED(), FAIL(), or ADD_FAILURE()). 19258 // ADD_FAILURE unconditionally adds a failure to the current test. 19264 // it behaves like ADD_FAILURE. In particular: 19269 // FAIL and ASSERT_* are similar to ADD_FAILURE and EXPECT_*, except 19272 // writing data-driven tests often find themselves using ADD_FAILURE 19276 #define ADD_FAILURE() GTEST_NONFATAL_FAILURE_("Failed") macro
|
Completed in 408 milliseconds