boost/build
2
0
Fork 0
mirror of https://github.com/boostorg/build.git synced 2026-02-10 11:22:12 +00:00
Code Issues Projects Releases Wiki Activity

Documenting testing.launcher

Browse Source 
[SVN r33067]
This commit is contained in:
Vladimir Prus
2006-02-21 14:42:42 +00:00
parent 00b6d9baf4
commit 876bcd067f
1 changed files with 18 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
doc/src/advanced.xml
View File

@@ -1585,6 +1585,24 @@ unit-test helpers_test : helpers_test.cpp helpers ;
can't miss a unit test failure.
</para>
<para>By default, the executable is run directly. Sometimes, it's
desirable to run the executable using some helper command. You should use the
<literal>testing.launcher</literal> property to specify the name of the
helper command. For example, if you write:
</para>
<programlisting>
unit-test helpers_test
: helpers_test.cpp helpers
: <emphasis role="bold">&lt;testing.launcher&gt;valgrind</emphasis>
;
</programlisting>
<para>The command used to run the executable will be:</para>
<screen>
<emphasis role="bold">valgrind</emphasis> bin/$toolset/debug/helpers_test
</screen>
<para>There are rules for more elaborate testing: <code>compile</code>,
<code>compile-fail</code>, <code>run</code> and
<code>run-fail</code>. They are more suitable for automated testing, and