cegonse/cest

Expects continue to be executed even if the first one fails

Closed this issue · 0 comments

I think most of the unit test frameworks stop test execution just after the first failure. Potentially, this could lead to some problems not being reported. For example, if there is a verifiation for not NULL, and that one fails, the following statements could lead to segfault, which would leave the user without error information:

int *value = NULL;

expect(value).toBeNotNull();
expect(*value).toBe(27);