| 1 | <HTML> |
|---|
| 2 | <HEAD> |
|---|
| 3 | <TITLE>Boost Test Library command line recommendations</TITLE> |
|---|
| 4 | <LINK rel="stylesheet" type="text/css" href="../style/btl.css" media="screen"> |
|---|
| 5 | <LINK rel="stylesheet" type="text/css" href="../style/btl-print.css" media="print"> |
|---|
| 6 | <META http-equiv="Content-Language" content="en-us"> |
|---|
| 7 | <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
|---|
| 8 | </HEAD> |
|---|
| 9 | <BODY> |
|---|
| 10 | <DIV class="header"> <A href="../index.html">Boost.Test</A> > <A href="recomendations.html"> Usage |
|---|
| 11 | recommendations </A> > <SPAN class="current_article">Command line</SPAN></DIV> |
|---|
| 12 | |
|---|
| 13 | <DIV class="body"> <IMG src='../btl1.gif' width='252' height='43' alt="Boost Test logo"> |
|---|
| 14 | <H1 class="subtitle"><SPAN class="first-line-indented">Command line </SPAN> usage |
|---|
| 15 | recommendations</H1> |
|---|
| 16 | <UL> |
|---|
| 17 | <LI><A href="#t1">If you got fatal exception somewhere within test case, make program |
|---|
| 18 | generate coredump by adding extra command line argument</A></LI> |
|---|
| 19 | <LI><A href="#t2">How to use test module build with Boost.Test framework under management |
|---|
| 20 | of automated regression test facilities?</A></LI> |
|---|
| 21 | </UL> |
|---|
| 22 | <H5>If you got fatal exception somewhere within test case, make program |
|---|
| 23 | generate coredump by adding extra command line argument<A name="t1"></A></H5> |
|---|
| 24 | <P class="first-line-indented">If you got "memory access violation" message |
|---|
| 25 | (or any other message indication fatal or system error) when you run you |
|---|
| 26 | test, to get more information of error location add --catch_system_errors=no |
|---|
| 27 | to the test run command line. Now run the test again and it |
|---|
| 28 | will create a coredump you could analyze using you preferable debugger. Or |
|---|
| 29 | run it under debugger in a first place and it will break at the point of |
|---|
| 30 | failure.</P> |
|---|
| 31 | <H5 class="first-line-indented">How to use test module build with Boost.Test |
|---|
| 32 | framework under management of automated regression test facilities?<A name="t2"></A></H5> |
|---|
| 33 | <P class="first-line-indented">My first recommendation is to make sure that |
|---|
| 34 | the test framework catches all fatal errors using catch_system_error=yes. |
|---|
| 35 | In other case test program may produce unwanted dialogs (depends on compiler |
|---|
| 36 | and OS) that will halt you regression tests run. Second suppress any results |
|---|
| 37 | reports using report_level=no and errors log using log_level=nothing, so |
|---|
| 38 | it wont produce undesirable output no one is going to look at anyway. I recommend |
|---|
| 39 | to rely only on result code that will be consistent for all test programs. |
|---|
| 40 | An alternative to my second recommendation is direct both log and report |
|---|
| 41 | to separate file you could analize later on. More over you could make Boost.Test |
|---|
| 42 | to produce them in XML format using output_format=XML and use some automated |
|---|
| 43 | tools that format this information as you like. </P> |
|---|
| 44 | </DIV> |
|---|
| 45 | <DIV class="footer"> |
|---|
| 46 | <DIV class="footer-body"> |
|---|
| 47 | <P> © <A name="Copyright">Copyright</A> <A href='mailto:boost-test at emailaccount dot com (please unobscure)'>Gennadiy |
|---|
| 48 | Rozental</A> 2001-2005. <BR> |
|---|
| 49 | Distributed under the Boost Software License, Version 1.0. |
|---|
| 50 | (See accompanying file <A href="../../../../LICENSE_1_0.txt">LICENSE_1_0.txt</A> or |
|---|
| 51 | copy at <A href="http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</A>)</P> |
|---|
| 52 | <P>Revised: |
|---|
| 53 | <!-- #BeginDate format:Sw1 -->24 May, 2004<!-- #EndDate --> |
|---|
| 54 | </P> |
|---|
| 55 | </DIV> |
|---|
| 56 | </DIV> |
|---|
| 57 | </BODY> |
|---|
| 58 | </HTML> |
|---|
