|
Boost Users : |
From: Ovanes Markarian (om_boost_at_[hidden])
Date: 2008-05-05 16:29:53
I just wanted to make a small addition to my post. Please see below.
On Mon, May 5, 2008 at 9:34 AM, Ovanes Markarian <om_boost_at_[hidden]>
wrote:
> Gennadiy,
>
> many thanks for your answer. Is there a doc, on how to do this or should I
> figure it out myself?
>
>
> With Kind Regards,
> Ovanes
>
>
>
> > I am not sure what prevents you from doing this. This should work
> > without problems. In fact if you really want you production code to
> > match your test one, you can build all you production code along with
> > all test cases into shared libraries and than use
> > boost_console_test_runner to execute the tests.
> >
> > Gennadiy
>
> Since our executables (total sum) are pretty big (around 2 gigs) we do not
want the unit test code to be compiled into the production code, since it
can easily increase the size. So my question was of the nature: Can I
somehow without writing own macros, use the Test Framework macros, which
will remove the entire test code from compilation unit or do I have to
enable / disable it via an own macro definitions a la:
#if defined PP_WITH_UNIT_TESTS
BOOST_AUTO_TEST_CASE(some_test) ...
#endif
And the other question is: can I make hierarchical test dependencies with
BOOST_AUTO_TEST_CASE. The problem is, it is not always a good idea run all
unit tests, because of timing aspects.
With Kind Regards,
Ovanes
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