forked from boostorg/regression
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
72 lines (57 loc) · 2.8 KB
/
index.html
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
59
60
61
62
63
64
65
66
67
68
69
70
71
72
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Language" content="en-us" />
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<title>Regression Test Reporting Tools</title>
</head>
<body>
<h1>Regression Test Reporting Tools</h1>
<p>This repository is the home of tools used to run Boost's automated
regression testing and reporting, and tools that may (optionally) be used by
Boost developers to perform local regression test reporting.</p>
<p>Instructions
for running Boost's automated regression testing and reporting, and
reporting<br>
the results back to the Boost community are
<a href="http://www.boost.org/development/running_regression_tests.html">
available on the Boost web site</a>.</p>
<p>To build developers local test reporting tools, cd to the specific tool's
build directory, then invoke b2 like this:</p>
<blockquote>
<pre>b2 --boost-root=<b><i>path</i></b> --boost-build=<i><b>path</b></i>/build/src install</pre>
</blockquote>
<p>For example:</p>
<blockquote>
<pre>cd regression/library_status/build
b2 --boost-root=c:/boost --boost-build=c:/boost/tools/build/src install</pre>
</blockquote>
Absolute paths are currently required.<p>There are two developers local test
reporting tools, plus the <code>process_jam_log</code> tool that prepares data
for the reporting tools.</p>
<ul>
<li><a href="src/process_jam_log.cpp">process_jam_log.cpp</a> -
Processes the bjam outputs, creating a file named test_log.xml for each
test encountered.</li>
<li><a href="compiler_status/src/compiler_status.cpp">Compiler Status</a>
- Generates HTML status tables from test_log.xml and other files. Simpler
to use than Library Status, but less capable.</li>
<li><a href="library_status/doc/library_status.html">Library Status</a>
- Runs test programs for one or all boost libraries on your local
installation and generates complete tables to show which combinations of
libraries, compilers, compiler settings pass and fail at your local
installation. More capable than Compiler Status, but more complex to use.</li>
</ul>
<hr />
<p><font size="2">Revised:
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B %Y" startspan -->01 April 2015<!--webbot bot="Timestamp" endspan i-checksum="28342" --></font></p>
<p><font size="2">Copyright Beman Dawes 2003.</font></p>
<p><font size="2">Copyright Rene Rivera 2007, 2015.</font></p>
<p>
<font size="2">Distributed under the Boost Software License, Version 1.0. (See copy at <a
href="http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)
</font>
</p>
</body>
</html>