mirror of
https://github.com/boostorg/test.git
synced 2026-01-23 18:12:12 +00:00
59 lines
3.3 KiB
HTML
59 lines
3.3 KiB
HTML
<HTML>
|
|
<HEAD>
|
|
<TITLE>Boost Test Library msvc .net 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">MSVC .NET</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">Microsoft Visual Studio
|
|
.NET</SPAN> usage recommendations</H1>
|
|
<UL>
|
|
<LI><A href="#t1">Use custom build step to automatically start test program after compilation</A></LI>
|
|
<LI><A href="#t2">If you got fatal exception somewhere within test case, make debugger
|
|
break at the point the failure by adding extra command line argument</A></LI>
|
|
</UL>
|
|
<H5>Use custom build step to automatically start test program after compilation<A name="t1"></A></H5>
|
|
<P class="first-line-indented">I found it most convenient to put test program
|
|
execution as a post-build step in compilation. To do so use project property
|
|
page:</P>
|
|
<IMG src="imgs/post_build_event.jpg" alt="project property page" width="500" height="342">
|
|
<P class="first-line-indented">Full command you need in "Command Line" field
|
|
is: </P>
|
|
<P class="first-line-indented"><u>"$(TargetDir)\$(TargetName).exe" --result_code=no
|
|
--report_level=no</u></P>
|
|
<P class="first-line-indented">Note that both report level and result code
|
|
are suppressed. This way the only output you may see from this command are
|
|
possible runtime errors. But the best part is that you could jump through
|
|
these errors using usual keyboard shortcuts/mouse clicks you use for compilation
|
|
error annalists:</P>
|
|
<P><IMG src="imgs/post_build_out.jpg" width="800" height="354">
|
|
</P>
|
|
<H5>If you got fatal exception somewhere within test case, make debugger
|
|
break at the point the failure by adding extra command line argument<A name="t2"></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:</P>
|
|
<P class="first-line-indented"><IMG src="imgs/run_args.jpg" width="500" height="342"></P>
|
|
<P class="first-line-indented">Now run the test again under debugger and it will break at the point of failure. </P>
|
|
</DIV>
|
|
<DIV class="footer">
|
|
<DIV class="footer-body">
|
|
<P> © <A name="Copyright">Copyright</A> <A href="mailto:boost-test%20at%20emailaccount%20dot%20com%20%28please%20unobscure%29">Gennadiy
|
|
Rozental</A> 2001-2006. <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 -->25 Oct, 2005<!-- #EndDate -->
|
|
</P>
|
|
</DIV>
|
|
</DIV>
|
|
</BODY>
|
|
</HTML>
|