7 will show you more assertions as well as how to construct complex failure
11 ## More Assertions
14 assertions.
18 See [Explicit Success and Failure](reference/assertions.md#success-failure) in
19 the Assertions Reference.
21 ### Exception Assertions  argument
23 See [Exception Assertions](reference/assertions.md#exceptions) in the Assertions
26 ### Predicate Assertions for Better Error Messages  argument
28 Even though GoogleTest has a rich set of assertions, they can never be complete,
45 [`EXPECT_PRED*`](reference/assertions.md#EXPECT_PRED) in the Assertions
76 To provide more readable messages in Boolean assertions (e.g. `EXPECT_TRUE()`),
114 (one third of Boolean assertions in the Google code base are negative ones), and
138 [`EXPECT_PRED*`](reference/assertions.md#EXPECT_PRED) and
139 [`EXPECT_TRUE`](reference/assertions.md#EXPECT_TRUE) unsatisfactory, or some
141 instead use *predicate-formatter assertions* to *fully* customize how the
143 [`EXPECT_PRED_FORMAT*`](reference/assertions.md#EXPECT_PRED_FORMAT) in the
144 Assertions Reference for details.
148 See [Floating-Point Comparison](reference/assertions.md#floating-point) in the
149 Assertions Reference.
156 [`EXPECT_PRED_FORMAT2`](reference/assertions.md#EXPECT_PRED_FORMAT), for
172 See [`EXPECT_THAT`](reference/assertions.md#EXPECT_THAT) in the Assertions
175 ### More String Assertions  argument
181 with [`EXPECT_THAT`](reference/assertions.md#EXPECT_THAT) to do more string
193 ### Windows HRESULT assertions
195 See [Windows HRESULT Assertions](reference/assertions.md#HRESULT) in the
196 Assertions Reference.
198 ### Type Assertions  argument
240 You can use assertions in any C++ function. In particular, it doesn't have to be
241 a method of the test fixture class. The one constraint is that assertions that
249 If you need to use fatal assertions in a function that returns non-void, one
256 If changing the function's type is not an option, you should just use assertions
262 assertions in them; you'll get a compilation error if you try. Instead, either
277 Related to the assertions `SUCCEED()` and `FAIL()`, you can prevent further test
410 In many applications, there are assertions that can cause application failure if
425 code, see [Exception Assertions](#ExceptionAssertions).
433 [Death Assertions](reference/assertions.md#death) in the Assertions Reference
465 The test function body may contain other assertions and statements as well, if
477 will **not** cause the death test to fail, as GoogleTest assertions don't abort
553 See [Death Assertions](reference/assertions.md#death) in the Assertions
632 Due to an implementation detail, you cannot place multiple death test assertions
640 ## Using Assertions in Sub-routines
643 Note: If you want to put a series of test assertions in a subroutine to check
649 ### Adding Traces to Assertions
753 either exceptions, the `(ASSERT|EXPECT)_NO_FATAL_FAILURE` assertions or the
793 the result of this type of assertions. If `statement` creates new threads,
807 Assertions from multiple threads are currently not supported on Windows.
1572 NOTE: Assertions from multiple threads are currently not supported on Windows.