16 Dec
2008
16 Dec
'08
9:44 p.m.
on Mon Dec 08 2008, "Dean Michael Berris" <mikhailberis-AT-gmail.com> 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.
Hi Mikhail, Since nobody has replied, would you open a Trac ticket? Otherwise, this important issue might get lost. Thanks, -- Dave Abrahams BoostPro Computing http://www.boostpro.com