I just wanted to make a small addition to my post. Please see below.<br><br><div class="gmail_quote">On Mon, May 5, 2008 at 9:34 AM, Ovanes Markarian &lt;<a href="mailto:om_boost@keywallet.com">om_boost@keywallet.com</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Gennadiy,<br><br>many thanks for your answer. Is there a doc, on how to do this or should I figure it out myself?<br>
<br><br>With Kind Regards,<br><font color="#888888">Ovanes</font><div><div></div><div class="Wj3C7c"><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

<div><br>
</div>I am not sure what prevents you from doing this. This should work<br>
without problems. In fact if you really want you production code to<br>
match your test one, you can build all you production code along with<br>
all test cases into shared libraries and than use<br>
boost_console_test_runner to execute the tests.<br>
<br>
Gennadiy</blockquote></div></div></div></blockquote><div>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:<br>
<br>#if defined PP_WITH_UNIT_TESTS<br>&nbsp;&nbsp; BOOST_AUTO_TEST_CASE(some_test) ...<br>#endif<br></div></div><br><br>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.<br>
<br><br>With Kind Regards,<br>Ovanes<br>