Next: conditions assertion, Previous: conditions failure, Up: conditions [Contents][Index]
The expected failure exceptional–condition object–type is used by CCTests to signal an expected failure in a test function. We can instantiate this type and also derive new types from it. To catch this exceptional condition we can do:
cce_location_t L[1];
if (cce_location(L)) {
if (cctests_condition_is_expected_failure(cce_condition(L))) {
CCTESTS_PC(cctests_condition_expected_failure_t, C, cce_condition(L));
do_something_with(C);
}
cce_run_catch_handlers_final(L);
} else {
do_something(L);
cce_run_body_handlers(L);
}
Type of data structure representing the exceptional–condition descriptor. It has the following public fields:
cce_descriptor_t descriptorThe condition descriptor’s base values.
The parent of this type descriptor is the one referenced by cctests_descriptor_failure_ptr,
Signalling test failure.
Type of data structure representing the exceptional–condition object.
Set the parent of the descriptor referenced by D to the descriptor of the
exceptional–condition object–type cctests_condition_expected_failure_t.
Initialisation function for the condition object. This function is meant to be called from the
initialisation function of sub–types of cctests_condition_expected_failure_t.
Return true if C if of type cctests_condition_expected_failure_t; otherwise
return false.
To define a sub–type of cctests_condition_expected_failure_t we can copy the code in the files:
condition-expected-failure-subtype.c condition-expected-failure-subtype-headear.h condition-expected-failure-subtype-body.c
under the tests directory of the source distribution; the code defines a new
condition–object type my_condition_expected_failure_subtype_t.
Next: conditions assertion, Previous: conditions failure, Up: conditions [Contents][Index]
This document describes version 0.4.1-devel.1 of CCTests.