Menu
While ASSERT_* macros cause termination of test case, EXPECT_* macros continue its evaluation. I would like to know which is the criteria to decide whether to use one or the other.
427
ASSERT: Fails fast, aborting the current function. EXPECT: Continues after the failure.
String Comparison If you want to compare two string objects, use EXPECT_EQ , EXPECT_NE , and etc instead. Note that "CASE" in an assertion name means that case is ignored. A NULL pointer and an empty string are considered different.
EXPECT_NO_THROW. EXPECT_NO_THROW( statement ) ASSERT_NO_THROW( statement ) Verifies that statement does not throw any exception.
Use ASSERT when the condition must hold - if it doesn't the test stops right there. Use this when the remainder of the test doesn't have semantic meaning without this condition holding.
Use EXPECT when the condition should hold, but in cases where it doesn't we can still get value out of continuing the test. (The test will still ultimately fail at the end, though.)
The rule of thumb is: use EXPECT by default, unless you require something to hold for the remainder of the tests, in which case you should use ASSERT for that particular condition.
This is echoed within the primer:
Usually
EXPECT_*are preferred, as they allow more than one failures to be reported in a test. However, you should useASSERT_*if it doesn't make sense to continue when the assertion in question fails.
156
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
