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