
9 Dec
2008
9 Dec
'08
3:20 a.m.
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. Have a good day! -- Dean Michael C. Berris Software Engineer, Friendster, Inc.