Boost logo

Boost-Commit :

Subject: [Boost-commit] svn:boost r67406 - website/public_html/beta/development
From: Jim_at_[hidden]
Date: 2010-12-21 18:55:58


Author: jimb
Date: 2010-12-21 18:55:55 EST (Tue, 21 Dec 2010)
New Revision: 67406
URL: http://svn.boost.org/trac/boost/changeset/67406

Log:
Added section describing running regression tests locally (via bjam), from list-serve discussion.
Text files modified:
   website/public_html/beta/development/running_regression_tests.html | 50 ++++++++++++++++++++++++++++++++++-----
   1 files changed, 43 insertions(+), 7 deletions(-)

Modified: website/public_html/beta/development/running_regression_tests.html
==============================================================================
--- website/public_html/beta/development/running_regression_tests.html (original)
+++ website/public_html/beta/development/running_regression_tests.html 2010-12-21 18:55:55 EST (Tue, 21 Dec 2010)
@@ -28,8 +28,44 @@
               <h1>Running Boost Regression Tests</h1>
             </div>
 
+ <div class="section-title">
+ <h2>Running Regression Tests Locally</h2>
+ </div>
+
+ <div class="section-title">
+ <p><strong><em>It's easy to run regression tests on your Boost
+ distribution.</em></strong></p>
+
+ <p>To run a library's regression tests, run Boost's <a href=
+ "/doc/tools/build/doc/html/jam/usage.html"><tt>bjam</tt></a>
+ utility from that library's
+ <tt>libs/<em>&lt;library&gt;</em>/test</tt> directory. To run a
+ single test, specify its name (as found in Jamfile.v2) on the
+ command line.</p>
+
+ <p>See the <a href=
+ "/doc/libs/release/more/getting_started/index.html">Getting
+ Started guide</a> for help building or downloading
+ <tt>bjam</tt> for your platform, and navigating your Boost
+ distribution.</p>
+
+ <p>To run every library's regression tests, run <tt>bjam</tt>
+ from Boost's <tt>/status</tt> directory.</p>
+
+ <p>To run Boost.Build's regression tests, run "<tt>python
+ test_all.py</tt>" from Boost's <tt>tools/build/v2/test</tt>
+ directory.</p>
+ </div>
+
+ <div class="section-title">
+ <h2>Running Boost's Automated Regression and Reporting</h2>
+ </div>
+
             <div class="section-body">
- <h2>Requirements</h2>
+ <p>This runs all regressions and reports the results back to
+ the Boost community.</p>
+
+ <h3>Requirements</h3>
 
               <ul>
                 <li>Python 2.3 or later.</li>
@@ -40,7 +76,7 @@
                 tested.</li>
               </ul>
 
- <h2>Step by step instructions</h2>
+ <h3>Step by step instructions</h3>
 
               <ol>
                 <li>Create a new directory for the branch you want to
@@ -77,7 +113,7 @@
 python run.py ... <strong>--proxy=http://www.someproxy.com:3128>
 </pre>
 
- <h2>Options</h2>
+ <h3>Options</h3>
               <pre>
 commands: cleanup, collect-logs, get-source, get-tools, patch, regression,
 setup, show-revision, test, test-boost-build, test-clean, test-process, test-
@@ -130,7 +166,7 @@
               "<code>--tag=branches/release</code>". Or substitute any Boost
               tree of your choice.</p>
 
- <h2>Details</h2>
+ <h3>Details</h3>
 
               <p>The regression run procedure will:</p>
 
@@ -160,7 +196,7 @@
               all submitted test runs and publish them at <a href=
               "testing.html#RegressionTesting">various locations</a>.</p>
 
- <h2>Advanced use</h2>
+ <h3>Advanced use</h3>
 
               <h3>Providing detailed information about your environment</h3>
 
@@ -225,13 +261,13 @@
               <tt>patch_boost</tt> script, and, if found, execute it after
               obtaining the Boost sources.</p>
 
- <h2>Feedback</h2>
+ <h3>Feedback</h3>
 
               <p>Please send all comments/suggestions regarding this document
               and the testing procedure itself to the <a href=
               "/community/groups.html#testing">Boost Testing list</a>.</p>
 
- <h2>Notes</h2>
+ <h3>Notes</h3>
 
               <p><a id="runnerid1" name="runnerid1">[1]</a> If you are
               running regressions interlacingly with a different set of


Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk