On Mon, 24 Oct 2011 22:08:50 +0200, Jonathan M Davis <[email protected]>
wrote:
On Monday, October 24, 2011 11:23 Andrej Mitrovic wrote:
I'm not sure why it just stops after the first failing unittest
though. What is the point of that 'failed' counter?
It's a long standing issue that when one unit test fails within a
module, no
more within that module are run (though fortunately, a while back it was
fixed
so that other modules' unit tests will still run). As I recall, there
had to
be a change to the compiler to fix it, but I don't known/remember the
details.
Certainly, the issue still stands.
- Jonathan M Davis
It's also annoying that the runtime quits with a non-zero exit code
when you return false from your unit tester.
Somehow the boolean return became a flag for fail/success rather than for
program continuation.
martin
