Re: Boost.Test problems (Was: [boost] Multiple link definitions on Darwin tests)

From: Joel de Guzman (joel_at_[hidden])
Date: 2004-07-20 19:01:52

Martin Wille wrote:

> Vladimir Prus wrote:
> 
>> <RANT>
>>
>> I really, really don't understand why it's necessary to commit new 
>> staff at this point of release process. The file in question, 
>> boost/test/detail/xml_printer.hpp was added 2004-07-19, which is 
>> *yesterday*. Was there any pressing need for that? Should not 
>> Boost.Test be in complete feature freeze for a month already?!
>>
>> Of all Boost.Test functionality I use only 'test_main' and 
>> BOOST_CHECK, and I'd be really gratefull if that subset just worked. 
>> Just mine opinion, of course.
> 
> 
> Not only yours. A change to Boost.Test basically means all tests will
> have to be recompiled on the testing machines. This means test results
> will be available at a lower frequency. A higher frequency is very
> desirable during the release preparations.

I'm seriously considering not using Boost.Test in the next Spirit
release. IMO, it's more trouble than it's worth. It's not stable.
All we basically use is some form of assert. I do not think the
fancy stuff are needed at all. If you want stability, use the
plain old ASSERT.

Cheers,
-- 
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net