> > Basically, it's possible to create your own assert handler. > > I did not have time to look over the test framework, but with some help from > > you, when the library is ready, I can provide such a (handler) function. > > Or from someone who understands the test library internals - I took a look > at the BOOST_CHECK macros before writing the below, and couldn't find the > function that does the actual work.
Ok. Will ask, when time comes ;-) Best, John > > Darren > > P.S. I won't be able to do anything in the next three weeks, but if no-one > has taken up the challenge I'll have another go then. > > > > John Torjo wrote: > > > >>>>>Following on from that, there seems some overlap between your proposed > >>>>>asserts and Boost.Test's BOOST_CHECK_() macros. I wonder if it would be > >>>>>possible to have an assert handler for use in the unit test framework, > >>>>>and > >>>>>then I can use SMART_ASSERT() in both main code and in test code and > >>>>>only have to learn one syntax. > >>> > >>>Indeed you can! Take a look at the things I've developed so far. > >> > >>I didn't see anything specifically for this (i.e. something that updates > > > > the > > > >>number of failed/passed tests, and doesn't prompt the user). > >> > > > > > > > > Best, > > John > > > > > > _______________________________________________ > > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost > > > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost > _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
