
19 Dec
2008
19 Dec
'08
12:47 a.m.
Dean Michael Berris wrote:
I'm using Boost 1.35 and I notice that when a unit test aborts due to asserts in the code, it doesn't count as a failure -- the end report says "*** No errors detected" when in fact a call to abort() was made due to a failed assert.
I'm thinking this would be a bug, but I'd like to ask first whether this is intended behavior before thinking it's a bug with Boost.Test.
I believe this was fixed in 1.36.0 Gennadiy