From 876bcd067fcdff14407df2061ae4871743fa5abd Mon Sep 17 00:00:00 2001
From: Vladimir Prus <ghost@cs.msu.su>
Date: Tue, 21 Feb 2006 14:42:42 +0000
Subject: [PATCH] Documenting testing.launcher

[SVN r33067]
---
 doc/src/advanced.xml | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/doc/src/advanced.xml b/doc/src/advanced.xml
index 7334136d4..5e3c18a7b 100644
--- a/doc/src/advanced.xml
+++ b/doc/src/advanced.xml
@@ -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