From: Felipe Magno de Almeida (felipe.m.almeida_at_[hidden])
Date: 2006-02-01 14:49:17
On 1/31/06, Robert Ramey <ramey_at_[hidden]> wrote:
[snip]
> I envision a common situation - (In fact, at this very moment I'm stuck
> on another project and I find my self in this exact situation). I'm working
> on my next wizbang project and I'm under huge pressure to fix a bug.
> I've been working on it for days with no luck. Now I realize that its
> much deeper than I thought and that it could be anywhere. In desperation
> I look to boost and find Boost Test. The introduction shows me
> the joys of unit testing which I havn't been using. I'm really
> desperate and will try anything that only takes two hours to try.
> I down load boost headers. Copy the tutorial example from
> boost test an make a test for one mof my routines. 2 hours.
> Still havn't found my bug but since I still don't know what to do
> I repeat the processes for the rest of the program. The bug
> turns out to be pretty stupid and easy to spot - if I had only
> thought to look at the right place. I leave the boost test
> stuff in becuase now its "free". I've been kidnapped into
> the boost community in spite of myself.
>
> Contrast that the current situation. I look into boost test.
> Well reading the documents is a couple of hours. Then
> there is bjam and library building and linking. Right away
> I'm on to something else.
I just would like to let you know that the this case Robert puts is a
lot common.
I find myself wanting to use Boost.Test for some time already (like 6
months), but I'm just *not finding time to setup it*.
[snip]
-- Felipe Magno de Almeida