|
Boost Users : |
From: Gennadiy Rozental (gennadiy.rozental_at_[hidden])
Date: 2006-07-29 12:33:39
"Jörg Becker" <becker_at_[hidden]> wrote in message
news:200607281836.13971.becker_at_flexis.de...
> On Friday, 28. July 2006 16:25, Gennadiy Rozental wrote:
>> Latest cvs version of Boost.
>> Test doesn't make any separation in
>> auto/non-auto unit test framework. You could use init_unit_test to
>> perform
>> any kind of initialization you need including call to
>> register_exception_translater.
> Using the init_unit_test was what I tried first, but this give me
> a 'redefinition' compile error, because the auto unit test framework
> provides
> this function.
This will work with cvs sources.
>
>> Also I believe you could employ global
>> fixture feature.
> Is this new in 1.34? I cannot find it in the 1.33 docu. I think this is
> very
I think so.
> similiar to my dummy test trick, but much nicer. The problem in both cases
> is
> how to get the unit_test_monitor or execution_monitor which are running my
> auto tests. In boost 1.31 I could simpy call
> register_exception_translator<>() but in 1.33 I have to call
> unit_test_monitor.register_exception_translator<>().
Sounds about right.
> Joerg
Gennaidy
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net