Lines Matching full:assertions

81 When using GoogleTest, you start by writing *assertions*, which are statements
86 *Tests* use assertions to verify the tested code's behavior. If a test crashes
99 ## Assertions  section in GoogleTest Primer
101 GoogleTest assertions are macros that resemble function calls. You test a class
102 or function by making assertions about its behavior. When an assertion fails,
107 The assertions come in pairs that test the same thing but have different effects
122 the [`ASSERT_EQ` and `EXPECT_EQ`](reference/assertions.md#EXPECT_EQ) macros to
138 GoogleTest provides a collection of assertions for verifying the behavior of
141 much more. There are even assertions that enable you to verify more complex
142 states by providing custom predicates. For the complete list of assertions
143 provided by GoogleTest, see the [Assertions Reference](reference/assertions.md).
152     use the various GoogleTest assertions to check values.
153 3.  The test's result is determined by the assertions; if any assertion in the
320 The above uses both `ASSERT_*` and `EXPECT_*` assertions. The rule of thumb is
478     *unsafe* to use Google Test assertions from two threads concurrently on
480     the assertions are done in the main thread. If you want to help, you can