On 03/23/2010 08:10 PM, Trip Volpe wrote:
Trip Volpe Wrote:
...and if an assert fails in one test in a module, _all_ subsequent tests in
that module will be aborted, even though this makes no sense.
Actually I said this wrong. It's worse than that: after one assert failure,
_all_ further execution is aborted, meaning that even unit tests in _other_
modules will be prevented from running. And you can't change this behavior,
even if you override the assert failure handler, since for some reason the
compiler expects the handler to throw an AssertError, and if it doesn't, a
segfault may result.
The solution to this would be not to use asserts in unittests.
