| -----Original Message----- | From: boost-bounces@lists.boost.org | [mailto:boost-bounces@lists.boost.org] On Behalf Of Gennadiy Rozental | Sent: 07 February 2006 16:43 | To: boost@lists.boost.org | Subject: [boost] [test] Test Execution monitor fate | While working on Boost.Test documentation update I've | realized that there is | no substantial reason anymore to keep this component around. | The Unit Test Framework work just as well and does not require any more effort. And I also think we could get rid of Test Tools as a separate library - so there is just ONE library, which could easily be supplied pre-built, and to which it is auto-linked. I feel strongly that this is the Right Thing To Do - it makes testing simple and uniform. One of the major barriers to using Boost.Test is complexity. Doing everything with one tool is much easier. Sine I don't have to change a lot of Boost testing code, I would say that ;-) But I am going to change all MY code. However there is plenty of time to make the changes, and they are not major. Paul -- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB Phone and SMS text +44 1539 561830, Mobile and SMS text +44 7714 330204 mailto: pbristow@hetp.u-net.com http://www.hetp.u-net.com/index.html http://www.hetp.u-net.com/Paul%20A%20Bristow%20info.html