2.4 KiB
Assertion Macros
Most test frameworks have a large collection of assertion macros to capture all possible conditional forms (_EQUALS, _NOTEQUALS, _GREATER_THAN etc).
Catch is different. Because it decomposes natural C-style conditional expressions most of these forms are reduced to one or two that you will use all the time. That said there are a rich set of auxilliary macros as well. We'll describe all of these here.
Most of these macros come in two forms:
Natural Expressions
The REQUIRE family of macros tests an expression and aborts the test case if it fails. The CHECK family are equivalent but execution continues in the same test case even if the assertion fails. This is useful if you have a series of essentially orthoginal assertions and it is useful to see all the results rather than stopping at the first failure.
REQUIRE( expression ) and
CHECK( expression )
Evaluates the expression and records the result. If an exception is thrown it is caught, reported, and counted as a failure. These are the macros you will use most of the time
Examples:
CHECK( str == "string value" );
CHECK( thisReturnsTrue() );
REQUIRE( i == 42 );
REQUIRE_FALSE( expression ) and
CHECK_FALSE( expression )
Evaluates the expression and records the logical NOT of the result. If an exception is thrown it is caught, reported, and counted as a failure.
(these forms exist as a workaround for the fact that ! prefixed expressions cannot be decomposed).
Example:
REQUIRE_FALSE( thisReturnsFalse() );
Exceptions
REQUIRE_THROWS( expression ) and
CHECK_THROWS( expression )
Expects that an exception (of any type) is be thrown during evaluation of the expression.
REQUIRE_THROWS_AS( expression and exception type ) and
CHECK_THROWS_AS( expression, exception type )
Expects that an exception of the specified type is thrown during evaluation of the expression.
REQUIRE_NOTHROW( expression ) and
CHECK_NOTHROW( expression )
Expects that no exception is thrown during evaluation of the expression.
Matcher expressions
To support Matchers a slightly different form is used. Matchers will be more fully documented elsewhere. Note that Matchers are still at early stage development and are subject to change.
REQUIRE_THAT( lhs, matcher call ) and
CHECK_THAT( lhs, matcher call )