|
|
Boost-Commit : |
Subject: [Boost-commit] svn:boost r62776 - in trunk/libs/test/doc/html: . execution-monitor prg-exec-monitor tutorials utf utf/compilation utf/testing-tools utf/usage-recommendations utf/user-guide utf/user-guide/fixture utf/user-guide/runtime-config utf/user-guide/test-organization utf/user-guide/test-output utf/user-guide/usage-variants
From: steven_at_[hidden]
Date: 2010-06-10 18:57:09
Author: steven_watanabe
Date: 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
New Revision: 62776
URL: http://svn.boost.org/trac/boost/changeset/62776
Log:
Update the generated documentation for Boost.Test
Added:
trunk/libs/test/doc/html/utf/user-guide/test-output/FPT.html (contents, props changed)
Text files modified:
trunk/libs/test/doc/html/aknowledgements.html | 10
trunk/libs/test/doc/html/execution-monitor.html | 20 +-
trunk/libs/test/doc/html/execution-monitor/compilation.html | 22 +-
trunk/libs/test/doc/html/execution-monitor/reference.html | 185 +++++++++++++++------------
trunk/libs/test/doc/html/execution-monitor/user-guide.html | 48 +++---
trunk/libs/test/doc/html/faq.html | 49 +++---
trunk/libs/test/doc/html/index.html | 24 +--
trunk/libs/test/doc/html/intro.html | 26 ++-
trunk/libs/test/doc/html/minimal.html | 36 ++--
trunk/libs/test/doc/html/open-issues.html | 38 ++--
trunk/libs/test/doc/html/prg-exec-monitor.html | 62 ++++----
trunk/libs/test/doc/html/prg-exec-monitor/compilation.html | 36 ++--
trunk/libs/test/doc/html/prg-exec-monitor/impl.html | 20 +-
trunk/libs/test/doc/html/tutorials/hello-the-testing-world.html | 24 +-
trunk/libs/test/doc/html/tutorials/intro-in-testing.html | 18 +-
trunk/libs/test/doc/html/tutorials/new-year-resolution.html | 26 +-
trunk/libs/test/doc/html/utf.html | 18 +-
trunk/libs/test/doc/html/utf/compilation.html | 64 ++++----
trunk/libs/test/doc/html/utf/compilation/auto-linking.html | 8
trunk/libs/test/doc/html/utf/compilation/direct-include.html | 8
trunk/libs/test/doc/html/utf/compilation/standalone.html | 20 +-
trunk/libs/test/doc/html/utf/intro.html | 54 ++++----
trunk/libs/test/doc/html/utf/testing-tools.html | 40 +++---
trunk/libs/test/doc/html/utf/testing-tools/custom-predicate.html | 22 +-
trunk/libs/test/doc/html/utf/testing-tools/floating_point_comparison.html | 76 +++++-----
trunk/libs/test/doc/html/utf/testing-tools/output-test.html | 41 +++--
trunk/libs/test/doc/html/utf/testing-tools/reference.html | 261 ++++++++++++++++++++-------------------
trunk/libs/test/doc/html/utf/tutorials.html | 16 +-
trunk/libs/test/doc/html/utf/usage-recommendations.html | 14 +-
trunk/libs/test/doc/html/utf/usage-recommendations/command-line-specific.html | 21 +-
trunk/libs/test/doc/html/utf/usage-recommendations/dot-net-specific.html | 21 +-
trunk/libs/test/doc/html/utf/usage-recommendations/generic.html | 33 ++--
trunk/libs/test/doc/html/utf/user-guide.html | 74 +++++-----
trunk/libs/test/doc/html/utf/user-guide/fixture.html | 36 ++--
trunk/libs/test/doc/html/utf/user-guide/fixture/global.html | 34 ++--
trunk/libs/test/doc/html/utf/user-guide/fixture/model.html | 12
trunk/libs/test/doc/html/utf/user-guide/fixture/per-test-case.html | 16 +-
trunk/libs/test/doc/html/utf/user-guide/fixture/test-suite-shared.html | 16 +-
trunk/libs/test/doc/html/utf/user-guide/initialization.html | 32 ++--
trunk/libs/test/doc/html/utf/user-guide/runtime-config.html | 12
trunk/libs/test/doc/html/utf/user-guide/runtime-config/reference.html | 80 ++++++------
trunk/libs/test/doc/html/utf/user-guide/runtime-config/run-by-name.html | 50 +++---
trunk/libs/test/doc/html/utf/user-guide/test-organization.html | 36 ++--
trunk/libs/test/doc/html/utf/user-guide/test-organization/auto-nullary-test-case.html | 16 +-
trunk/libs/test/doc/html/utf/user-guide/test-organization/auto-test-case-template.html | 15 +-
trunk/libs/test/doc/html/utf/user-guide/test-organization/auto-test-suite.html | 20 +-
trunk/libs/test/doc/html/utf/user-guide/test-organization/expected-failures.html | 28 ++--
trunk/libs/test/doc/html/utf/user-guide/test-organization/manual-nullary-test-case.html | 40 +++---
trunk/libs/test/doc/html/utf/user-guide/test-organization/manual-test-case-template.html | 23 +-
trunk/libs/test/doc/html/utf/user-guide/test-organization/manual-test-suite.html | 14 +-
trunk/libs/test/doc/html/utf/user-guide/test-organization/master-test-suite.html | 30 ++--
trunk/libs/test/doc/html/utf/user-guide/test-organization/nullary-test-case.html | 18 +-
trunk/libs/test/doc/html/utf/user-guide/test-organization/test-case-template.html | 16 +-
trunk/libs/test/doc/html/utf/user-guide/test-organization/test-suite.html | 20 +-
trunk/libs/test/doc/html/utf/user-guide/test-organization/unary-test-case.html | 22 +-
trunk/libs/test/doc/html/utf/user-guide/test-output.html | 46 +++---
trunk/libs/test/doc/html/utf/user-guide/test-output/BOOST_TEST_CHECKPOINT.html | 14 +-
trunk/libs/test/doc/html/utf/user-guide/test-output/BOOST_TEST_MESSAGE.html | 14 +-
trunk/libs/test/doc/html/utf/user-guide/test-output/BOOST_TEST_PASSPOINT.html | 98 ++++++++------
trunk/libs/test/doc/html/utf/user-guide/test-output/log-ct-config.html | 34 ++--
trunk/libs/test/doc/html/utf/user-guide/test-output/log-hr-format.html | 56 ++++----
trunk/libs/test/doc/html/utf/user-guide/test-output/log-xml-format.html | 8
trunk/libs/test/doc/html/utf/user-guide/test-output/results-report.html | 22 +-
trunk/libs/test/doc/html/utf/user-guide/test-output/test-log.html | 90 ++++++------
trunk/libs/test/doc/html/utf/user-guide/test-output/test-progress.html | 22 +-
trunk/libs/test/doc/html/utf/user-guide/test-runners.html | 28 ++--
trunk/libs/test/doc/html/utf/user-guide/usage-variants.html | 22 +-
trunk/libs/test/doc/html/utf/user-guide/usage-variants/dynamic-lib-variant.html | 10
trunk/libs/test/doc/html/utf/user-guide/usage-variants/extern-test-runner-variant.html | 12
trunk/libs/test/doc/html/utf/user-guide/usage-variants/extern-test-runner.html | 14 +-
trunk/libs/test/doc/html/utf/user-guide/usage-variants/single-header-variant.html | 10
trunk/libs/test/doc/html/utf/user-guide/usage-variants/static-lib-variant.html | 12
72 files changed, 1291 insertions(+), 1242 deletions(-)
Modified: trunk/libs/test/doc/html/aknowledgements.html
==============================================================================
--- trunk/libs/test/doc/html/aknowledgements.html (original)
+++ trunk/libs/test/doc/html/aknowledgements.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Acknowledgements</title>
<link rel="stylesheet" href="../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="index.html" title="Boost Test Library">
<link rel="up" href="intro.html" title="Introduction">
<link rel="prev" href="open-issues.html" title="Open issues">
-<link rel="next" href="execution-monitor.html" title="Part I. Boost Test Library: The Execution Monitor">
+<link rel="next" href="execution-monitor.html" title="Boost Test Library: The Execution Monitor">
<script language="JavaScript1.2" src="../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,7 +22,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="btl.aknowledgements"></a>Acknowledgements</h3></div></div></div>
<p>Original Test Library:</p>
@@ -41,7 +41,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/execution-monitor.html
==============================================================================
--- trunk/libs/test/doc/html/execution-monitor.html (original)
+++ trunk/libs/test/doc/html/execution-monitor.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Part I. Boost Test Library: The Execution Monitor</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Boost Test Library: The Execution Monitor</title>
<link rel="stylesheet" href="../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="index.html" title="Boost Test Library">
<link rel="up" href="index.html" title="Boost Test Library">
<link rel="prev" href="aknowledgements.html" title="Acknowledgements">
@@ -22,9 +22,9 @@
</div></td>
</tr></table>
<hr>
-<div class="part" lang="en">
-<div class="titlepage"><div><div><h1 class="title">
-<a name="execution-monitor"></a>Part I. Boost Test Library: The Execution Monitor</h1></div></div></div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="execution-monitor"></a>Boost Test Library: The Execution Monitor</h2></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
@@ -33,7 +33,7 @@
<dt>Reference</dt>
</dl>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title"><a name="execution-monitor.intro"></a></h3></div></div></div>
<p class="first-line-indented">
Sometimes we need to call a function and make sure that no user or system originated exceptions are being thrown
@@ -48,9 +48,9 @@
</p>
<p class="first-line-indented">
The Execution Monitor usage is demonstrated in the example exec_mon_example . Additional examples are
- in <a class="xref" href="prg-exec-monitor.html" title="Part II. Boost Test Library: The Program Execution Monitor">Part II, “The Program Execution Monitor”</a> or <a class="xref" href="utf.html" title="Part IV. Boost Test Library: The Unit Test Framework">Part IV, “The Unit Test Framework”</a>.
+ in <a class="xref" href="prg-exec-monitor.html" title="Boost Test Library: The Program Execution Monitor">the section called “The Program Execution Monitor”</a> or <a class="xref" href="utf.html" title="Boost Test Library: The Unit Test Framework">the section called “The Unit Test Framework”</a>.
</p>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="execution-monitor.design"></a>Design Rationale</h4></div></div></div>
<p class="first-line-indented">
@@ -62,7 +62,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"><p><small>Last revised: , at </small></p></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/execution-monitor/compilation.html
==============================================================================
--- trunk/libs/test/doc/html/execution-monitor/compilation.html (original)
+++ trunk/libs/test/doc/html/execution-monitor/compilation.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>The Execution Monitor compilation variants and procedures</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
-<link rel="up" href="../execution-monitor.html" title="Part I. Boost Test Library: The Execution Monitor">
-<link rel="prev" href="../execution-monitor.html" title="Part I. Boost Test Library: The Execution Monitor">
+<link rel="up" href="../execution-monitor.html" title="Boost Test Library: The Execution Monitor">
+<link rel="prev" href="../execution-monitor.html" title="Boost Test Library: The Execution Monitor">
<link rel="next" href="user-guide.html" title="The Execution Monitor user's guide">
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
</head>
@@ -22,10 +22,10 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="execution-monitor.compilation"></a>The Execution Monitor compilation variants and procedures</h3></div></div></div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="execution-monitor.impl"></a>Implementation</h4></div></div></div>
<p class="first-line-indented">
@@ -41,7 +41,7 @@
</td>
</tr>
<tr>
-<td><p><span class="term">libs/test/execution_monitor.hpp</span></p></td>
+<td><p><span class="term">boost/test/impl/execution_monitor.ipp</span></p></td>
<td>
provides the Execution Monitor implementation for all supported configurations, including Microsoft structured
exception based, UNIX signals.
@@ -54,17 +54,17 @@
catch Microsoft C runtime debug events.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="execution-monitor.lib-compilation"></a>Standalone library compilation</h4></div></div></div>
<p class="first-line-indented">
To compile the Execution Monitor as standalone library compose it using only
- <code class="filename">execution-monitor.cpp</code> as a source file. Alternatively you can add this file directly to the
+ <code class="filename">execution_monitor.cpp</code> as a source file. Alternatively you can add this file directly to the
list of source files for your project. Boost Test Library's components include this file as a part of their
compilation procedure.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="execution-monitor.direct-include"></a>Direct include</h4></div></div></div>
<p class="first-line-indented">
@@ -76,7 +76,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/execution-monitor/reference.html
==============================================================================
--- trunk/libs/test/doc/html/execution-monitor/reference.html (original)
+++ trunk/libs/test/doc/html/execution-monitor/reference.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>The Execution Monitor reference</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
-<link rel="up" href="../execution-monitor.html" title="Part I. Boost Test Library: The Execution Monitor">
+<link rel="up" href="../execution-monitor.html" title="Boost Test Library: The Execution Monitor">
<link rel="prev" href="user-guide.html" title="The Execution Monitor user's guide">
-<link rel="next" href="../prg-exec-monitor.html" title="Part II. Boost Test Library: The Program Execution Monitor">
+<link rel="next" href="../prg-exec-monitor.html" title="Boost Test Library: The Program Execution Monitor">
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,19 +22,19 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="execution-monitor.reference"></a>The Execution Monitor reference</h3></div></div></div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="header.boost.test.execution_monitor.hpp"></a>Header <boost/test/execution_monitor.hpp></h4></div></div></div>
-<pre class="synopsis"><span class="bold"><strong>namespace</strong></span> boost {
- <span class="bold"><strong>class</strong></span> <a class="link" href="reference.html#boost.execution_monitor" title="Class execution_monitor">execution_monitor</a>;
- <span class="bold"><strong>class</strong></span> <a class="link" href="reference.html#boost.execution_exception" title="Class execution_exception">execution_exception</a>;
- <span class="bold"><strong>class</strong></span> <a class="link" href="reference.html#boost.execution_aborted" title="Class execution_aborted">execution_aborted</a>;
- <span class="bold"><strong>class</strong></span> <a class="link" href="reference.html#boost.system_error" title="Class system_error">system_error</a>;
-}</pre>
-<div class="refentry" lang="en">
+<a name="header.boost.test.execution_monitor_hpp"></a>Header <boost/test/execution_monitor.hpp></h4></div></div></div>
+<pre class="synopsis"><span class="keyword">namespace</span> <span class="identifier">boost</span> <span class="special">{</span>
+ <span class="keyword">class</span> <a class="link" href="reference.html#boost.execution_monitor" title="Class execution_monitor">execution_monitor</a><span class="special">;</span>
+ <span class="keyword">class</span> <a class="link" href="reference.html#boost.execution_exception" title="Class execution_exception">execution_exception</a><span class="special">;</span>
+ <span class="keyword">class</span> <a class="link" href="reference.html#boost.execution_aborted" title="Class execution_aborted">execution_aborted</a><span class="special">;</span>
+ <span class="keyword">class</span> <a class="link" href="reference.html#boost.system_error" title="Class system_error">system_error</a><span class="special">;</span>
+<span class="special">}</span></pre>
+<div class="refentry">
<a name="boost.execution_monitor"></a><div class="titlepage"></div>
<div class="refnamediv">
<h2><span class="refentrytitle">Class execution_monitor</span></h2>
@@ -44,34 +44,48 @@
</p>
</div>
<h2 xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv-title">Synopsis</h2>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv"><pre class="synopsis">
-<span class="bold"><strong>class</strong></span> <a class="link" href="reference.html#boost.execution_monitor" title="Class execution_monitor">execution_monitor</a> {
-<span class="bold"><strong>public</strong></span>:
+<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv"><pre class="synopsis"><span class="comment">// In header: <boost/test/execution_monitor.hpp>
+
+</span>
+<span class="keyword">class</span> <a class="link" href="reference.html#boost.execution_monitor" title="Class execution_monitor">execution_monitor</a> <span class="special">{</span>
+<span class="keyword">public</span><span class="special">:</span>
<span class="emphasis"><em>// <a class="link" href="reference.html#boost.execution_monitorconstruct-copy-destruct">construct/copy/destruct</a></em></span>
- <a class="link" href="reference.html#id270337-bb">execution_monitor</a>();
+ <a class="link" href="reference.html#id186105-bb"><span class="identifier">execution_monitor</span></a><span class="special">(</span><span class="special">)</span><span class="special">;</span>
- <span class="emphasis"><em>// <a class="link" href="reference.html#id270356-bb">execution</a></em></span>
- <span class="type"><span class="bold"><strong>int</strong></span></span> <a class="link" href="reference.html#id270361-bb">execute</a>(unit_test::callback0<<span class="bold"><strong>int</strong></span>> <span class="bold"><strong>const</strong></span>&);
+ <span class="emphasis"><em>// <a class="link" href="reference.html#id186122-bb">execution</a></em></span>
+ <span class="type"><span class="keyword">int</span></span> <a class="link" href="reference.html#id186126-bb"><span class="identifier">execute</span></a><span class="special">(</span>unit_test::callback0<span class="special"><</span><span class="keyword">int</span><span class="special">></span> <span class="keyword">const</span><span class="special">&</span><span class="special">)</span><span class="special">;</span>
- <span class="emphasis"><em>// <a class="link" href="reference.html#id270422-bb">registration</a></em></span>
- <span class="bold"><strong>template</strong></span><<span class="bold"><strong>typename</strong></span> Exception, <span class="bold"><strong>typename</strong></span> ExceptionTranslator>
- <span class="type"><span class="bold"><strong>void</strong></span></span> <a class="link" href="reference.html#id270427-bb">register_exception_translator</a>(ExceptionTranslator <span class="bold"><strong>const</strong></span>&,
- boost::type<Exception>* = 0);
- <span class="type">unit_test::readwrite_property<<span class="bold"><strong>bool</strong></span>></span> p_catch_system_errors;
- <span class="type">unit_test::readwrite_property<<span class="bold"><strong>bool</strong></span>></span> p_auto_start_dbg;
- <span class="type">unit_test::readwrite_property<<span class="bold"><strong>int</strong></span>></span> p_timeout;
- <span class="type">unit_test::readwrite_property<<span class="bold"><strong>int</strong></span>></span> p_use_alt_stack;
- <span class="type">unit_test::readwrite_property<<span class="bold"><strong>bool</strong></span>></span> p_detect_fp_exceptions;
-};</pre></div>
-<div class="refsect1" lang="en">
-<a name="id587156"></a><h2>Description</h2>
-<div class="refsect2" lang="en">
-<a name="id587160"></a><h3>
+ <span class="emphasis"><em>// <a class="link" href="reference.html#id236629-bb">registration</a></em></span>
+ <span class="keyword">template</span><span class="special"><</span><span class="keyword">typename</span> Exception<span class="special">,</span> <span class="keyword">typename</span> ExceptionTranslator<span class="special">></span>
+ <span class="type"><span class="keyword">void</span></span> <a class="link" href="reference.html#id236634-bb"><span class="identifier">register_exception_translator</span></a><span class="special">(</span><span class="identifier">ExceptionTranslator</span> <span class="keyword">const</span><span class="special">&</span><span class="special">,</span>
+ boost::type<span class="special"><</span><span class="identifier">Exception</span><span class="special">></span><span class="special">*</span> = 0<span class="special">)</span><span class="special">;</span>
+ <span class="type">unit_test::readwrite_property<span class="special"><</span><span class="keyword">bool</span><span class="special">></span></span> p_catch_system_errors<span class="special">;</span> <span class="comment">//
+ Specifies whether the monitor should try to catch system errors/exceptions that would cause program to crash in
+ regular case.
+ </span>
+ <span class="type">unit_test::readwrite_property<span class="special"><</span><span class="keyword">bool</span><span class="special">></span></span> p_auto_start_dbg<span class="special">;</span> <span class="comment">//
+ Specifies whether the monitor should try to attach debugger in case of caught system error.
+ </span>
+ <span class="type">unit_test::readwrite_property<span class="special"><</span><span class="keyword">int</span><span class="special">></span></span> p_timeout<span class="special">;</span> <span class="comment">//
+ Specifies the seconds that elapse before a timer_error occurs. May be ignored on some platforms.
+ </span>
+ <span class="type">unit_test::readwrite_property<span class="special"><</span><span class="keyword">int</span><span class="special">></span></span> p_use_alt_stack<span class="special">;</span> <span class="comment">//
+ Specifies whether the monitor should use alternative stack for the signal catching.
+ </span>
+ <span class="type">unit_test::readwrite_property<span class="special"><</span><span class="keyword">bool</span><span class="special">></span></span> p_detect_fp_exceptions<span class="special">;</span> <span class="comment">//
+ Specifies whether or not execution_monitor should install hardware traps for the floating
+ point exception.
+ </span>
+<span class="special">}</span><span class="special">;</span></pre></div>
+<div class="refsect1">
+<a name="id480044"></a><h2>Description</h2>
+<div class="refsect2">
+<a name="id480048"></a><h3>
<a name="boost.execution_monitorconstruct-copy-destruct"></a><code class="computeroutput">execution_monitor</code>
public
construct/copy/destruct</h3>
-<div class="orderedlist"><ol type="1"><li>
-<pre class="literallayout"><a name="id270337-bb"></a>execution_monitor();</pre>
+<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
+<pre class="literallayout"><a name="id186105-bb"></a><span class="identifier">execution_monitor</span><span class="special">(</span><span class="special">)</span><span class="special">;</span></pre>
<div class="variablelist"><table border="0">
<col align="left" valign="top">
<tbody>
@@ -87,11 +101,11 @@
</table></div>
</li></ol></div>
</div>
-<div class="refsect2" lang="en">
-<a name="id587233"></a><h3>
-<a name="id270356-bb"></a><code class="computeroutput">execution_monitor</code> execution</h3>
-<div class="orderedlist"><ol type="1"><li>
-<pre class="literallayout"><span class="type"><span class="bold"><strong>int</strong></span></span> <a name="id270361-bb"></a>execute(unit_test::callback0<<span class="bold"><strong>int</strong></span>> <span class="bold"><strong>const</strong></span>& F);</pre>
+<div class="refsect2">
+<a name="id480128"></a><h3>
+<a name="id186122-bb"></a><code class="computeroutput">execution_monitor</code> execution</h3>
+<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
+<pre class="literallayout"><span class="type"><span class="keyword">int</span></span> <a name="id186126-bb"></a><span class="identifier">execute</span><span class="special">(</span>unit_test::callback0<span class="special"><</span><span class="keyword">int</span><span class="special">></span> <span class="keyword">const</span><span class="special">&</span> F<span class="special">)</span><span class="special">;</span></pre>
<div class="variablelist"><table border="0">
<col align="left" valign="top">
<tbody>
@@ -124,14 +138,13 @@
</table></div>
</li></ol></div>
</div>
-<div class="refsect2" lang="en">
-<a name="id587350"></a><h3>
-<a name="id270422-bb"></a><code class="computeroutput">execution_monitor</code> registration</h3>
-<div class="orderedlist"><ol type="1"><li>
-<pre class="literallayout"><span class="bold"><strong>template</strong></span><<span class="bold"><strong>typename</strong></span> Exception, <span class="bold"><strong>typename</strong></span> ExceptionTranslator>
- <span class="type"><span class="bold"><strong>void</strong></span></span> <a name="id270427-bb"></a>register_exception_translator(ExceptionTranslator <span class="bold"><strong>const</strong></span>& tr,
- boost::type<Exception>* dummy = 0);</pre>
-<div class="variablelist"><table border="0">
+<div class="refsect2">
+<a name="id480264"></a><h3>
+<a name="id236629-bb"></a><code class="computeroutput">execution_monitor</code> registration</h3>
+<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
+<pre class="literallayout"><span class="keyword">template</span><span class="special"><</span><span class="keyword">typename</span> Exception<span class="special">,</span> <span class="keyword">typename</span> ExceptionTranslator<span class="special">></span>
+ <span class="type"><span class="keyword">void</span></span> <a name="id236634-bb"></a><span class="identifier">register_exception_translator</span><span class="special">(</span><span class="identifier">ExceptionTranslator</span> <span class="keyword">const</span><span class="special">&</span> tr<span class="special">,</span>
+ boost::type<span class="special"><</span><span class="identifier">Exception</span><span class="special">></span><span class="special">*</span> dummy = 0<span class="special">)</span><span class="special">;</span></pre>register custom (user supplied) exception translator<div class="variablelist"><table border="0">
<col align="left" valign="top">
<tbody>
<tr>
@@ -155,7 +168,7 @@
</div>
</div>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="boost.execution_exception"></a><div class="titlepage"></div>
<div class="refnamediv">
<h2><span class="refentrytitle">Class execution_exception</span></h2>
@@ -164,30 +177,34 @@
</p>
</div>
<h2 xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv-title">Synopsis</h2>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv"><pre class="synopsis">
-<span class="bold"><strong>class</strong></span> <a class="link" href="reference.html#boost.execution_exception" title="Class execution_exception">execution_exception</a> {
-<span class="bold"><strong>public</strong></span>:
- <span class="bold"><strong>enum</strong></span> <a class="link" href="reference.html#boost.execution_exception.error_code" title="Type error_code">error_code</a>;
-};</pre></div>
-<div class="refsect1" lang="en">
-<a name="id630857"></a><h2>Description</h2>
+<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv"><pre class="synopsis"><span class="comment">// In header: <boost/test/execution_monitor.hpp>
+
+</span>
+<span class="keyword">class</span> <a class="link" href="reference.html#boost.execution_exception" title="Class execution_exception">execution_exception</a> <span class="special">{</span>
+<span class="keyword">public</span><span class="special">:</span>
+ <span class="keyword">enum</span> <a class="link" href="reference.html#boost.execution_exception.error_code" title="Type error_code">error_code</a><span class="special">;</span>
+<span class="special">}</span><span class="special">;</span></pre></div>
+<div class="refsect1">
+<a name="id480502"></a><h2>Description</h2>
<p class="first-line-indented">
The class execution_exception is an exception used by the Execution Monitor to report problems detected during
a monitored function execution. It intentionally does not allocate any memory so as to be safe for use when
there is a lack of memory.
</p>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="boost.execution_exception.error_code"></a><div class="titlepage"></div>
<div class="refnamediv">
<h2><span class="refentrytitle">Type error_code</span></h2>
<p>boost::execution_exception::error_code</p>
</div>
<h2 xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv-title">Synopsis</h2>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv"><pre class="synopsis">
-<span class="bold"><strong>enum</strong></span> error_code { no_error, user_error, cpp_exception_error, system_error,
- timeout_error, user_fatal_error, system_fatal_error };</pre></div>
-<div class="refsect1" lang="en">
-<a name="id630905"></a><h2>Description</h2>
+<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv"><pre class="synopsis"><span class="comment">// In header: <boost/test/execution_monitor.hpp>
+
+</span>
+<span class="keyword">enum</span> <span class="identifier">error_code</span> <span class="special">{</span> no_error, user_error, cpp_exception_error, system_error,
+ timeout_error, user_fatal_error, system_fatal_error <span class="special">}</span><span class="special">;</span></pre></div>
+<div class="refsect1">
+<a name="id480575"></a><h2>Description</h2>
<p class="first-line-indented">
These values are sometimes used as program return codes. The particular values have been chosen to avoid
conflicts with commonly used program return codes: values < 100 are often user assigned, values > 255 are
@@ -222,7 +239,7 @@
</div>
</div>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="boost.execution_aborted"></a><div class="titlepage"></div>
<div class="refnamediv">
<h2><span class="refentrytitle">Class execution_aborted</span></h2>
@@ -232,11 +249,13 @@
</p>
</div>
<h2 xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv-title">Synopsis</h2>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv"><pre class="synopsis">
-<span class="bold"><strong>class</strong></span> <a class="link" href="reference.html#boost.execution_aborted" title="Class execution_aborted">execution_aborted</a> {
-};</pre></div>
+<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv"><pre class="synopsis"><span class="comment">// In header: <boost/test/execution_monitor.hpp>
+
+</span>
+<span class="keyword">class</span> <a class="link" href="reference.html#boost.execution_aborted" title="Class execution_aborted">execution_aborted</a> <span class="special">{</span>
+<span class="special">}</span><span class="special">;</span></pre></div>
</div>
-<div class="refentry" lang="en">
+<div class="refentry">
<a name="boost.system_error"></a><div class="titlepage"></div>
<div class="refnamediv">
<h2><span class="refentrytitle">Class system_error</span></h2>
@@ -245,22 +264,26 @@
</p>
</div>
<h2 xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv-title">Synopsis</h2>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv"><pre class="synopsis">
-<span class="bold"><strong>class</strong></span> <a class="link" href="reference.html#boost.system_error" title="Class system_error">system_error</a> {
-<span class="bold"><strong>public</strong></span>:
+<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv"><pre class="synopsis"><span class="comment">// In header: <boost/test/execution_monitor.hpp>
+
+</span>
+<span class="keyword">class</span> <a class="link" href="reference.html#boost.system_error" title="Class system_error">system_error</a> <span class="special">{</span>
+<span class="keyword">public</span><span class="special">:</span>
<span class="emphasis"><em>// <a class="link" href="reference.html#boost.system_errorconstruct-copy-destruct">construct/copy/destruct</a></em></span>
- <a class="link" href="reference.html#id270669-bb">system_error</a>();
- <span class="type">unit_test::readonly_property<<span class="bold"><strong>long</strong></span>></span> p_errno;
-};</pre></div>
-<div class="refsect1" lang="en">
-<a name="id630949"></a><h2>Description</h2>
-<div class="refsect2" lang="en">
-<a name="id630953"></a><h3>
+ <a class="link" href="reference.html#id236852-bb"><span class="identifier">system_error</span></a><span class="special">(</span><span class="special">)</span><span class="special">;</span>
+ <span class="type">unit_test::readonly_property<span class="special"><</span><span class="keyword">long</span><span class="special">></span></span> p_errno<span class="special">;</span> <span class="comment">//
+ System errno value at the point of error.
+ </span>
+<span class="special">}</span><span class="special">;</span></pre></div>
+<div class="refsect1">
+<a name="id480817"></a><h2>Description</h2>
+<div class="refsect2">
+<a name="id480820"></a><h3>
<a name="boost.system_errorconstruct-copy-destruct"></a><code class="computeroutput">system_error</code>
public
construct/copy/destruct</h3>
-<div class="orderedlist"><ol type="1"><li>
-<pre class="literallayout"><a name="id270669-bb"></a>system_error();</pre>
+<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
+<pre class="literallayout"><a name="id236852-bb"></a><span class="identifier">system_error</span><span class="special">(</span><span class="special">)</span><span class="special">;</span></pre>
<div class="variablelist"><table border="0">
<col align="left" valign="top">
<tbody>
@@ -282,7 +305,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/execution-monitor/user-guide.html
==============================================================================
--- trunk/libs/test/doc/html/execution-monitor/user-guide.html (original)
+++ trunk/libs/test/doc/html/execution-monitor/user-guide.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>The Execution Monitor user's guide</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
-<link rel="up" href="../execution-monitor.html" title="Part I. Boost Test Library: The Execution Monitor">
+<link rel="up" href="../execution-monitor.html" title="Boost Test Library: The Execution Monitor">
<link rel="prev" href="compilation.html" title="The Execution Monitor compilation variants and procedures">
<link rel="next" href="reference.html" title="The Execution Monitor reference">
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
@@ -22,7 +22,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="execution-monitor.user-guide"></a>The Execution Monitor user's guide</h3></div></div></div>
<p class="first-line-indented">
@@ -40,29 +40,29 @@
All symbols in the Execution Monitor implementation are located in the namespace boost. To use the Execution
Monitor you need to:
</p>
-<div class="orderedlist"><ol type="1">
-<li>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
#include <boost/test/execution_monitor.hpp>
</li>
-<li>Make an instance of <code class="computeroutput"><a class="link" href="reference.html#boost.execution_monitor" title="Class execution_monitor">execution_monitor</a></code>
+<li class="listitem">Make an instance of <code class="computeroutput"><a class="link" href="reference.html#boost.execution_monitor" title="Class execution_monitor">execution_monitor</a></code>
</li>
-<li>
+<li class="listitem">
Optionally register custom exception translators for exception classes which require special processing.
</li>
</ol></div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="execution-monitor.user-guide.monitor-outcomes"></a>Monitored function execution</h4></div></div></div>
<p class="first-line-indented">
- To start the monitored function, invoke the method <code class="computeroutput"><a class="link" href="reference.html#id270361-bb">execution_monitor::execute</a></code> and pass
+ To start the monitored function, invoke the method <code class="computeroutput"><a class="link" href="reference.html#id186126-bb">execution_monitor::execute</a></code> and pass
the monitored function as an argument. If the call succeeds, the method returns the result code produced by the
monitored function. If any of the following conditions occur:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>Uncaught C++ exception.</li>
-<li>Hardware or software signal, trap, or other exception.</li>
-<li>Timeout reached.</li>
-<li>Debug assert event occurred (under Microsoft Visual C++ or compatible compiler).</li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">Uncaught C++ exception.</li>
+<li class="listitem">Hardware or software signal, trap, or other exception.</li>
+<li class="listitem">Timeout reached.</li>
+<li class="listitem">Debug assert event occurred (under Microsoft Visual C++ or compatible compiler).</li>
</ul></div>
<p>
then the method throws the <code class="computeroutput"><a class="link" href="reference.html#boost.execution_exception" title="Class execution_exception">execution_exception</a></code>. The exception contains unique
@@ -70,7 +70,7 @@
the error.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="execution-monitor.user-guide.monitor-params"></a>The execution monitor parameters</h4></div></div></div>
<p class="first-line-indented">
@@ -105,7 +105,7 @@
exception on platforms where it's supported.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="execution-monitor.user-guide.errors-reporting"></a>Errors reporting and translation</h4></div></div></div>
<p class="first-line-indented">
@@ -113,10 +113,10 @@
<code class="computeroutput"><a class="link" href="reference.html#boost.execution_exception" title="Class execution_exception">execution_exception</a></code> - it's not intended to be used for this purpose. The simplest choice is
to use one of the following C++ types as an exception:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>C string.</li>
-<li>std:string.</li>
-<li>any exception class in std::exception hierarchy.</li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">C string.</li>
+<li class="listitem">std:string.</li>
+<li class="listitem">any exception class in std::exception hierarchy.</li>
</ul></div>
<p class="first-line-indented">
In case if you prefer to use your own exception classes or can't govern what exceptions are generated by monitored
@@ -128,10 +128,10 @@
<p class="first-line-indented">
Finally, if you need to abort the monitored function execution without reporting any errors, you can throw an
exception <code class="computeroutput"><a class="link" href="reference.html#boost.execution_aborted" title="Class execution_aborted">execution_aborted</a></code>. As a result the execution is aborted and zero result code
- is produced by the method <code class="computeroutput"><a class="link" href="reference.html#id270361-bb">execution_monitor::execute</a></code>.
+ is produced by the method <code class="computeroutput"><a class="link" href="reference.html#id186126-bb">execution_monitor::execute</a></code>.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="execution-monitor.user-guide.mem-leaks-detection"></a>Memory leaks detection</h4></div></div></div>
<p class="first-line-indented">
@@ -154,7 +154,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/faq.html
==============================================================================
--- trunk/libs/test/doc/html/faq.html (original)
+++ trunk/libs/test/doc/html/faq.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Frequently Asked Questions</title>
<link rel="stylesheet" href="../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="index.html" title="Boost Test Library">
<link rel="up" href="intro.html" title="Introduction">
<link rel="prev" href="intro.html" title="Introduction">
@@ -24,54 +24,55 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="btl.faq"></a>Frequently Asked Questions</h3></div></div></div>
<div class="qandaset">
-<dl>
-<dt> <a href="faq.html#id641632">
+<a name="id479223"></a><dl>
+<dt> <a href="faq.html#id479228">
Where the latest version of the Boost Test Library is located?
</a>
</dt>
-<dt> <a href="faq.html#id641658">
+<dt> <a href="faq.html#id479117">
I found a bug. Where can I report it?
</a>
</dt>
-<dt> <a href="faq.html#id641686">
+<dt> <a href="faq.html#id479145">
I have a request for a new feature. Where can I ask for it?
</a>
</dt>
-<dt> <a href="faq.html#id641714">
+<dt> <a href="faq.html#id423775">
How to create test case using the Unit Test Framework?
</a>
</dt>
-<dt> <a href="faq.html#id641746">
+<dt> <a href="faq.html#id423804">
How to create test suite using the Unit Test Framework?
</a>
</dt>
-<dt> <a href="faq.html#id641781">
+<dt> <a href="faq.html#id423835">
Why did I get a linker error when compiling my test program?
</a>
</dt>
-<dt> <a href="faq.html#id641857">
+<dt> <a href="faq.html#id423908">
How can I redirect testing output?
</a>
</dt>
-<dt> <a href="faq.html#id641893">
+<dt> <a href="faq.html#id425509">
I want different default log trace level
</a>
</dt>
-<dt> <a href="faq.html#id641929">
+<dt> <a href="faq.html#id425541">
Is there DLL version of Boost.Test components available on Win32 platform?
</a>
</dt>
</dl>
-<table border="0" summary="Q and A Set">
+<table border="0" width="100%" summary="Q and A Set">
<col align="left" width="1%">
+<col>
<tbody>
<tr class="question">
<td align="left" valign="top">
-<a name="id641632"></a><a name="id641634"></a>
+<a name="id479228"></a><a name="id479230"></a>
</td>
<td align="left" valign="top"><b><p>
Where the latest version of the Boost Test Library is located?
@@ -85,7 +86,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id641658"></a><a name="id641660"></a>
+<a name="id479117"></a><a name="id479119"></a>
</td>
<td align="left" valign="top"><b><p>
I found a bug. Where can I report it?
@@ -100,7 +101,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id641686"></a><a name="id641688"></a>
+<a name="id479145"></a><a name="id479147"></a>
</td>
<td align="left" valign="top"><b><p>
I have a request for a new feature. Where can I ask for it?
@@ -115,7 +116,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id641714"></a><a name="id641716"></a>
+<a name="id423775"></a><a name="id423778"></a>
</td>
<td align="left" valign="top"><b><p>
How to create test case using the Unit Test Framework?
@@ -130,7 +131,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id641746"></a><a name="id641748"></a>
+<a name="id423804"></a><a name="id423807"></a>
</td>
<td align="left" valign="top"><b><p>
How to create test suite using the Unit Test Framework?
@@ -145,7 +146,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id641781"></a><a name="id641783"></a>
+<a name="id423835"></a><a name="id423837"></a>
</td>
<td align="left" valign="top"><b><p>
Why did I get a linker error when compiling my test program?
@@ -171,7 +172,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id641857"></a><a name="id641859"></a>
+<a name="id423908"></a><a name="id423910"></a>
</td>
<td align="left" valign="top"><b><p>
How can I redirect testing output?
@@ -186,7 +187,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id641893"></a><a name="id641895"></a>
+<a name="id425509"></a><a name="id425511"></a>
</td>
<td align="left" valign="top"><b><p>
I want different default log trace level
@@ -202,7 +203,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id641929"></a><a name="id641931"></a>
+<a name="id425541"></a><a name="id425544"></a>
</td>
<td align="left" valign="top"><b><p>
Is there DLL version of Boost.Test components available on Win32 platform?
@@ -220,7 +221,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/index.html
==============================================================================
--- trunk/libs/test/doc/html/index.html (original)
+++ trunk/libs/test/doc/html/index.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Boost Test Library</title>
<link rel="stylesheet" href="../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="index.html" title="Boost Test Library">
<link rel="next" href="intro.html" title="Introduction">
<script language="JavaScript1.2" src="../js/boost-test.js"></script>
@@ -15,7 +15,7 @@
<td><div class="spirit-nav">
</div></td>
</tr></table>
<hr>
-<div class="chapter" lang="en">
+<div class="chapter">
<div class="titlepage"><div>
<div><h2 class="title">
<a name="btl"></a>Boost Test Library</h2></div>
@@ -25,9 +25,9 @@
</h3>
<code class="email"><<a class="email" href="mailto:boost-test%20=at=%20emailaccount%20=dot=%20com">boost-test =at= emailaccount =dot= com</a>></code>
</div></div>
-<div><p class="copyright">Copyright © 2001-2007 Gennadiy Rozental</p></div>
+<div><p class="copyright">Copyright © 2001-2008 Gennadiy Rozental</p></div>
<div><div class="legalnotice">
-<a name="id586245"></a><p>
+<a name="id425261"></a><p>
Use, modification and distribution is subject to the Boost Software License, Version 1.0. (See accompanying file
<code class="filename">LICENSE_1_0.txt</code> or copy at
<a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt> )
@@ -43,23 +43,19 @@
<dt>Open issues</dt>
<dt>Acknowledgements</dt>
</dl>
-<dt>I. The Execution Monitor
-</dt>
+<dt>The Execution Monitor</dt>
<dl>
<dt>Compilation</dt>
<dt>User's guide</dt>
<dt>Reference</dt>
</dl>
-<dt>II. The Program Execution Monitor
-</dt>
+<dt>The Program Execution Monitor</dt>
<dl>
<dt>Implementation</dt>
<dt>Compilation</dt>
</dl>
-<dt>III. Minimal testing facility
-</dt>
-<dt>IV. The Unit Test Framework
-</dt>
+<dt>Minimal testing facility</dt>
+<dt>The Unit Test Framework</dt>
<dl>
<dt>Introduction</dt>
<dt>Tutorials</dt>
@@ -121,7 +117,7 @@
<dt>BOOST_TEST_MESSAGE</dt>
<dt>BOOST_TEST_CHECKPOINT</dt>
<dt>BOOST_TEST_PASSPOINT</dt>
-<dt>Logging floating point type numbers</dt>
+<dt>Logging floating point type numbers</dt>
<dt>Human readable format</dt>
<dt>XML based log output format</dt>
<dt>Compile time configuration</dt>
Modified: trunk/libs/test/doc/html/intro.html
==============================================================================
--- trunk/libs/test/doc/html/intro.html (original)
+++ trunk/libs/test/doc/html/intro.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Introduction</title>
<link rel="stylesheet" href="../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="index.html" title="Boost Test Library">
<link rel="up" href="index.html" title="Boost Test Library">
<link rel="prev" href="index.html" title="Boost Test Library">
@@ -22,40 +22,48 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="btl.intro"></a>Introduction</h2></div></div></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt>FAQ</dt>
+<dt>Open issues</dt>
+<dt>Acknowledgements</dt>
+</dl>
+</div>
<div class="epigraph">
<p>Test everything that could possibly break</p>
-<div class="attribution"><span>--<span class="attribution">XP maxim</span></span></div>
+<div class="attribution"><span>—<span class="attribution">XP maxim</span></span></div>
</div>
<p class="first-line-indented">
The Boost Test Library provides a matched set of components for writing test programs, organizing tests in to
simple test cases and test suites, and controlling their runtime execution. The Program Execution Monitor is also
useful in some production (non-test) environments.
</p>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="btl.about-docs"></a>About this documentation</h3></div></div></div>
<p class="first-line-indented">
This documentation is <span class="bold"><strong>not</strong></span> intended to be read though from the beginning to the end by
a novice user. You can do that if you are interested in detailed bottom-up description of all Boost.Test components.
Otherwise you are better off jumping directly to the subject of your interest. For example, if you are interested in
- unit testing framework you may go directly <a class="link" href="utf.html" title="Part IV. Boost Test Library: The Unit Test Framework">there</a>, but for novice users I recommend to
+ unit testing framework you may go directly <a class="link" href="utf.html" title="Boost Test Library: The Unit Test Framework">there</a>, but for novice users I recommend to
start from simple <a class="link" href="utf/tutorials.html" title="The unit test framework tutorials">tutorials</a>. Looking for quick help - check
<a class="link" href="faq.html" title="Frequently Asked Questions">FAQ</a> section for resolution to many popular issues you may be faced with. Most pages
should link you directly to the terms that you need to understand it. For help with compilation see compilation
sections of an appropriate component.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="btl.release-notes"></a>Release notes</h3></div></div></div>
<p class="first-line-indented">
For more details see complete release notes.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="btl.portability"></a>Portability</h3></div></div></div>
<p class="first-line-indented">
@@ -72,7 +80,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/minimal.html
==============================================================================
--- trunk/libs/test/doc/html/minimal.html (original)
+++ trunk/libs/test/doc/html/minimal.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Part III. Boost Test Library: The minimal testing facility</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Boost Test Library: The minimal testing facility</title>
<link rel="stylesheet" href="../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="index.html" title="Boost Test Library">
<link rel="up" href="index.html" title="Boost Test Library">
<link rel="prev" href="prg-exec-monitor/compilation.html" title="The Program Execution Monitor compilation">
-<link rel="next" href="utf.html" title="Part IV. Boost Test Library: The Unit Test Framework">
+<link rel="next" href="utf.html" title="Boost Test Library: The Unit Test Framework">
<script language="JavaScript1.2" src="../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -20,10 +20,10 @@
</div></td>
</tr></table>
<hr>
-<div class="part" lang="en">
-<div class="titlepage"><div><div><h1 class="title">
-<a name="minimal"></a>Part III. Boost Test Library: The minimal testing facility</h1></div></div></div>
-<div class="section" lang="en">
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="minimal"></a>Boost Test Library: The minimal testing facility</h2></div></div></div>
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="minimal.intro"></a>Introduction</h3></div></div></div>
<p class="first-line-indented">
@@ -31,7 +31,7 @@
original version of Boost.Test. As the name suggest, it provides only minimal basic facilities for test creation. It
have no configuration parameters (either command line arguments or environment variables) and it supplies
a limited set of <a class="link" href="minimal.html#minimal.tools" title="Provided testing tools">testing tools</a> which behaves similarly to ones defined amount
- the Unit Test Framework <a class="link" href="utf/testing-tools.html" title="The UTF testing tools or tester's toolbox for all occasions">Testing tools</a>. The minimal testing facility supplies its own function
+ the Unit Test Framework <a class="link" href="utf/testing-tools.html" title="The UTF testing tools … or tester's toolbox for all occasions">Testing tools</a>. The minimal testing facility supplies its own function
main() (so can not be used for multi unit testing) and will execute the test program in a monitored environment.
</p>
<p class="first-line-indented">
@@ -40,7 +40,7 @@
testing tools (and other goods), while still being as easy to set up.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="minimal.usage"></a>Usage</h3></div></div></div>
<p class="first-line-indented">
@@ -57,7 +57,7 @@
<a class="link" href="minimal.html#minimal.tools" title="Provided testing tools">testing tools</a> provided by the minimal testing facility and get uniform errors reporting.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="minimal.example"></a>Example</h3></div></div></div>
<p class="first-line-indented">
@@ -65,7 +65,7 @@
testing tools
</p>
<div class="example">
-<a name="minimal.example.example27"></a><p class="title"><b>Example 4. Minimal testing facility application</b></p>
+<a name="minimal.example.example27"></a><p class="title"><b>Example 4. Minimal testing facility application</b></p>
<div class="example-contents">
<div class="programlistingco">
<pre class="programlisting">#include <boost/test/minimal.hpp>
@@ -92,12 +92,12 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show annotations</code></td>
+<td><code class="literal">Show annotations</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<div class="example-annot" id="example27-annot"><table border="0" summary="Callout list">
<tr>
@@ -157,7 +157,7 @@
</div>
<br class="example-break">
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="minimal.tools"></a>Provided testing tools</h3></div></div></div>
<p class="first-line-indented">
@@ -173,7 +173,7 @@
implemented by the Unit Test Framework.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="minimal.impl"></a>Implementation</h3></div></div></div>
<p class="first-line-indented">
@@ -187,7 +187,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"><p><small>Last revised: , at </small></p></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/open-issues.html
==============================================================================
--- trunk/libs/test/doc/html/open-issues.html (original)
+++ trunk/libs/test/doc/html/open-issues.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Open issues</title>
<link rel="stylesheet" href="../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="index.html" title="Boost Test Library">
<link rel="up" href="intro.html" title="Introduction">
<link rel="prev" href="faq.html" title="Frequently Asked Questions">
@@ -22,41 +22,41 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="btl.open-issues"></a>Open issues</h3></div></div></div>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>Finish update for the command line arguments support</li>
-<li>Selective test cases run by name</li>
-<li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">Finish update for the command line arguments support</li>
+<li class="listitem">Selective test cases run by name</li>
+<li class="listitem">
Boost.Test thread safety need to be achieved at least if BOOST_TEST_THREAD_SAFE is defined. This one will require
separate discussion
</li>
-<li>
+<li class="listitem">
Some performance testing tools (aka profiler). Unless somebody else will come up with something like this
</li>
-<li>
+<li class="listitem">
Build info feature needs to be updated: there are at least two different "build infos": library build and test
module build
</li>
-<li>More tutorial documentation.</li>
-<li>
+<li class="listitem">More tutorial documentation.</li>
+<li class="listitem">
Projects that could be very interesting, but I may not be able to do it by myself:
<div class="itemizedlist"><ul type="circle">
-<li>An add-on for Visual Studio to automate test case/ test modules generation</li>
-<li>Set of Python and/or Perl scripts to automate test case/test modules generation from command line</li>
+<li class="listitem">An add-on for Visual Studio to automate test case/ test modules generation</li>
+<li class="listitem">Set of Python and/or Perl scripts to automate test case/test modules generation from command line</li>
</ul></div>
</li>
-<li>Memory usage test tools.</li>
-<li>Time-out implementation on Win32 platform.</li>
-<li>Make output_test_stream match like diff do</li>
-<li>Better Unicode support (reports and log in wostream)</li>
-<li>Support for custom test case dependency/condition</li>
+<li class="listitem">Memory usage test tools.</li>
+<li class="listitem">Time-out implementation on Win32 platform.</li>
+<li class="listitem">Make output_test_stream match like diff do</li>
+<li class="listitem">Better Unicode support (reports and log in wostream)</li>
+<li class="listitem">Support for custom test case dependency/condition</li>
</ul></div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/prg-exec-monitor.html
==============================================================================
--- trunk/libs/test/doc/html/prg-exec-monitor.html (original)
+++ trunk/libs/test/doc/html/prg-exec-monitor.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Part II. Boost Test Library: The Program Execution Monitor</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Boost Test Library: The Program Execution Monitor</title>
<link rel="stylesheet" href="../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="index.html" title="Boost Test Library">
<link rel="up" href="index.html" title="Boost Test Library">
<link rel="prev" href="execution-monitor/reference.html" title="The Execution Monitor reference">
@@ -22,9 +22,9 @@
</div></td>
</tr></table>
<hr>
-<div class="part" lang="en">
-<div class="titlepage"><div><div><h1 class="title">
-<a name="pem"></a>Part II. Boost Test Library: The Program Execution Monitor</h1></div></div></div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="pem"></a>Boost Test Library: The Program Execution Monitor</h2></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
@@ -32,7 +32,7 @@
<dt>Compilation</dt>
</dl>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="pem.intro"></a>Introduction</h3></div></div></div>
<p class="first-line-indented">
@@ -61,11 +61,11 @@
</p>
<p class="first-line-indented">
Uniform error reporting can be also useful in test environments such as the Boost regression tests. Be aware though
- in such case it might be preferable to use the <a class="link" href="utf.html" title="Part IV. Boost Test Library: The Unit Test Framework">Unit Test Framework</a>, cause it allows one
- to use the <a class="link" href="utf/testing-tools.html" title="The UTF testing tools or tester's toolbox for all occasions">Testing tools</a> and generate more detailed error information.
+ in such case it might be preferable to use the <a class="link" href="utf.html" title="Boost Test Library: The Unit Test Framework">Unit Test Framework</a>, cause it allows one
+ to use the <a class="link" href="utf/testing-tools.html" title="The UTF testing tools … or tester's toolbox for all occasions">Testing tools</a> and generate more detailed error information.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="pem.usage"></a>Usage</h3></div></div></div>
<p class="first-line-indented">
@@ -76,7 +76,7 @@
Here is the traditional Hello World program implemented using the Program Execution Monitor:
</p>
<div class="example">
-<a name="pem.usage.example24"></a><p class="title"><b>Example 1. The Program Execution Monitor: Hello World</b></p>
+<a name="pem.usage.example24"></a><p class="title"><b>Example 1. The Program Execution Monitor: Hello World</b></p>
<div class="example-contents">
<pre class="programlisting">#include <iostream>
#include <boost/test/included/prg_exec_monitor.hpp>
@@ -92,10 +92,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example24-output">Hello, world
@@ -109,16 +109,16 @@
<p class="first-line-indented">
The Program Execution Monitor treats as errors:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>Exceptions thrown from cpp_main().</li>
-<li>Non-zero return from cpp_main().</li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">Exceptions thrown from cpp_main().</li>
+<li class="listitem">Non-zero return from cpp_main().</li>
</ul></div>
<p class="first-line-indented">
So what if some function had thrown a runtime_error with the message "big trouble" and it's not trapped by any
catch clause? Like in a following example:
</p>
<div class="example">
-<a name="pem.usage.example25"></a><p class="title"><b>Example 2. The Program Execution Monitor: standard exception detection</b></p>
+<a name="pem.usage.example25"></a><p class="title"><b>Example 2. The Program Execution Monitor: standard exception detection</b></p>
<div class="example-contents">
<pre class="programlisting">#include <stdexcept>
#include <boost/test/included/prg_exec_monitor.hpp>
@@ -138,10 +138,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example25-output">**** exception(205): std::runtime_error: big trouble
******** errors detected; see standard output for details ********</pre>
@@ -159,7 +159,7 @@
Let's consider an example where function cpp_main() had bubbled up a return code of 5:
</p>
<div class="example">
-<a name="pem.usage.example26"></a><p class="title"><b>Example 3. The Program Execution Monitor: error return code detection</b></p>
+<a name="pem.usage.example26"></a><p class="title"><b>Example 3. The Program Execution Monitor: error return code detection</b></p>
<div class="example-contents">
<pre class="programlisting">#include <boost/test/prg_exec_monitor.hpp> // this header is optional
@@ -172,10 +172,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example26-output">**** error return code: 5
******** errors detected; see standard output for details ********</pre>
@@ -190,13 +190,13 @@
<p class="first-line-indented">
The Program Execution Monitor's supplied main() will return following result codes:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>boost::exit_success - no errors</li>
-<li>boost::exit_failure - non-zero and non-boost::exit_success return code from cpp_main().</li>
-<li>boost::exit_exception_failure - cpp_main() throw an exception.</li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">boost::exit_success - no errors</li>
+<li class="listitem">boost::exit_failure - non-zero and non-boost::exit_success return code from cpp_main().</li>
+<li class="listitem">boost::exit_exception_failure - cpp_main() throw an exception.</li>
</ul></div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="pem.config"></a>Configuration</h3></div></div></div>
<p class="first-line-indented">
@@ -204,11 +204,11 @@
environment variables.
</p>
<div class="table">
-<a name="pem.config.flags"></a><p class="title"><b>Table 1. The Program Execution Monitor configuration environment variables</b></p>
+<a name="pem.config.flags"></a><p class="title"><b>Table 1. The Program Execution Monitor configuration environment variables</b></p>
<div class="table-contents"><table class="table" summary="The Program Execution Monitor configuration environment variables">
<colgroup>
-<col>
-<col>
+<col class="c1">
+<col class="c3">
</colgroup>
<thead><tr>
<th>Flag</th>
@@ -240,7 +240,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"><p><small>Last revised: , at </small></p></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/prg-exec-monitor/compilation.html
==============================================================================
--- trunk/libs/test/doc/html/prg-exec-monitor/compilation.html (original)
+++ trunk/libs/test/doc/html/prg-exec-monitor/compilation.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>The Program Execution Monitor compilation</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
-<link rel="up" href="../prg-exec-monitor.html" title="Part II. Boost Test Library: The Program Execution Monitor">
+<link rel="up" href="../prg-exec-monitor.html" title="Boost Test Library: The Program Execution Monitor">
<link rel="prev" href="impl.html" title="The Program Execution Monitor implementation">
-<link rel="next" href="../minimal.html" title="Part III. Boost Test Library: The minimal testing facility">
+<link rel="next" href="../minimal.html" title="Boost Test Library: The minimal testing facility">
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,7 +22,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="pem.compilation"></a>The Program Execution Monitor compilation</h3></div></div></div>
<p class="first-line-indented">
@@ -35,11 +35,11 @@
compilation of the Program Execution Monitor library and your program:
</p>
<div class="table">
-<a name="pem.compilation.flags"></a><p class="title"><b>Table 2. Program Execution Monitor compilation flags</b></p>
+<a name="pem.compilation.flags"></a><p class="title"><b>Table 2. Program Execution Monitor compilation flags</b></p>
<div class="table-contents"><table class="table" summary="Program Execution Monitor compilation flags">
<colgroup>
-<col>
-<col>
+<col class="c1">
+<col class="c3">
</colgroup>
<thead><tr>
<th>Variable</th>
@@ -59,20 +59,20 @@
</tbody>
</table></div>
</div>
-<br class="table-break"><div class="section" lang="en">
+<br class="table-break"><div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="pem.compilation.standalone"></a>Standalone library compilation</h4></div></div></div>
<p class="first-line-indented">
If you opted to link your program with the standalone library, you need to build it first. To build a standalone
library all C++ files (.cpp), that constitute Program Execution Monitor <a class="link" href="impl.html" title="The Program Execution Monitor implementation">implementation</a> need to be
- listed as source files in your makefile<sup>[<a name="id642858" href="#ftn.id642858" class="footnote">1</a>]</sup>.
+ listed as source files in your makefile<sup>[<a name="id481935" href="#ftn.id481935" class="footnote">1</a>]</sup>.
</p>
<p class="first-line-indented">
The makefile for use with Boost.Build system is supplied in <code class="filename">libs/test/build</code>
directory. The Program Execution Monitor can be built as either <a class="link" href="compilation.html#pem.compilation.standalone.static" title="Static library compilation">static</a>
or <a class="link" href="compilation.html#pem.compilation.standalone.dynamic" title="Dynamic library compilation">dynamic</a> library.
</p>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="pem.compilation.standalone.static"></a>Static library compilation</h5></div></div></div>
<p class="first-line-indented">
@@ -84,11 +84,11 @@
Also on Windows you can use the Microsoft Visual Studio .NET project file provided.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="pem.compilation.standalone.dynamic"></a>Dynamic library compilation</h5></div></div></div>
<p class="first-line-indented">
- To build the dynamic library<sup>[<a name="id643007" href="#ftn.id643007" class="footnote">2</a>]</sup> you
+ To build the dynamic library<sup>[<a name="id482056" href="#ftn.id482056" class="footnote">2</a>]</sup> you
need to add <a class="xref" href="compilation.html#pem.flag.dyn-link">BOOST_TEST_DYN_LINK</a> to the list of macro definitions in the
makefile. Using the Boost.Build system you can build the dynamic library with the following command from
<code class="filename">libs/test/build</code> directory:
@@ -110,7 +110,7 @@
</table></div>
</div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="pem.compilation.auto-linking"></a>Support of the auto-linking feature</h4></div></div></div>
<p class="first-line-indented">
@@ -127,7 +127,7 @@
<a href="../under_construction.html" target="_top">appropriate documentation</a>.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="pem.compilation.direct-include"></a>Including the Program Execution Monitor directly into your program</h4></div></div></div>
<p class="first-line-indented">
@@ -142,19 +142,19 @@
</div>
<div class="footnotes">
<br><hr width="100" align="left">
-<div class="footnote"><p><sup>[<a name="ftn.id642858" href="#id642858" class="simpara">1</a>] </sup>There are varieties of make systems that can be used. To name
+<div class="footnote"><p><sup>[<a id="ftn.id481935" href="#id481935" class="simpara">1</a>] </sup>There are varieties of make systems that can be used. To name
a few: <acronym class="acronym">GNU</acronym> make (and other make clones) and build systems integrated into <acronym class="acronym">IDE</acronym>s
(for example Microsoft Visual Studio). The Boost preferred solution is Boost.Build system that is based on top of
bjam tool. Make systems require some kind of configuration file that lists all files that constitute the library
and all build options. For example the makefile that is used by make, or the Microsoft Visual Studio project file,
Jamfile is used by Boost.Build. For the sake of simplicity let's call this file the makefile.</p></div>
-<div class="footnote"><p><sup>[<a name="ftn.id643007" href="#id643007" class="simpara">2</a>] </sup>What is meant by the term dynamic library is a <em class="firstterm">dynamically
+<div class="footnote"><p><sup>[<a id="ftn.id482056" href="#id482056" class="simpara">2</a>] </sup>What is meant by the term dynamic library is a <em class="firstterm">dynamically
loaded library</em>, alternatively called a <em class="firstterm">shared library</em>.</p></div>
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/prg-exec-monitor/impl.html
==============================================================================
--- trunk/libs/test/doc/html/prg-exec-monitor/impl.html (original)
+++ trunk/libs/test/doc/html/prg-exec-monitor/impl.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>The Program Execution Monitor implementation</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
-<link rel="up" href="../prg-exec-monitor.html" title="Part II. Boost Test Library: The Program Execution Monitor">
-<link rel="prev" href="../prg-exec-monitor.html" title="Part II. Boost Test Library: The Program Execution Monitor">
+<link rel="up" href="../prg-exec-monitor.html" title="Boost Test Library: The Program Execution Monitor">
+<link rel="prev" href="../prg-exec-monitor.html" title="Boost Test Library: The Program Execution Monitor">
<link rel="next" href="compilation.html" title="The Program Execution Monitor compilation">
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
</head>
@@ -22,26 +22,26 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="pem.impl"></a>The Program Execution Monitor implementation</h3></div></div></div>
<p class="first-line-indented">
To monitor execution of user supplied function cpp_main() the Program Execution Monitor relies on the Boost.Test's
- <a class="link" href="../execution-monitor.html" title="Part I. Boost Test Library: The Execution Monitor">Execution Monitor</a>. Also the Program Execution Monitor supplies the function main() to facilitate
+ <a class="link" href="../execution-monitor.html" title="Boost Test Library: The Execution Monitor">Execution Monitor</a>. Also the Program Execution Monitor supplies the function main() to facilitate
uniform error reporting. Following files constitute the Program Execution Monitor implementation:
</p>
<div class="variablelist"><table border="0">
<col align="left" valign="top">
<tbody>
<tr>
-<td><p><span class="term">libs/test/execution_monitor.cpp</span></p></td>
+<td><p><span class="term">boost/test/impl/execution_monitor.ipp</span></p></td>
<td>
- provides <a class="link" href="../execution-monitor.html" title="Part I. Boost Test Library: The Execution Monitor">Execution Monitor</a> implementation for all supported
+ provides <a class="link" href="../execution-monitor.html" title="Boost Test Library: The Execution Monitor">Execution Monitor</a> implementation for all supported
configurations.
</td>
</tr>
<tr>
-<td><p><span class="term">libs/test/cpp_main.cpp</span></p></td>
+<td><p><span class="term">boost/test/impl/cpp_main.ipp</span></p></td>
<td>supplies function main() for static library build</td>
</tr>
<tr>
@@ -65,7 +65,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/tutorials/hello-the-testing-world.html
==============================================================================
--- trunk/libs/test/doc/html/tutorials/hello-the-testing-world.html (original)
+++ trunk/libs/test/doc/html/tutorials/hello-the-testing-world.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Hello the testing world or beginner's introduction into testing using the Unit Test Framework</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Hello the testing world … or beginner's introduction into testing using the Unit Test Framework</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
<link rel="up" href="../utf/tutorials.html" title="The unit test framework tutorials">
-<link rel="prev" href="intro-in-testing.html" title="Introduction into testing or why testing is worth the effort">
-<link rel="next" href="new-year-resolution.html" title='Boost.Test driven development or "getting started" for TDD followers'>
+<link rel="prev" href="intro-in-testing.html" title="Introduction into testing … or why testing is worth the effort">
+<link rel="next" href="new-year-resolution.html" title='Boost.Test driven development … or "getting started" for TDD followers'>
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,9 +22,9 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="tutorial.hello-the-testing-world"></a>Hello the testing world or beginner's introduction into testing using the Unit Test Framework</h4></div></div></div>
+<a name="tutorial.hello-the-testing-world"></a>Hello the testing world … or beginner's introduction into testing using the Unit Test Framework</h4></div></div></div>
<p class="first-line-indented">
How should a test program report errors? Displaying an error message is an obvious possibility:
</p>
@@ -67,10 +67,10 @@
<p class="first-line-indented">
There are several issues with above test.
</p>
-<div class="orderedlist"><ol type="1">
-<li>You need to convert is_valid result in proper result code.</li>
-<li>Would exception happen in test_object construction of method is_valid invocation, the program will crash.</li>
-<li>You won't see any output, would you run this test manually.</li>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">You need to convert is_valid result in proper result code.</li>
+<li class="listitem">Would exception happen in test_object construction of method is_valid invocation, the program will crash.</li>
+<li class="listitem">You won't see any output, would you run this test manually.</li>
</ol></div>
<p class="first-line-indented">
The Unit Test Framework solves all these issues. To integrate with it above program needs to be changed to:
@@ -181,7 +181,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/tutorials/intro-in-testing.html
==============================================================================
--- trunk/libs/test/doc/html/tutorials/intro-in-testing.html (original)
+++ trunk/libs/test/doc/html/tutorials/intro-in-testing.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Introduction into testing or why testing is worth the effort</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Introduction into testing … or why testing is worth the effort</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
<link rel="up" href="../utf/tutorials.html" title="The unit test framework tutorials">
<link rel="prev" href="../utf/tutorials.html" title="The unit test framework tutorials">
-<link rel="next" href="hello-the-testing-world.html" title="Hello the testing world or beginner's introduction into testing using the Unit Test Framework">
+<link rel="next" href="hello-the-testing-world.html" title="Hello the testing world … or beginner's introduction into testing using the Unit Test Framework">
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,19 +22,19 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div>
<div><h4 class="title">
-<a name="tutorial.intro-in-testing"></a>Introduction into testing or why testing is worth the effort</h4></div>
+<a name="tutorial.intro-in-testing"></a>Introduction into testing … or why testing is worth the effort</h4></div>
<div><div class="author">
<h3 class="author">
<span class="firstname">John</span> <span class="othername">R</span> <span class="surname">Phillips</span>
</h3>
<code class="email"><<a class="email" href="mailto:jphillip%20at%20capital%20dot%20edu%20(please%20unobscure)">jphillip at capital dot edu (please unobscure)</a>></code>
</div></div>
-<div><p class="copyright">Copyright © 2006 John R. Phillips</p></div>
+<div><p class="copyright">Copyright © 2006 John R. Phillips</p></div>
<div><div class="legalnotice">
-<a name="id644286"></a><p>
+<a name="id483159"></a><p>
Use, modification and distribution is subject to the Boost Software License, Version 1.0. (See accompanying file
<code class="filename">LICENSE_1_0.txt</code> or copy at
<a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt> )
@@ -205,7 +205,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/tutorials/new-year-resolution.html
==============================================================================
--- trunk/libs/test/doc/html/tutorials/new-year-resolution.html (original)
+++ trunk/libs/test/doc/html/tutorials/new-year-resolution.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Boost.Test driven development or "getting started" for TDD followers</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Boost.Test driven development … or "getting started" for TDD followers</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
<link rel="up" href="../utf/tutorials.html" title="The unit test framework tutorials">
-<link rel="prev" href="hello-the-testing-world.html" title="Hello the testing world or beginner's introduction into testing using the Unit Test Framework">
+<link rel="prev" href="hello-the-testing-world.html" title="Hello the testing world … or beginner's introduction into testing using the Unit Test Framework">
<link rel="next" href="../utf/compilation.html" title="The UTF compilation variants and procedures">
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
</head>
@@ -22,12 +22,12 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="tutorial.new-year-resolution"></a>Boost.Test driven development or "getting started" for TDD followers</h4></div></div></div>
+<a name="tutorial.new-year-resolution"></a>Boost.Test driven development … or "getting started" for TDD followers</h4></div></div></div>
<p class="first-line-indented">
Today is a momentous day - first day of new year. Today I am going to start a new life. I am going to stop eating a
- greasy food, start attending a fitness club and today I am going to test programs I am writing. I can start
+ greasy food, start attending a fitness club and … today I am going to test programs I am writing. I can start
right after the last line of a program is completed or, even better, I can write tests while I am coding. And maybe
next time I will write tests before the coding, during the design stage. I have read a lot of literature on how to
write the tests, I have the unit test framework in hand and an idea of new class. So let's get started.
@@ -79,7 +79,7 @@
<pre class="programlisting">#define BOOST_TEST_MODULE const_string test
#include <boost/test/unit_test.hpp>
-BOOST_AUTO_EST_CASE( constructors_test )
+BOOST_AUTO_TEST_CASE( constructors_test )
{
const_string cs0( "" ); // 1 //
BOOST_CHECK_EQUAL( cs0.length(), (size_t)0 );
@@ -124,7 +124,7 @@
errors in the implementation (do you write programs without errors from scratch?) I am able to pass this test case
and the unit test framework gives me the following report:
</p>
-<pre class="screen">Running 1 test case
+<pre class="screen">Running 1 test case…
*** No errors detected</pre>
<p class="first-line-indented">
@@ -146,12 +146,12 @@
<pre class="programlisting">#define BOOST_TEST_MODULE const_string test
#include <boost/test/unit_test.hpp>
-BOOST_AUTO_EST_CASE( constructors_test )
+BOOST_AUTO_TEST_CASE( constructors_test )
{
...
}
-BOOST_AUTO_EST_CASE( data_access_test )
+BOOST_AUTO_TEST_CASE( data_access_test )
{
const_string cs1( "test_string" ); // 1 //
BOOST_CHECK_EQUAL( cs1[(size_t)0], 't' );
@@ -184,7 +184,7 @@
</p>
<p class="first-line-indented">
Well, I am step closer to fulfilling my new year resolution (we should see about this fitness club sometime next
- ). What about you? Your testing habits could be a little different. You could start with a class/library
+ …). What about you? Your testing habits could be a little different. You could start with a class/library
development and then at some point start writing test cases on feature basis. Or you can, given a detailed
specification for the future product, including expected interfaces, immediately start with writing all test cases
(or it could be a different person, while you working on implementation at the same time). In any case you should not
@@ -196,7 +196,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf.html
==============================================================================
--- trunk/libs/test/doc/html/utf.html (original)
+++ trunk/libs/test/doc/html/utf.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Part IV. Boost Test Library: The Unit Test Framework</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Boost Test Library: The Unit Test Framework</title>
<link rel="stylesheet" href="../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="index.html" title="Boost Test Library">
<link rel="up" href="index.html" title="Boost Test Library">
-<link rel="prev" href="minimal.html" title="Part III. Boost Test Library: The minimal testing facility">
+<link rel="prev" href="minimal.html" title="Boost Test Library: The minimal testing facility">
<link rel="next" href="utf/intro.html" title="Introduction">
<script language="JavaScript1.2" src="../js/boost-test.js"></script>
</head>
@@ -20,9 +20,9 @@
</div></td>
</tr></table>
<hr>
-<div class="part" lang="en">
-<div class="titlepage"><div><div><h1 class="title">
-<a name="utf"></a>Part IV. Boost Test Library: The Unit Test Framework</h1></div></div></div>
+<div class="section">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="utf"></a>Boost Test Library: The Unit Test Framework</h2></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
@@ -86,7 +86,7 @@
<dt>BOOST_TEST_MESSAGE</dt>
<dt>BOOST_TEST_CHECKPOINT</dt>
<dt>BOOST_TEST_PASSPOINT</dt>
-<dt>Logging floating point type numbers</dt>
+<dt>Logging floating point type numbers</dt>
<dt>Human readable format</dt>
<dt>XML based log output format</dt>
<dt>Compile time configuration</dt>
@@ -118,7 +118,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"><p><small>Last revised: , at </small></p></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/compilation.html
==============================================================================
--- trunk/libs/test/doc/html/utf/compilation.html (original)
+++ trunk/libs/test/doc/html/utf/compilation.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>The UTF compilation variants and procedures</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
-<link rel="up" href="../utf.html" title="Part IV. Boost Test Library: The Unit Test Framework">
-<link rel="prev" href="../tutorials/new-year-resolution.html" title='Boost.Test driven development or "getting started" for TDD followers'>
+<link rel="up" href="../utf.html" title="Boost Test Library: The Unit Test Framework">
+<link rel="prev" href="../tutorials/new-year-resolution.html" title='Boost.Test driven development … or "getting started" for TDD followers'>
<link rel="next" href="compilation/standalone.html" title="Standalone library compilation">
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
</head>
@@ -22,9 +22,9 @@
</div></td>
</tr></table>
<hr>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="utf.compilation"></a>The <acronym class="acronym">UTF</acronym> compilation variants and procedures</h2></div></div></div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="utf.compilation"></a>The <acronym class="acronym">UTF</acronym> compilation variants and procedures</h3></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
@@ -33,7 +33,7 @@
<dt>Direct include</dt>
</dl>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title"><a name="utf.compilation.impl"></a></h4></div></div></div>
<p class="first-line-indented">
The <acronym class="acronym">UTF</acronym> is comparatively complicated component and is implemented in close to hundred header and source files,
@@ -47,28 +47,28 @@
<p class="first-line-indented">
Following files constitute the <acronym class="acronym">UTF</acronym> implementation:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="files-list"><ul type="disc">
-<li>debug.cpp</li>
-<li>compiler_log_formatter.cpp</li>
-<li>exception_safety.cpp</li>
-<li>execution_monitor.cpp</li>
-<li>framework.cpp</li>
-<li>interaction_based.cpp</li>
-<li>logged_expectations.cpp</li>
-<li>plain_report_formatter.cpp</li>
-<li>progress_monitor.cpp</li>
-<li>results_collector.cpp</li>
-<li>results_reporter.cpp</li>
-<li>unit_test_log.cpp</li>
-<li>unit_test_main.cpp</li>
-<li>unit_test_monitor.cpp</li>
-<li>unit_test_parameters.cpp</li>
-<li>unit_test_suite.cpp</li>
-<li>xml_log_formatter.cpp</li>
-<li>xml_report_formatter.cpp</li>
+<div class="files-list"><ul type="disc">
+<li class="listitem">debug.cpp</li>
+<li class="listitem">compiler_log_formatter.cpp</li>
+<li class="listitem">exception_safety.cpp</li>
+<li class="listitem">execution_monitor.cpp</li>
+<li class="listitem">framework.cpp</li>
+<li class="listitem">interaction_based.cpp</li>
+<li class="listitem">logged_expectations.cpp</li>
+<li class="listitem">plain_report_formatter.cpp</li>
+<li class="listitem">progress_monitor.cpp</li>
+<li class="listitem">results_collector.cpp</li>
+<li class="listitem">results_reporter.cpp</li>
+<li class="listitem">unit_test_log.cpp</li>
+<li class="listitem">unit_test_main.cpp</li>
+<li class="listitem">unit_test_monitor.cpp</li>
+<li class="listitem">unit_test_parameters.cpp</li>
+<li class="listitem">unit_test_suite.cpp</li>
+<li class="listitem">xml_log_formatter.cpp</li>
+<li class="listitem">xml_report_formatter.cpp</li>
</ul></div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="utf.compilation.procedured"></a>Compilation procedures</h4></div></div></div>
<p class="first-line-indented">
@@ -81,11 +81,11 @@
a test module can be configured using the following compilation flags.
</p>
<div class="table">
-<a name="utf.compilation.flags"></a><p class="title"><b>Table 3. The <acronym class="acronym">UTF</acronym> compilation flags</b></p>
+<a name="utf.compilation.flags"></a><p class="title"><b>Table 3. The <acronym class="acronym">UTF</acronym> compilation flags</b></p>
<div class="table-contents"><table class="table" summary="The UTF compilation flags">
<colgroup>
-<col>
-<col>
+<col class="c1">
+<col class="c2">
</colgroup>
<thead><tr>
<th>Flag</th>
@@ -142,7 +142,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/compilation/auto-linking.html
==============================================================================
--- trunk/libs/test/doc/html/utf/compilation/auto-linking.html (original)
+++ trunk/libs/test/doc/html/utf/compilation/auto-linking.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Support of the auto-linking feature</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
<link rel="up" href="../compilation.html" title="The UTF compilation variants and procedures">
<link rel="prev" href="standalone.html" title="Standalone library compilation">
@@ -22,7 +22,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="utf.compilation.auto-linking"></a>Support of the auto-linking feature</h4></div></div></div>
<p class="first-line-indented">
@@ -35,7 +35,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/compilation/direct-include.html
==============================================================================
--- trunk/libs/test/doc/html/utf/compilation/direct-include.html (original)
+++ trunk/libs/test/doc/html/utf/compilation/direct-include.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Including the UTF directly into your test module</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
<link rel="up" href="../compilation.html" title="The UTF compilation variants and procedures">
<link rel="prev" href="auto-linking.html" title="Support of the auto-linking feature">
@@ -22,7 +22,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="utf.compilation.direct-include"></a>Including the <acronym class="acronym">UTF</acronym> directly into your test module</h4></div></div></div>
<p class="first-line-indented">
@@ -41,7 +41,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/compilation/standalone.html
==============================================================================
--- trunk/libs/test/doc/html/utf/compilation/standalone.html (original)
+++ trunk/libs/test/doc/html/utf/compilation/standalone.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Standalone library compilation</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
<link rel="up" href="../compilation.html" title="The UTF compilation variants and procedures">
<link rel="prev" href="../compilation.html" title="The UTF compilation variants and procedures">
@@ -22,20 +22,20 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="utf.compilation.standalone"></a>Standalone library compilation</h4></div></div></div>
<p class="first-line-indented">
If you opted to link your program with the standalone library, you need to build it first. To build a standalone
library the all C++ files (.cpp), that constitute <acronym class="acronym">UTF</acronym> <a class="link" href="../../prg-exec-monitor/impl.html" title="The Program Execution Monitor implementation">implementation</a> need to be
- listed as source files in your makefile<sup>[<a name="id646111" href="#ftn.id646111" class="footnote">3</a>]</sup>.
+ listed as source files in your makefile<sup>[<a name="id484832" href="#ftn.id484832" class="footnote">3</a>]</sup>.
</p>
<p class="first-line-indented">
The Jamfile for use with Boost.Build system is supplied in <code class="filename">libs/test/build</code>
directory. The <acronym class="acronym">UTF</acronym> can be built as either <a name="prg-exec-monitor.compilation.standalone.static"></a>static
or <a name="prg-exec-monitor.compilation.standalone.dynamic"></a>dynamic library.
</p>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.compilation.standalone.static"></a>Static library compilation</h5></div></div></div>
<p class="first-line-indented">
@@ -48,11 +48,11 @@
Also on Windows you can use the Microsoft Visual Studio .NET project file provided.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.compilation.standalone.dynamic"></a>Dynamic library compilation</h5></div></div></div>
<p class="first-line-indented">
- To build the dynamic library<sup>[<a name="id646262" href="#ftn.id646262" class="footnote">4</a>]</sup> you
+ To build the dynamic library<sup>[<a name="id484963" href="#ftn.id484963" class="footnote">4</a>]</sup> you
need to add <a class="xref" href="../compilation.html#utf.flag.dyn-link">BOOST_TEST_DYN_LINK</a> to the list of macro definitions in the
makefile. Using the Boost.Build system you can build the dynamic library with the following command from
<code class="filename">libs/test/build</code> directory:
@@ -75,19 +75,19 @@
</div>
<div class="footnotes">
<br><hr width="100" align="left">
-<div class="footnote"><p><sup>[<a name="ftn.id646111" href="#id646111" class="simpara">3</a>] </sup>There are varieties of make systems that can be used. To name
+<div class="footnote"><p><sup>[<a id="ftn.id484832" href="#id484832" class="simpara">3</a>] </sup>There are varieties of make systems that can be used. To name
a few: <acronym class="acronym">GNU</acronym> make (and other make clones) and build systems integrated into <acronym class="acronym">IDE</acronym>s
(for example Microsoft Visual Studio). The Boost preferred solution is Boost.Build system that is based on top of
bjam tool. Make systems require some kind of configuration file that lists all files that constitute the library
and all build options. For example the makefile that is used by make, or the Microsoft Visual Studio project file,
Jamfile is used by Boost.Build. For the sake of simplicity let's call this file the makefile.</p></div>
-<div class="footnote"><p><sup>[<a name="ftn.id646262" href="#id646262" class="simpara">4</a>] </sup>What is meant by the term dynamic library is a <em class="firstterm">dynamically
+<div class="footnote"><p><sup>[<a id="ftn.id484963" href="#id484963" class="simpara">4</a>] </sup>What is meant by the term dynamic library is a <em class="firstterm">dynamically
loaded library</em>, alternatively called a <em class="firstterm">shared library</em>.</p></div>
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/intro.html
==============================================================================
--- trunk/libs/test/doc/html/utf/intro.html (original)
+++ trunk/libs/test/doc/html/utf/intro.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Introduction</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
-<link rel="up" href="../utf.html" title="Part IV. Boost Test Library: The Unit Test Framework">
-<link rel="prev" href="../utf.html" title="Part IV. Boost Test Library: The Unit Test Framework">
+<link rel="up" href="../utf.html" title="Boost Test Library: The Unit Test Framework">
+<link rel="prev" href="../utf.html" title="Boost Test Library: The Unit Test Framework">
<link rel="next" href="tutorials.html" title="The unit test framework tutorials">
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
</head>
@@ -20,16 +20,16 @@
</div></td>
</tr></table>
<hr>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="utf.intro"></a>Introduction</h2></div></div></div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="utf.intro"></a>Introduction</h3></div></div></div>
<div class="epigraph">
<p>
The acceptance test makes the customer satisfied that the software provides the business value that makes them
willing to pay for it. The unit test makes the programmer satisfied that the software does what the programmer
thinks it does
</p>
-<div class="attribution"><span>--<span class="attribution">XP maxim</span></span></div>
+<div class="attribution"><span>—<span class="attribution">XP maxim</span></span></div>
</div>
<p class="first-line-indented">
What is the first thing you need to do when you start working on new library/class/program? That's right -
@@ -49,45 +49,45 @@
approached differently by different developers. The wide spectrum of tasks in a problem domain cause many
requirements (sometimes conflicting) to be placed on a unit testing framework. These include:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="square">
-<li style="list-style-type: square">
+<div class="itemizedlist"><ul type="square">
+<li class="listitem" style="list-style-type: square">
Writing a unit test module should be simple and obvious for new users.
</li>
-<li style="list-style-type: square">
+<li class="listitem" style="list-style-type: square">
The framework should allow advanced users to perform nontrivial tests.
</li>
-<li style="list-style-type: square">
+<li class="listitem" style="list-style-type: square">
Test module should be able to have many small test cases and developer should be able to group them into test
suites.
</li>
-<li style="list-style-type: square">
+<li class="listitem" style="list-style-type: square">
At the beginning of the development users want to see verbose and descriptive error message, whereas during the
regression testing they just want to know if any tests failed.
</li>
-<li style="list-style-type: square">
+<li class="listitem" style="list-style-type: square">
For a small test modules run time should prevail over compilation time: user don't want to wait a minute to
compile a test that takes a second to run.
</li>
-<li style="list-style-type: square">
+<li class="listitem" style="list-style-type: square">
For long and complex tests users want to be able to see the test progress.
</li>
-<li style="list-style-type: square">
+<li class="listitem" style="list-style-type: square">
Simplest tests shouldn't require an external library.
</li>
-<li style="list-style-type: square">
+<li class="listitem" style="list-style-type: square">
For long term usage users of a unit test framework should be able to build it as a standalone library.
</li>
</ul></div>
<p class="first-line-indented">
The <acronym class="acronym">UTF</acronym> design is based on above rationale and provides versatile facilities to:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="square">
-<li style="list-style-type: square">
+<div class="itemizedlist"><ul type="square">
+<li class="listitem" style="list-style-type: square">
Simplify writing test cases by using various <a class="link" href="testing-tools/reference.html" title="The UTF testing tools reference">testing tools</a>.
</li>
-<li style="list-style-type: square">
-<a class="link" href="user-guide/test-organization.html" title="Test organization or the house that Jack built">Organize test cases</a> into a test tree.</li>
-<li style="list-style-type: square">
+<li class="listitem" style="list-style-type: square">
+<a class="link" href="user-guide/test-organization.html" title="Test organization … or the house that Jack built">Organize test cases</a> into a test tree.</li>
+<li class="listitem" style="list-style-type: square">
Relieve you from messy error detection, reporting duties and framework runtime parameters processing.
</li>
</ul></div>
@@ -96,7 +96,7 @@
provides an ability to check the <a class="link" href="user-guide/test-output/test-progress.html" title="Test progress display">test progress</a>
and generates a <a class="link" href="user-guide/test-output/results-report.html" title="Test report output">result report</a> in several different
formats. The <acronym class="acronym">UTF</acronym> supplies command line test runners that initialize the framework and run the requested tests.
- Depending on the selected <a class="link" href="compilation.html#utf.compilation.flags" title="Table 3. The UTF compilation flags">compilation flags</a> the function main()
+ Depending on the selected <a class="link" href="compilation.html#utf.compilation.flags" title="Table 3. The UTF compilation flags">compilation flags</a> the function main()
default implementation, that invoke the supplied test runner, can be generated automatically as well.
</p>
<p class="first-line-indented">
@@ -109,12 +109,12 @@
simple, easy-to-use interfaces with limited customization options and advanced interfaces, which allow unit testing
to be fully customized. Accordingly the material provided in this documentation is split into two sections:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="upper-roman">
-<li style="list-style-type: upper-roman">
+<div class="itemizedlist"><ul type="upper-roman">
+<li class="listitem" style="list-style-type: upper-roman">
<a class="link" href="user-guide.html" title="Unit Test Framework: User's guide">The User's Guide</a>: covers all functionality that doesn't require
knowledge of the <acronym class="acronym">UTF</acronym> internals
</li>
-<li style="list-style-type: upper-roman">
+<li class="listitem" style="list-style-type: upper-roman">
<a href="../under_construction.html" target="_top">The Advanced User's Guide</a>: covers all implementation details
required for a user to understand the advanced customization options available in the <acronym class="acronym">UTF</acronym>, and for a user
interested in extending the testing framework.
@@ -127,7 +127,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/testing-tools.html
==============================================================================
--- trunk/libs/test/doc/html/utf/testing-tools.html (original)
+++ trunk/libs/test/doc/html/utf/testing-tools.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>The UTF testing tools or tester's toolbox for all occasions</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>The UTF testing tools … or tester's toolbox for all occasions</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
-<link rel="up" href="../utf.html" title="Part IV. Boost Test Library: The Unit Test Framework">
+<link rel="up" href="../utf.html" title="Boost Test Library: The Unit Test Framework">
<link rel="prev" href="user-guide/runtime-config/reference.html" title="Runtime parameters reference">
<link rel="next" href="testing-tools/output-test.html" title="Output testing tool">
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
@@ -22,9 +22,9 @@
</div></td>
</tr></table>
<hr>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="utf.testing-tools"></a>The <acronym class="acronym">UTF</acronym> testing tools or tester's toolbox for all occasions</h2></div></div></div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="utf.testing-tools"></a>The <acronym class="acronym">UTF</acronym> testing tools … or tester's toolbox for all occasions</h3></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
@@ -34,7 +34,7 @@
<dt>Reference</dt>
</dl>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="utf.testing-tools.intro"></a>Introduction</h4></div></div></div>
<p class="first-line-indented">
@@ -48,24 +48,24 @@
ways to detect and report errors. For list of all supplied testing tools and usage examples see the reference.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="utf.testing-tools.flavors"></a>Testing tools flavors</h4></div></div></div>
<p class="first-line-indented">
All the tools are supplied in three flavors(levels): <em class="firstterm">WARN</em>, <em class="firstterm">CHECK</em> and
<em class="firstterm">REQUIRE</em>. For example: <code class="computeroutput"><a class="link" href="testing-tools/reference.html" title="The UTF testing tools reference">BOOST_WARN_EQUAL</a></code>,
<code class="computeroutput"><a class="link" href="testing-tools/reference.html" title="The UTF testing tools reference">BOOST_CHECK_EQUAL</a></code>, <code class="computeroutput"><a class="link" href="testing-tools/reference.html" title="The UTF testing tools reference">BOOST_REQUIRE_EQUAL</a></code>. If an assertion designated by
- the tool passes, confirmation message can be printed in log output<sup>[<a name="id657740" href="#ftn.id657740" class="footnote">6</a>]</sup>. If an assertion designated by the tool failed, depending on the level following
- will happened<sup>[<a name="id657756" href="#ftn.id657756" class="footnote">7</a>]</sup>:
+ the tool passes, confirmation message can be printed in log output<sup>[<a name="id496257" href="#ftn.id496257" class="footnote">6</a>]</sup>. If an assertion designated by the tool failed, depending on the level following
+ will happened<sup>[<a name="id496274" href="#ftn.id496274" class="footnote">7</a>]</sup>:
</p>
<div class="table">
-<a name="utf.testing-tools.levels-diffs"></a><p class="title"><b>Table 5. Testing tools levels differences</b></p>
+<a name="utf.testing-tools.levels-diffs"></a><p class="title"><b>Table 5. Testing tools levels differences</b></p>
<div class="table-contents"><table class="table" summary="Testing tools levels differences">
<colgroup>
-<col>
-<col>
-<col>
-<col>
+<col class="col1">
+<col class="col2">
+<col class="col3">
+<col class="col4">
</colgroup>
<thead><tr>
<th>Level</th>
@@ -112,16 +112,16 @@
</div>
<div class="footnotes">
<br><hr width="100" align="left">
-<div class="footnote"><p><sup>[<a name="ftn.id657740" href="#id657740" class="simpara">6</a>] </sup>to manage what messages appear
+<div class="footnote"><p><sup>[<a id="ftn.id496257" href="#id496257" class="simpara">6</a>] </sup>to manage what messages appear
in the test log stream set the proper <a class="link" href="user-guide/test-output/test-log.html" title="Test log output">log
level</a></p></div>
-<div class="footnote"><p><sup>[<a name="ftn.id657756" href="#id657756" class="simpara">7</a>] </sup>in some cases log message can be slightly different to reflect failed tool
+<div class="footnote"><p><sup>[<a id="ftn.id496274" href="#id496274" class="simpara">7</a>] </sup>in some cases log message can be slightly different to reflect failed tool
specifics</p></div>
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="left"><p><small>Last revised: , at </small></p></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/testing-tools/custom-predicate.html
==============================================================================
--- trunk/libs/test/doc/html/utf/testing-tools/custom-predicate.html (original)
+++ trunk/libs/test/doc/html/utf/testing-tools/custom-predicate.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Custom predicate support</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
-<link rel="up" href="../testing-tools.html" title="The UTF testing tools or tester's toolbox for all occasions">
+<link rel="up" href="../testing-tools.html" title="The UTF testing tools … or tester's toolbox for all occasions">
<link rel="prev" href="output-test.html" title="Output testing tool">
<link rel="next" href="floating_point_comparison.html" title="Floating-point comparison algorithms">
<script language="JavaScript1.2" src="../../../js/boost-test.js"></script>
@@ -22,7 +22,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="utf.testing-tools.custom-predicate"></a>Custom predicate support</h4></div></div></div>
<p class="first-line-indented">
@@ -37,7 +37,7 @@
automatically in case of failure.
</p>
<div class="example">
-<a name="utf.testing-tools.custom-predicate.example30"></a><p class="title"><b>Example 36. Custom predicate support using BOOST_CHECK_PREDICATE</b></p>
+<a name="utf.testing-tools.custom-predicate.example30"></a><p class="title"><b>Example 36. Custom predicate support using BOOST_CHECK_PREDICATE</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -57,10 +57,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example30-output">> example
Running 1 test case...
@@ -85,7 +85,7 @@
error message is stored in public read-write property p_message.
</p>
<div class="example">
-<a name="utf.testing-tools.custom-predicate.example31"></a><p class="title"><b>Example 37. Custom predicate support using class predicate_result</b></p>
+<a name="utf.testing-tools.custom-predicate.example31"></a><p class="title"><b>Example 37. Custom predicate support using class predicate_result</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -120,10 +120,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example31-output">Running 1 test case...
test.cpp(28): error in "test_list_comparizon": check compare_lists( l1, l2 ) failed. Different sizes [2!=0]
@@ -136,7 +136,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/testing-tools/floating_point_comparison.html
==============================================================================
--- trunk/libs/test/doc/html/utf/testing-tools/floating_point_comparison.html (original)
+++ trunk/libs/test/doc/html/utf/testing-tools/floating_point_comparison.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Floating-point comparison algorithms</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
-<link rel="up" href="../testing-tools.html" title="The UTF testing tools or tester's toolbox for all occasions">
+<link rel="up" href="../testing-tools.html" title="The UTF testing tools … or tester's toolbox for all occasions">
<link rel="prev" href="custom-predicate.html" title="Custom predicate support">
<link rel="next" href="reference.html" title="The UTF testing tools reference">
<script language="JavaScript1.2" src="../../../js/boost-test.js"></script>
@@ -22,13 +22,13 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="utf.testing-tools.fpv-comparison"></a>Floating-point comparison algorithms</h4></div></div></div>
<p class="first-line-indented">
In most cases it is unreasonable to use an <code class="computeroutput">operator==(...)</code> for a floating-point values equality check.
The simple, absolute value comparison based, solution for a floating-point values <code class="varname">u</code>,
- <code class="varname">v</code> and a tolerance :
+ <code class="varname">v</code> and a tolerance ε:
</p>
<div class="equation">
<a name="utf.testing-tools.fpv-comparison.eq.1"></a><table class="table">
@@ -38,7 +38,7 @@
</colgroup>
<tbody><tr>
<td><div class="informalequation"><span class="mathphrase">
- |<code class="varname">u</code> <code class="varname">v</code>|
+ |<code class="varname">u</code> − <code class="varname">v</code>| ≤ ε
</span></div></td>
<td class="index">(<span class="bold"><strong>1</strong></span>)</td>
</tr></tbody>
@@ -57,14 +57,14 @@
</colgroup>
<tbody><tr>
<td><div class="informalequation"><span class="mathphrase">
- |<code class="varname">u</code> <code class="varname">v</code>| |<code class="varname">u</code>| |<code class="varname">u</code> <code class="varname">v</code>| |<code class="varname">v</code>|
+ |<code class="varname">u</code> − <code class="varname">v</code>| ≤ ε × |<code class="varname">u</code>| ∧ |<code class="varname">u</code> − <code class="varname">v</code>| ≤ ε × |<code class="varname">v</code>|
</span></div></td>
<td class="index">(<span class="bold"><strong>2</strong></span>)</td>
</tr></tbody>
</table>
</div>
<p>
- defines a <em class="firstterm">very close with tolerance </em> relationship between <code class="varname">u</code> and <code class="varname">v</code>
+ defines a <em class="firstterm">very close with tolerance ε</em> relationship between <code class="varname">u</code> and <code class="varname">v</code>
</p>
<div class="equation">
<a name="utf.testing-tools.fpv-comparison.eq.3"></a><table class="table">
@@ -74,20 +74,20 @@
</colgroup>
<tbody><tr>
<td><div class="informalequation"><span class="mathphrase">
- |<code class="varname">u</code> <code class="varname">v</code>| |<code class="varname">u</code>| |<code class="varname">u</code> <code class="varname">v</code>| |<code class="varname">v</code>|
+ |<code class="varname">u</code> − <code class="varname">v</code>| ≤ ε × |<code class="varname">u</code>| ∨ |<code class="varname">u</code> − <code class="varname">v</code>| ≤ ε × |<code class="varname">v</code>|
</span></div></td>
<td class="index">(<span class="bold"><strong>3</strong></span>)</td>
</tr></tbody>
</table>
</div>
<p>
- defines a <em class="firstterm">close enough with tolerance </em> relationship between <code class="varname">u</code> and <code class="varname">v</code>
+ defines a <em class="firstterm">close enough with tolerance ε</em> relationship between <code class="varname">u</code> and <code class="varname">v</code>
</p>
<p class="first-line-indented">
Both relationships are commutative but are not transitive. The relationship defined by inequations
(2) is stronger
that the relationship defined by inequations (3)
- (i.e. (2)
+ (i.e. (2) ⇒
(3)). Because of the multiplication in the right side
of inequations, that can cause an unwanted underflow condition, the implementation is using modified version of the
inequations (2) and
@@ -102,7 +102,7 @@
</colgroup>
<tbody><tr>
<td><div class="informalequation"><span class="mathphrase">
- |<code class="varname">u</code> <code class="varname">v</code>| |<code class="varname">u</code>| |<code class="varname">u</code> <code class="varname">v</code>| / |<code class="varname">v</code>|
+ |<code class="varname">u</code> − <code class="varname">v</code>| / |<code class="varname">u</code>| ≤ ε ∧ |<code class="varname">u</code> − <code class="varname">v</code>| / |<code class="varname">v</code>| ≤ ε
</span></div></td>
<td class="index">(<span class="bold"><strong>4</strong></span>)</td>
</tr></tbody>
@@ -116,7 +116,7 @@
</colgroup>
<tbody><tr>
<td><div class="informalequation"><span class="mathphrase">
- |<code class="varname">u</code> <code class="varname">v</code>| |<code class="varname">u</code>| |<code class="varname">u</code> <code class="varname">v</code>| / |<code class="varname">v</code>|
+ |<code class="varname">u</code> − <code class="varname">v</code>| / |<code class="varname">u</code>| ≤ ε ∨ |<code class="varname">u</code> − <code class="varname">v</code>| / |<code class="varname">v</code>| ≤ ε
</span></div></td>
<td class="index">(<span class="bold"><strong>5</strong></span>)</td>
</tr></tbody>
@@ -125,8 +125,8 @@
<p class="first-line-indented">
Checks based on equations (4) and
(5) are implemented by two predicates with
- alternative interfaces: binary predicate <code class="computeroutput">close_at_tolerance</code><sup>[<a name="id658995" href="#ftn.id658995" class="footnote">8</a>]</sup> and predicate with four arguments
- <code class="computeroutput">check_is_close</code><sup>[<a name="id659008" href="#ftn.id659008" class="footnote">9</a>]</sup>.
+ alternative interfaces: binary predicate <code class="computeroutput">close_at_tolerance</code><sup>[<a name="id497556" href="#ftn.id497556" class="footnote">8</a>]</sup> and predicate with four arguments
+ <code class="computeroutput">check_is_close</code><sup>[<a name="id497569" href="#ftn.id497569" class="footnote">9</a>]</sup>.
</p>
<p class="first-line-indented">
While equations (4) and
@@ -134,14 +134,14 @@
point comparison check over equation (1), they are
unusable for the test on closeness to zero. The later check is still might be useful in some cases and the <acronym class="acronym">UTF</acronym>
implements an algorithm based on equation (1) in
- binary predicate <code class="computeroutput">check_is_small</code><sup>[<a name="id659064" href="#ftn.id659064" class="footnote">10</a>]</sup>.
+ binary predicate <code class="computeroutput">check_is_small</code><sup>[<a name="id497633" href="#ftn.id497633" class="footnote">10</a>]</sup>.
</p>
<p class="first-line-indented">
On top of the generic, flexible predicates the <acronym class="acronym">UTF</acronym> implements macro based family of tools
<code class="computeroutput"><a class="link" href="reference.html" title="The UTF testing tools reference">BOOST_CHECK_CLOSE</a></code> and <code class="computeroutput"><a class="link" href="reference.html" title="The UTF testing tools reference">BOOST_CHECK_SMALL</a></code>. These tools limit the check
flexibility to strong-only checks, but automate failed check arguments reporting.
</p>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.testing-tools.fpv-comparison.tolerance-selection"></a>Tolerance selection considerations</h5></div></div></div>
<p class="first-line-indented">
@@ -151,23 +151,23 @@
The "relative rounding error" is the difference between the real and the floating point values in relation to real
value: |x-X|/|x|. The discrepancy between real and floating point value may be caused by several reasons:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>Type promotion</li>
-<li>Arithmetic operations</li>
-<li>Conversion from a decimal presentation to a binary presentation</li>
-<li>Non-arithmetic operation</li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">Type promotion</li>
+<li class="listitem">Arithmetic operations</li>
+<li class="listitem">Conversion from a decimal presentation to a binary presentation</li>
+<li class="listitem">Non-arithmetic operation</li>
</ul></div>
<p class="first-line-indented">
- The first two operations proved to have a relative rounding error that does not exceed
+ The first two operations proved to have a relative rounding error that does not exceed ½ ×
"machine epsilon value" for the appropriate floating point type (represented by
<code class="computeroutput">std::numeric_limits</code><FPT>::epsilon()). Conversion to binary presentation, sadly, does
- not have such requirement. So we can't assume that float 1.1 is close to real 1.1 with tolerance
- "machine epsilon value" for float (though for 11./10 we can). Non arithmetic operations either do not have a
+ not have such requirement. So we can't assume that float 1.1 is close to real 1.1 with tolerance ½
+ × "machine epsilon value" for float (though for 11./10 we can). Non arithmetic operations either do not have a
predicted upper limit relative rounding errors. Note that both arithmetic and non-arithmetic operations might also
produce others "non-rounding" errors, such as underflow/overflow, division-by-zero or 'operation errors'.
</p>
<p class="first-line-indented">
- All theorems about the upper limit of a rounding error, including that of epsilon, refer only to
+ All theorems about the upper limit of a rounding error, including that of ½ × epsilon, refer only to
the 'rounding' operation, nothing more. This means that the 'operation error', that is, the error incurred by the
operation itself, besides rounding, isn't considered. In order for numerical software to be able to actually
predict error bounds, the IEEE754 standard requires arithmetic operations to be 'correctly or exactly rounded'.
@@ -178,8 +178,8 @@
with unpredictable upper limits.
</p>
<p class="first-line-indented">
- At last be aware that epsilon rules are not transitive. In other words combination of two
- arithmetic operations may produce rounding error that significantly exceeds 2 epsilon. All
+ At last be aware that ½ × epsilon rules are not transitive. In other words combination of two
+ arithmetic operations may produce rounding error that significantly exceeds 2 × ½ × epsilon. All
in all there are no generic rules on how to select the tolerance and users need to apply common sense and domain/
problem specific knowledge to decide on tolerance value.
</p>
@@ -193,16 +193,16 @@
</p>
</div>
<div class="bibliography">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="bbl.fpv-comparison"></a>A floating-point comparison related references</h3></div></div></div>
+<div class="titlepage"><div><div><h5 class="title">
+<a name="bbl.fpv-comparison"></a>A floating-point comparison related references</h5></div></div></div>
<div class="bibliodiv">
<h3 class="title">
<a name="bbl.fpv-comparison.books"></a>Books</h3>
<div class="biblioentry">
-<a name="bbl.KnuthII"></a><p>[<abbr class="abbrev">KnuthII</abbr>] <span class="title"><i>The art of computer programming (vol II)</i>. </span><span class="author"><span class="firstname">Donald. E.</span> <span class="surname">Knuth</span>. </span><span class="copyright">Copyright © 1998 Addison-Wesley Longman, Inc.. </span><span class="isbn">0-201-89684-2. </span><span class="publisher"><span class="publishername">Addison-Wesley Professional; 3 edition. </span></span></p>
+<a name="bbl.KnuthII"></a><p>[<abbr class="abbrev">KnuthII</abbr>] <span class="title"><i>The art of computer programming (vol II)</i>. </span><span class="author"><span class="firstname">Donald. E.</span> <span class="surname">Knuth</span>. </span><span class="copyright">Copyright © 1998 Addison-Wesley Longman, Inc.. </span><span class="isbn">0-201-89684-2. </span><span class="publisher"><span class="publishername">Addison-Wesley Professional; 3 edition. </span></span></p>
</div>
<div class="biblioentry">
-<a name="bbl.Kulisch"></a><p>[<abbr class="abbrev">Kulisch</abbr>] <span class="biblioset"><i>Rounding near zero</i>. </span><span class="biblioset"><i>Advanced Arithmetic for the Digital Computer</i>. <span class="author"><span class="firstname">Ulrich W</span> <span class="surname">Kulisch</span>. </span><span class="copyright">Copyright © 2002 Springer, Inc.. </span><span class="isbn">0-201-89684-2. </span><span class="publisher"><span class="publishername">Springer; 1 edition. </span></span></span></p>
+<a name="bbl.Kulisch"></a><p>[<abbr class="abbrev">Kulisch</abbr>] <span class="biblioset"><i>Rounding near zero</i>. </span><span class="biblioset"><i>Advanced Arithmetic for the Digital Computer</i>. <span class="author"><span class="firstname">Ulrich W</span> <span class="surname">Kulisch</span>. </span><span class="copyright">Copyright © 2002 Springer, Inc.. </span><span class="isbn">0-201-89684-2. </span><span class="publisher"><span class="publishername">Springer; 1 edition. </span></span></span></p>
</div>
</div>
<div class="bibliodiv">
@@ -221,11 +221,11 @@
<h3 class="title">
<a name="bbl.fpv-comparison.publications"></a>Publications</h3>
<div class="biblioentry">
-<a name="bbl.Goldberg"></a><p>[<abbr class="abbrev">Goldberg</abbr>] <span class="biblioset">“What Every Computer Scientist Should Know About Floating-Point Arithmetic”. <span class="author"><span class="firstname">David</span> <span class="surname">Goldberg</span>. </span><span class="copyright">Copyright © 1991 Association for Computing Machinery, Inc.. </span><span class="pagenums">150-230. </span></span><span class="biblioset"><i>Computing Surveys</i>. <span class="issuenum">March. </span>.
+<a name="bbl.Goldberg"></a><p>[<abbr class="abbrev">Goldberg</abbr>] <span class="biblioset">“What Every Computer Scientist Should Know About Floating-Point Arithmetic”. <span class="author"><span class="firstname">David</span> <span class="surname">Goldberg</span>. </span><span class="copyright">Copyright © 1991 Association for Computing Machinery, Inc.. </span><span class="pagenums">150-230. </span></span><span class="biblioset"><i>Computing Surveys</i>. <span class="issuenum">March. </span>.
</span></p>
</div>
<div class="biblioentry">
-<a name="bbl.Langlois"></a><p>[<abbr class="abbrev">Langlois</abbr>] <span class="title"><i>From Rounding Error Estimation to Automatic Correction with Automatic Differentiation</i>. </span><span class="author"><span class="firstname">Philippe</span> <span class="surname">Langlois</span>. </span><span class="copyright">Copyright © 2000. </span><span class="issn">0249-6399. </span></p>
+<a name="bbl.Langlois"></a><p>[<abbr class="abbrev">Langlois</abbr>] <span class="title"><i>From Rounding Error Estimation to Automatic Correction with Automatic Differentiation</i>. </span><span class="author"><span class="firstname">Philippe</span> <span class="surname">Langlois</span>. </span><span class="copyright">Copyright © 2000. </span><span class="issn">0249-6399. </span></p>
</div>
<div class="biblioentry">
<a name="bbl.Kahan"></a><p>[<abbr class="abbrev">Kahan</abbr>] <span class="title"><i>Lots of information on William Kahan home page</i>. </span><span class="author"><span class="firstname">William</span> <span class="surname">Kahan</span>. </span></p>
@@ -234,16 +234,16 @@
</div>
<div class="footnotes">
<br><hr width="100" align="left">
-<div class="footnote"><p><sup>[<a name="ftn.id658995" href="#id658995" class="simpara">8</a>] </sup>check type
+<div class="footnote"><p><sup>[<a id="ftn.id497556" href="#id497556" class="simpara">8</a>] </sup>check type
and tolerance value are fixed at predicate construction time</p></div>
-<div class="footnote"><p><sup>[<a name="ftn.id659008" href="#id659008" class="simpara">9</a>] </sup>check type and tolerance value are the arguments of the
+<div class="footnote"><p><sup>[<a id="ftn.id497569" href="#id497569" class="simpara">9</a>] </sup>check type and tolerance value are the arguments of the
predicate</p></div>
-<div class="footnote"><p><sup>[<a name="ftn.id659064" href="#id659064" class="simpara">10</a>] </sup><code class="varname">v</code> is zero</p></div>
+<div class="footnote"><p><sup>[<a id="ftn.id497633" href="#id497633" class="simpara">10</a>] </sup><code class="varname">v</code> is zero</p></div>
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/testing-tools/output-test.html
==============================================================================
--- trunk/libs/test/doc/html/utf/testing-tools/output-test.html (original)
+++ trunk/libs/test/doc/html/utf/testing-tools/output-test.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Output testing tool</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
-<link rel="up" href="../testing-tools.html" title="The UTF testing tools or tester's toolbox for all occasions">
-<link rel="prev" href="../testing-tools.html" title="The UTF testing tools or tester's toolbox for all occasions">
+<link rel="up" href="../testing-tools.html" title="The UTF testing tools … or tester's toolbox for all occasions">
+<link rel="prev" href="../testing-tools.html" title="The UTF testing tools … or tester's toolbox for all occasions">
<link rel="next" href="custom-predicate.html" title="Custom predicate support">
<script language="JavaScript1.2" src="../../../js/boost-test.js"></script>
</head>
@@ -22,13 +22,13 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="utf.testing-tools.output-test"></a>Output testing tool</h4></div></div></div>
<p class="first-line-indented">
How do you perform correctness test for <code class="computeroutput">operator<<( std::ostream&, ... )</code>
operations? You can print into the standard output stream and manually check that it is matching your expectations.
- Unfortunately, this is not really acceptable for the regression testing and doesn't serve a ling term purpose of a
+ Unfortunately, this is not really acceptable for the regression testing and doesn't serve a long term purpose of a
unit test. You can use <code class="computeroutput">std::stringstream</code> and compare resulting output buffer with the
expected pattern string, but you are required to perform several additional operations with every check you do. So it
becomes tedious very fast. The class <em class="firstterm"><code class="computeroutput">output_test_stream</code></em> is designed to
@@ -36,12 +36,17 @@
<code class="computeroutput">std::ostream</code> based output operation. The class <code class="computeroutput">output_test_stream</code>
complies to <code class="computeroutput">std::ostream</code> interface so it can be used in place of any
<code class="computeroutput">std::ostream</code> parameter. It provides several test methods to validate output content,
- including test for match to expected output content or test for expected output length. Flushing, synchronizing,
+ including test for match to expected output content or test for expected output length. Flushing, synchronizing,
string comparison and error message generation is automated by the tool implementation.
</p>
<p class="first-line-indented">
- In some cases it still may not be good enough. It becomes even more obvious when it's difficult to generate the
- expected pattern. What we need in cases like this is to be able to check once manually that the output is as expected
+ All <code class="computeroutput">output_test_stream</code> validation methods by default flush the stream once check is performed.
+ If you want to perform several checks with the same output, specify parameter <em class="firstterm">flush_stream</em>
+ with value false. This parameter is supported on all comparison methods.
+ </p>
+<p class="first-line-indented">
+ In some cases manual generation of expected output is either too time consuming or is impossible at all bacause
+ of sheer volume. What we need in cases like this is to be able to check once manually that the output is as expected
and to be able in a future check that it stays the same. To help manage this logic the class
<code class="computeroutput">output_test_stream</code> allows matching output content versus specified pattern file and produce
pattern file based on successful test run.
@@ -49,7 +54,7 @@
<p class="first-line-indented">
Detailed specification of class <code class="computeroutput">output_test_stream</code> is covered in reference section.
</p>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.testing-tools.output-test.usage"></a>Usage</h5></div></div></div>
<p class="first-line-indented">
@@ -58,7 +63,7 @@
</p>
</div>
<div class="example">
-<a name="utf.testing-tools.output-test.example28"></a><p class="title"><b>Example 34. output_test_stream usage with explicit output checks</b></p>
+<a name="utf.testing-tools.output-test.example28"></a><p class="title"><b>Example 34. output_test_stream usage with explicit output checks</b></p>
<div class="example-contents">
<p class="first-line-indented">
Use the instance of class output_test_stream as an output stream and check output content using tool's methods.
@@ -87,10 +92,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example28-output">> example
Running 1 test case...
@@ -101,7 +106,7 @@
</div>
</div>
<br class="example-break"><div class="example">
-<a name="utf.testing-tools.output-test.example29"></a><p class="title"><b>Example 35. output_test_stream usage for pattern file matching</b></p>
+<a name="utf.testing-tools.output-test.example29"></a><p class="title"><b>Example 35. output_test_stream usage for pattern file matching</b></p>
<div class="example-contents">
<p class="first-line-indented">
Even simpler: no need to generate expected patterns. Though you need to keep the pattern file all the time somewhere
@@ -111,7 +116,7 @@
</p>
<p>
<div class="literallayout"><p>i=2<br>
-File: test.cpp Line: 14</p></div>
+File: test.cpp Line: 14</p></div>
</p>
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -133,10 +138,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example29-output">> example
Running 1 test case...
@@ -152,7 +157,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/testing-tools/reference.html
==============================================================================
--- trunk/libs/test/doc/html/utf/testing-tools/reference.html (original)
+++ trunk/libs/test/doc/html/utf/testing-tools/reference.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>The UTF testing tools reference</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
-<link rel="up" href="../testing-tools.html" title="The UTF testing tools or tester's toolbox for all occasions">
+<link rel="up" href="../testing-tools.html" title="The UTF testing tools … or tester's toolbox for all occasions">
<link rel="prev" href="floating_point_comparison.html" title="Floating-point comparison algorithms">
<link rel="next" href="../usage-recommendations.html" title="The unit test framework usage recommendations">
<script language="JavaScript1.2" src="../../../js/boost-test.js"></script>
@@ -22,33 +22,33 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="utf.testing-tools.reference"></a>The <acronym class="acronym">UTF</acronym> testing tools reference</h4></div></div></div>
<script language="JavaScript1.2">
- var id298906;
+ var id288015;
</script><table class="inline-reference"><tr>
<td class="index" valign="top"><ul>
-<li>BOOST_<level></li>
-<li>BOOST_<level>_BITWISE_EQUAL</li>
-<li>BOOST_<level>_CLOSE</li>
-<li>BOOST_<level>_CLOSE_FRACTION</li>
-<li>BOOST_<level>_EQUAL</li>
-<li>BOOST_<level>_EQUAL_COLLECTION</li>
-<li>BOOST_<level>_EXCEPTION</li>
-<li>BOOST_<level>_GE</li>
-<li>BOOST_<level>_GT</li>
-<li>BOOST_<level>_LE</li>
-<li>BOOST_<level>_LT</li>
-<li>BOOST_<level>_MESSAGE</li>
-<li>BOOST_<level>_NE</li>
-<li>BOOST_<level>_NO_THROW</li>
-<li>BOOST_<level>_PREDICATE</li>
-<li>BOOST_<level>_SMALL</li>
-<li>BOOST_<level>_THROW</li>
-<li>BOOST_ERROR</li>
-<li>BOOST_FAIL</li>
-<li>BOOST_IS_DEFINED</li>
+<li>BOOST_<level></li>
+<li>BOOST_<level>_BITWISE_EQUAL</li>
+<li>BOOST_<level>_CLOSE</li>
+<li>BOOST_<level>_CLOSE_FRACTION</li>
+<li>BOOST_<level>_EQUAL</li>
+<li>BOOST_<level>_EQUAL_COLLECTIONS</li>
+<li>BOOST_<level>_EXCEPTION</li>
+<li>BOOST_<level>_GE</li>
+<li>BOOST_<level>_GT</li>
+<li>BOOST_<level>_LE</li>
+<li>BOOST_<level>_LT</li>
+<li>BOOST_<level>_MESSAGE</li>
+<li>BOOST_<level>_NE</li>
+<li>BOOST_<level>_NO_THROW</li>
+<li>BOOST_<level>_PREDICATE</li>
+<li>BOOST_<level>_SMALL</li>
+<li>BOOST_<level>_THROW</li>
+<li>BOOST_ERROR</li>
+<li>BOOST_FAIL</li>
+<li>BOOST_IS_DEFINED</li>
</ul></td>
<td class="content" valign="top">
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>">
@@ -62,7 +62,7 @@
expression gets evaluated only once, so it's safe to pass complex expression for validation.
</p>
<div class="example">
-<a name=".example34"></a><p class="title"><b>Example 38. BOOST_<level> usage</b></p>
+<a name=".example34"></a><p class="title"><b>Example 38. BOOST_<level> usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -80,10 +80,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example34-output">> example --log_level=warning
Running 1 test case...
@@ -96,7 +96,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>_MESSAGE
+ BOOST_<level>_MESSAGE
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_BITWISE_EQUAL">
<pre class="inline-synopsis">
@@ -112,7 +112,7 @@
not required to be of the same type, but warning is issued if their type's size does not coincide.
</p>
<div class="example">
-<a name=".example33"></a><p class="title"><b>Example 39. BOOST_<level>_BITWISE_EQUAL usage</b></p>
+<a name=".example33"></a><p class="title"><b>Example 39. BOOST_<level>_BITWISE_EQUAL usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -126,10 +126,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example33-output">> example
Running 1 test case...
@@ -142,7 +142,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>_EQUAL
+ BOOST_<level>_EQUAL
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_CLOSE">
<pre class="inline-synopsis">
@@ -152,7 +152,7 @@
<p class="first-line-indented">
These tools are used to check on closeness using strong relationship defined by the predicate
<code class="computeroutput">check_is_close</code>( left, right, tolerance ). To check for the weak relationship use
- BOOST_<level>_PREDICATE family of tools with explicit <code class="computeroutput">check_is_close</code>
+ BOOST_<level>_PREDICATE family of tools with explicit <code class="computeroutput">check_is_close</code>
invocation.
</p>
<p>
@@ -180,7 +180,7 @@
</p></td></tr>
</table></div>
<div class="example">
-<a name=".example42"></a><p class="title"><b>Example 40. BOOST_<level>_CLOSE usage with very small values</b></p>
+<a name=".example42"></a><p class="title"><b>Example 40. BOOST_<level>_CLOSE usage with very small values</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -201,10 +201,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example42-output">> example
Running 1 test case...
@@ -215,7 +215,7 @@
</div>
</div>
<br class="example-break"><div class="example">
-<a name=".example43"></a><p class="title"><b>Example 41. BOOST_<level>_CLOSE usage with very big values</b></p>
+<a name=".example43"></a><p class="title"><b>Example 41. BOOST_<level>_CLOSE usage with very big values</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -236,10 +236,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example43-output">> example
Running 1 test case...
@@ -249,7 +249,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>_CLOSE_FRACTION, BOOST_<level>_SMALL, BOOST_<level>_EQUAL,
+ BOOST_<level>_CLOSE_FRACTION, BOOST_<level>_SMALL, BOOST_<level>_EQUAL,
<a class="link" href="floating_point_comparison.html" title="Floating-point comparison algorithms">Floating point comparison algorithms</a>
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_CLOSE_FRACTION">
@@ -260,13 +260,14 @@
<p class="first-line-indented">
These tools are used to check on closeness using strong relationship defined by the predicate
<code class="computeroutput">check_is_close</code>( left, right, tolerance ). To check for the weak relationship use
- BOOST_<level>_PREDICATE family of tools with explicit <code class="computeroutput">check_is_close</code>
+ BOOST_<level>_PREDICATE family of tools with explicit <code class="computeroutput">check_is_close</code>
invocation.
</p>
<p>
The first parameter is the <span class="emphasis"><em>left</em></span> compared value. The second parameter is the
- <span class="emphasis"><em>right</em></span> compared value. Last third parameter defines the tolerance for the comparison in
- <a class="link" href="floating_point_comparison.html#utf.testing-tools.fpv-comparison.tolerance-selection" title="Tolerance selection considerations"><span class="bold"><strong>percentage units</strong></span></a>.
+ <span class="emphasis"><em>right</em></span> compared value. Last third parameter defines the tolerance for the comparison as
+ <a class="link" href="floating_point_comparison.html#utf.testing-tools.fpv-comparison.tolerance-selection" title="Tolerance selection considerations"><span class="bold"><strong>fraction of absolute
+ values being compared</strong></span></a>.
</p>
<div class="note"><table border="0" summary="Note">
<tr>
@@ -288,7 +289,7 @@
</p></td></tr>
</table></div>
<div class="example">
-<a name=".example44"></a><p class="title"><b>Example 42. BOOST_<level>_CLOSE_FRACTION usage</b></p>
+<a name=".example44"></a><p class="title"><b>Example 42. BOOST_<level>_CLOSE_FRACTION usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -306,10 +307,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example44-output">> example
Running 1 test case...
@@ -320,7 +321,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>_CLOSE, BOOST_<level>_SMALL, BOOST_<level>_EQUAL,
+ BOOST_<level>_CLOSE, BOOST_<level>_SMALL, BOOST_<level>_EQUAL,
<a class="link" href="floating_point_comparison.html" title="Floating-point comparison algorithms">Floating point comparison algorithms</a>
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_EQUAL">
@@ -329,7 +330,7 @@
<a name="BOOST_CHECK_EQUAL"></a>BOOST_CHECK_EQUAL(<span class="emphasis"><em>left</em></span>, <span class="emphasis"><em>right</em></span>)
<a name="BOOST_REQUIRE_EQUAL"></a>BOOST_REQUIRE_EQUAL(<span class="emphasis"><em>left</em></span>, <span class="emphasis"><em>right</em></span>)</pre>
<p class="first-line-indented">
- Check performed by these tools is the same as the one performed by BOOST_<level>( left == right ).
+ Check performed by these tools is the same as the one performed by BOOST_<level>( left == right ).
The difference is that the mismatched values are reported as well.
</p>
<div class="note"><table border="0" summary="Note">
@@ -338,12 +339,12 @@
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top"><p>
- It is bad idea to use these tools to compare floating point values. Use BOOST_<level>_CLOSE or
- BOOST_<level>_CLOSE_FRACTION tools instead.
+ It is bad idea to use these tools to compare floating point values. Use BOOST_<level>_CLOSE or
+ BOOST_<level>_CLOSE_FRACTION tools instead.
</p></td></tr>
</table></div>
<div class="example">
-<a name=".example35"></a><p class="title"><b>Example 43. BOOST_<level>_EQUAL usage</b></p>
+<a name=".example35"></a><p class="title"><b>Example 43. BOOST_<level>_EQUAL usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -359,10 +360,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example35-output">> example
Running 1 test case...
@@ -373,13 +374,13 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>, BOOST_<level>_CLOSE, BOOST_<level>_NE
+ BOOST_<level>, BOOST_<level>_CLOSE, BOOST_<level>_NE
</div>
-<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_EQUAL_COLLECTION">
+<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_EQUAL_COLLECTIONS">
<pre class="inline-synopsis">
-<a name="BOOST_WARN_EQUAL_COLLECTION"></a>BOOST_WARN_EQUAL_COLLECTION(<span class="emphasis"><em>left_begin</em></span>, <span class="emphasis"><em>left_end</em></span>, <span class="emphasis"><em>right_begin</em></span>, <span class="emphasis"><em>right_end</em></span>)
-<a name="BOOST_CHECK_EQUAL_COLLECTION"></a>BOOST_CHECK_EQUAL_COLLECTION(<span class="emphasis"><em>left_begin</em></span>, <span class="emphasis"><em>left_end</em></span>, <span class="emphasis"><em>right_begin</em></span>, <span class="emphasis"><em>right_end</em></span>)
-<a name="BOOST_REQUIRE_EQUAL_COLLECTION"></a>BOOST_REQUIRE_EQUAL_COLLECTION(<span class="emphasis"><em>left_begin</em></span>, <span class="emphasis"><em>left_end</em></span>, <span class="emphasis"><em>right_begin</em></span>, <span class="emphasis"><em>right_end</em></span>)</pre>
+<a name="BOOST_WARN_EQUAL_COLLECTIONS"></a>BOOST_WARN_EQUAL_COLLECTIONS(<span class="emphasis"><em>left_begin</em></span>, <span class="emphasis"><em>left_end</em></span>, <span class="emphasis"><em>right_begin</em></span>, <span class="emphasis"><em>right_end</em></span>)
+<a name="BOOST_CHECK_EQUAL_COLLECTIONS"></a>BOOST_CHECK_EQUAL_COLLECTIONS(<span class="emphasis"><em>left_begin</em></span>, <span class="emphasis"><em>left_end</em></span>, <span class="emphasis"><em>right_begin</em></span>, <span class="emphasis"><em>right_end</em></span>)
+<a name="BOOST_REQUIRE_EQUAL_COLLECTIONS"></a>BOOST_REQUIRE_EQUAL_COLLECTIONS(<span class="emphasis"><em>left_begin</em></span>, <span class="emphasis"><em>left_end</em></span>, <span class="emphasis"><em>right_begin</em></span>, <span class="emphasis"><em>right_end</em></span>)</pre>
<p class="first-line-indented">
These tools are used to perform an element by element comparison of two collections. They print all mismatched
positions, collection elements at these positions and check that the collections have the same size. The first two
@@ -387,7 +388,7 @@
second collection.
</p>
<div class="example">
-<a name=".example36"></a><p class="title"><b>Example 44. BOOST_<level>_EQUAL_COLLECTION usage</b></p>
+<a name=".example36"></a><p class="title"><b>Example 44. BOOST_<level>_EQUAL_COLLECTIONS usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -404,10 +405,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example36-output">> example
Running 1 test case...
@@ -420,7 +421,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>_EQUAL
+ BOOST_<level>_EQUAL
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_EXCEPTION">
<pre class="inline-synopsis">
@@ -431,12 +432,12 @@
These tools are used to perform an exception detection and validation check. Tools execute the supplied expression
and validate that it throws an exception of supplied class (or the one derived from it) that complies with the
supplied predicate. If the expression throws any other unrelated exception, doesn't throw at all or
- predicate evaluates to false, check fails. In comparison with BOOST_<level>_THROW tools these
+ predicate evaluates to false, check fails. In comparison with BOOST_<level>_THROW tools these
allow performing more fine-grained checks. For example: make sure that an expected exception has specific
error message.
</p>
<div class="example">
-<a name=".example37"></a><p class="title"><b>Example 45. BOOST_<level>_EXCEPTION usage</b></p>
+<a name=".example37"></a><p class="title"><b>Example 45. BOOST_<level>_EXCEPTION usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -458,10 +459,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example37-output">> example
Running 1 test case...
@@ -472,7 +473,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>_THROW
+ BOOST_<level>_THROW
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_GE">
<pre class="inline-synopsis">
@@ -480,11 +481,11 @@
<a name="BOOST_CHECK_GE"></a>BOOST_CHECK_GE(<span class="emphasis"><em>left</em></span>, <span class="emphasis"><em>right</em></span>)
<a name="BOOST_REQUIRE_GE"></a>BOOST_REQUIRE_GE(<span class="emphasis"><em>left</em></span>, <span class="emphasis"><em>right</em></span>)</pre>
<p class="first-line-indented">
- Check performed by these tools is the same as the one performed by BOOST_<level>( left >= right ).
+ Check performed by these tools is the same as the one performed by BOOST_<level>( left >= right ).
The difference is that the argument values are reported as well.
</p>
<div class="example">
-<a name=".example57"></a><p class="title"><b>Example 46. BOOST_<level>_GE usage</b></p>
+<a name=".example57"></a><p class="title"><b>Example 46. BOOST_<level>_GE usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -500,10 +501,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example57-output">>example
Running 1 test case...
@@ -514,7 +515,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>_LE, BOOST_<level>_LT, BOOST_<level>_GT
+ BOOST_<level>_LE, BOOST_<level>_LT, BOOST_<level>_GT
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_GT">
<pre class="inline-synopsis">
@@ -522,11 +523,11 @@
<a name="BOOST_CHECK_GT"></a>BOOST_CHECK_GT(<span class="emphasis"><em>left</em></span>, <span class="emphasis"><em>right</em></span>)
<a name="BOOST_REQUIRE_GT"></a>BOOST_REQUIRE_GT(<span class="emphasis"><em>left</em></span>, <span class="emphasis"><em>right</em></span>)</pre>
<p class="first-line-indented">
- Check performed by these tools is the same as the one performed by BOOST_<level>( left >= right ).
+ Check performed by these tools is the same as the one performed by BOOST_<level>( left > right ).
The difference is that the argument values are reported as well.
</p>
<div class="example">
-<a name=".example58"></a><p class="title"><b>Example 47. BOOST_<level>_GT usage</b></p>
+<a name=".example58"></a><p class="title"><b>Example 47. BOOST_<level>_GT usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -542,10 +543,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example58-output">>example
Running 1 test case...
@@ -556,7 +557,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>_LE, BOOST_<level>_LT, BOOST_<level>_GE
+ BOOST_<level>_LE, BOOST_<level>_LT, BOOST_<level>_GE
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_LE">
<pre class="inline-synopsis">
@@ -564,11 +565,11 @@
<a name="BOOST_CHECK_LE"></a>BOOST_CHECK_LE(<span class="emphasis"><em>left</em></span>, <span class="emphasis"><em>right</em></span>)
<a name="BOOST_REQUIRE_LE"></a>BOOST_REQUIRE_LE(<span class="emphasis"><em>left</em></span>, <span class="emphasis"><em>right</em></span>)</pre>
<p class="first-line-indented">
- Check performed by these tools is the same as the one performed by BOOST_<level>( left <= right ).
+ Check performed by these tools is the same as the one performed by BOOST_<level>( left <= right ).
The difference is that the argument values are reported as well.
</p>
<div class="example">
-<a name=".example55"></a><p class="title"><b>Example 48. BOOST_<level>_LE usage</b></p>
+<a name=".example55"></a><p class="title"><b>Example 48. BOOST_<level>_LE usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -584,10 +585,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example55-output">>example
Running 1 test case...
@@ -598,7 +599,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>_LT, BOOST_<level>_GE, BOOST_<level>_GT
+ BOOST_<level>_LT, BOOST_<level>_GE, BOOST_<level>_GT
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_LT">
<pre class="inline-synopsis">
@@ -606,11 +607,11 @@
<a name="BOOST_CHECK_LT"></a>BOOST_CHECK_LT(<span class="emphasis"><em>left</em></span>, <span class="emphasis"><em>right</em></span>)
<a name="BOOST_REQUIRE_LT"></a>BOOST_REQUIRE_LT(<span class="emphasis"><em>left</em></span>, <span class="emphasis"><em>right</em></span>)</pre>
<p class="first-line-indented">
- Check performed by these tools is the same as the one performed by BOOST_<level>( left < right ).
+ Check performed by these tools is the same as the one performed by BOOST_<level>( left < right ).
The difference is that the argument values are reported as well.
</p>
<div class="example">
-<a name=".example56"></a><p class="title"><b>Example 49. BOOST_<level>_LT usage</b></p>
+<a name=".example56"></a><p class="title"><b>Example 49. BOOST_<level>_LT usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -626,10 +627,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example56-output">>example
Running 1 test case...
@@ -640,7 +641,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>_LE, BOOST_<level>_GE, BOOST_<level>_GT
+ BOOST_<level>_LE, BOOST_<level>_GE, BOOST_<level>_GT
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_MESSAGE">
<pre class="inline-synopsis">
@@ -648,7 +649,7 @@
<a name="BOOST_CHECK_MESSAGE"></a>BOOST_CHECK_MESSAGE(<span class="emphasis"><em>predicate</em></span>, <span class="emphasis"><em>message</em></span>)
<a name="BOOST_REQUIRE_MESSAGE"></a>BOOST_REQUIRE_MESSAGE(<span class="emphasis"><em>predicate</em></span>, <span class="emphasis"><em>message</em></span>)</pre>
<p class="first-line-indented">
- These tools perform exactly the same check as BOOST_<level> tools. The only difference is that
+ These tools perform exactly the same check as BOOST_<level> tools. The only difference is that
instead of generating an error/confirm message these use the supplied one.
</p>
<p>
@@ -657,7 +658,7 @@
<code class="computeroutput">std::ostream& operator<<(std::ostream&)</code>.
</p>
<div class="example">
-<a name=".example38"></a><p class="title"><b>Example 50. BOOST_<level>_MESSAGE usage</b></p>
+<a name=".example38"></a><p class="title"><b>Example 50. BOOST_<level>_MESSAGE usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -675,10 +676,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example38-output">> example --log_level=warning
Running 1 test case...
@@ -688,7 +689,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>
+ BOOST_<level>
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_NE">
<pre class="inline-synopsis">
@@ -696,11 +697,11 @@
<a name="BOOST_CHECK_NE"></a>BOOST_CHECK_NE(<span class="emphasis"><em>left</em></span>, <span class="emphasis"><em>right</em></span>)
<a name="BOOST_REQUIRE_NE"></a>BOOST_REQUIRE_NE(<span class="emphasis"><em>left</em></span>, <span class="emphasis"><em>right</em></span>)</pre>
<p class="first-line-indented">
- Check performed by these tools is the same as the one performed by BOOST_<level>( left != right ).
+ Check performed by these tools is the same as the one performed by BOOST_<level>( left != right ).
The difference is that the matched values are reported as well.
</p>
<div class="example">
-<a name=".example54"></a><p class="title"><b>Example 51. BOOST_<level>_NE usage</b></p>
+<a name=".example54"></a><p class="title"><b>Example 51. BOOST_<level>_NE usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -716,10 +717,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example54-output">>example
Running 1 test case...
@@ -730,7 +731,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>_EQUAL
+ BOOST_<level>_EQUAL
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_NO_THROW">
<pre class="inline-synopsis">
@@ -751,7 +752,7 @@
statement.
</p>
<div class="example">
-<a name=".example39"></a><p class="title"><b>Example 52. BOOST_<level>_NO_THROW usage</b></p>
+<a name=".example39"></a><p class="title"><b>Example 52. BOOST_<level>_NO_THROW usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -767,10 +768,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example39-output">> example
Running 1 test case...
@@ -780,7 +781,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>_THROW
+ BOOST_<level>_THROW
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_PREDICATE">
<pre class="inline-synopsis">
@@ -790,7 +791,7 @@
<p class="first-line-indented">
These are generic tools used to validate an arbitrary supplied predicate functor (there is a compile time limit on
predicate arity defined by the configurable macro <code class="computeroutput">BOOST_TEST_MAX_PREDICATE_ARITY</code>). To
- validate zero arity predicate use BOOST_<level> tools. In other cases prefer theses tools. The
+ validate zero arity predicate use BOOST_<level> tools. In other cases prefer theses tools. The
advantage of these tools is that they show arguments values in case of predicate failure.
</p>
<p>
@@ -798,7 +799,7 @@
in round brackets (BOOST_PP sequence format).
</p>
<div class="example">
-<a name=".example40"></a><p class="title"><b>Example 53. BOOST_<level>_PREDICATE usage</b></p>
+<a name=".example40"></a><p class="title"><b>Example 53. BOOST_<level>_PREDICATE usage</b></p>
<div class="example-contents">
<p>
Note difference in error log from
@@ -822,10 +823,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example40-output">> example
Running 1 test case...
@@ -836,7 +837,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>
+ BOOST_<level>
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_SMALL">
<pre class="inline-synopsis">
@@ -846,7 +847,7 @@
<p class="first-line-indented">
These tools are used to check that supplied value is small enough. The "smallness" is defined by absolute value
of the tolerance supplied as a second argument. Use these tools with caution. To compare to values on closeness
- it's preferable to use BOOST_<level>_CLOSE tools instead.
+ it's preferable to use BOOST_<level>_CLOSE tools instead.
</p>
<p class="first-line-indented">
The first parameter is the value to check. The second parameter is the tolerance.
@@ -861,7 +862,7 @@
</p></td></tr>
</table></div>
<div class="example">
-<a name=".example41"></a><p class="title"><b>Example 54. BOOST_<level>_SMALL usage</b></p>
+<a name=".example41"></a><p class="title"><b>Example 54. BOOST_<level>_SMALL usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -878,10 +879,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example41-output">> example
Running 1 test case...
@@ -892,7 +893,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>_CLOSE, BOOST_<level>_CLOSE_FRACTION,
+ BOOST_<level>_CLOSE, BOOST_<level>_CLOSE_FRACTION,
<a class="link" href="floating_point_comparison.html" title="Floating-point comparison algorithms">Floating point comparison algorithms</a>
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_<level>_THROW">
@@ -914,7 +915,7 @@
statement. The second parameter is an expected exception.
</p>
<div class="example">
-<a name=".example45"></a><p class="title"><b>Example 55. BOOST_<level>_THROW usage</b></p>
+<a name=".example45"></a><p class="title"><b>Example 55. BOOST_<level>_THROW usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -931,10 +932,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example45-output">> example
Running 1 test case...
@@ -944,7 +945,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>NO_THROW
+ BOOST_<level>NO_THROW
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_ERROR">
<pre class="inline-synopsis">
@@ -957,7 +958,7 @@
The only tool's parameter is an error message to log.
</p>
<div class="example">
-<a name=".example46"></a><p class="title"><b>Example 56. BOOST_ERROR usage</b></p>
+<a name=".example46"></a><p class="title"><b>Example 56. BOOST_ERROR usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -971,10 +972,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example46-output">> example
Running 1 test case...
@@ -984,7 +985,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>
+ BOOST_<level>
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_FAIL">
<pre class="inline-synopsis">
@@ -997,7 +998,7 @@
The only tool's parameter is an error message to log.
</p>
<div class="example">
-<a name=".example47"></a><p class="title"><b>Example 57. BOOST_FAIL usage</b></p>
+<a name=".example47"></a><p class="title"><b>Example 57. BOOST_FAIL usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -1011,10 +1012,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example47-output">> example
Running 1 test case...
@@ -1024,7 +1025,7 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>
+ BOOST_<level>
</div>
<div class="entry" id="utf.testing-tools.reference.body.BOOST_IS_DEFINED">
<pre class="inline-synopsis">
@@ -1032,14 +1033,14 @@
<p class="first-line-indented">
Unlike the rest of the tools in the toolbox this tool does not perform the logging itself. Its only purpose
is to check at runtime whether or not the supplied preprocessor symbol is defined. Use it in combination with
- BOOST_<level> to perform and log validation. Macros of any arity could be checked. To check the
+ BOOST_<level> to perform and log validation. Macros of any arity could be checked. To check the
macro definition with non-zero arity specify dummy arguments for it. See below for example.
</p>
<p>
The only tool's parameter is a preprocessor symbol that gets validated.
</p>
<div class="example">
-<a name=".example48"></a><p class="title"><b>Example 58. BOOST_IS_DEFINED usage</b></p>
+<a name=".example48"></a><p class="title"><b>Example 58. BOOST_IS_DEFINED usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -1054,10 +1055,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example48-output">> example
Running 1 test case...
@@ -1068,14 +1069,14 @@
</div>
</div>
<br class="example-break"><span class="inline-ref-see-also">See also: </span>
- BOOST_<level>
+ BOOST_<level>
</div>
</td>
</tr></table>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/tutorials.html
==============================================================================
--- trunk/libs/test/doc/html/utf/tutorials.html (original)
+++ trunk/libs/test/doc/html/utf/tutorials.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>The unit test framework tutorials</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
-<link rel="up" href="../utf.html" title="Part IV. Boost Test Library: The Unit Test Framework">
+<link rel="up" href="../utf.html" title="Boost Test Library: The Unit Test Framework">
<link rel="prev" href="intro.html" title="Introduction">
-<link rel="next" href="../tutorials/intro-in-testing.html" title="Introduction into testing or why testing is worth the effort">
+<link rel="next" href="../tutorials/intro-in-testing.html" title="Introduction into testing … or why testing is worth the effort">
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,9 +22,9 @@
</div></td>
</tr></table>
<hr>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="utf.tutorials"></a>The unit test framework tutorials</h2></div></div></div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="utf.tutorials"></a>The unit test framework tutorials</h3></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
@@ -40,7 +40,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/usage-recommendations.html
==============================================================================
--- trunk/libs/test/doc/html/utf/usage-recommendations.html (original)
+++ trunk/libs/test/doc/html/utf/usage-recommendations.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>The unit test framework usage recommendations</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
-<link rel="up" href="../utf.html" title="Part IV. Boost Test Library: The Unit Test Framework">
+<link rel="up" href="../utf.html" title="Boost Test Library: The Unit Test Framework">
<link rel="prev" href="testing-tools/reference.html" title="The UTF testing tools reference">
<link rel="next" href="usage-recommendations/generic.html" title="Generic usage recommendations">
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
@@ -20,9 +20,9 @@
</div></td>
</tr></table>
<hr>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="utf.usage-recommendations"></a>The unit test framework usage recommendations</h2></div></div></div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="utf.usage-recommendations"></a>The unit test framework usage recommendations</h3></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
@@ -38,7 +38,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/usage-recommendations/command-line-specific.html
==============================================================================
--- trunk/libs/test/doc/html/utf/usage-recommendations/command-line-specific.html (original)
+++ trunk/libs/test/doc/html/utf/usage-recommendations/command-line-specific.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Command line usage recommendations</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
<link rel="up" href="../usage-recommendations.html" title="The unit test framework usage recommendations">
<link rel="prev" href="dot-net-specific.html" title="Microsoft Visual Studio .NET usage recommendations">
@@ -17,27 +17,28 @@
<td><div class="spirit-nav">
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="utf.usage-recommendations.command-line-specific"></a>Command line usage recommendations</h4></div></div></div>
<div class="qandaset">
-<dl>
-<dt> <a href="command-line-specific.html#id663841">
+<a name="id502450"></a><dl>
+<dt> <a href="command-line-specific.html#id502454">
If you got fatal exception somewhere within test case, make program generate coredump by adding extra command
line argument
</a>
</dt>
-<dt> <a href="command-line-specific.html#id663872">
+<dt> <a href="command-line-specific.html#id502485">
How to use test module build with Boost.Test framework under management of automated regression test facilities?
</a>
</dt>
</dl>
-<table border="0" summary="Q and A Set">
+<table border="0" width="100%" summary="Q and A Set">
<col align="left" width="1%">
+<col>
<tbody>
<tr class="question">
<td align="left" valign="top">
-<a name="id663841"></a><a name="id663843"></a>
+<a name="id502454"></a><a name="id502456"></a>
</td>
<td align="left" valign="top"><b><p>
If you got fatal exception somewhere within test case, make program generate coredump by adding extra command
@@ -55,7 +56,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id663872"></a><a name="id663874"></a>
+<a name="id502485"></a><a name="id502487"></a>
</td>
<td align="left" valign="top"><b><p>
How to use test module build with Boost.Test framework under management of automated regression test facilities?
@@ -81,7 +82,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/usage-recommendations/dot-net-specific.html
==============================================================================
--- trunk/libs/test/doc/html/utf/usage-recommendations/dot-net-specific.html (original)
+++ trunk/libs/test/doc/html/utf/usage-recommendations/dot-net-specific.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Microsoft Visual Studio .NET usage recommendations</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
<link rel="up" href="../usage-recommendations.html" title="The unit test framework usage recommendations">
<link rel="prev" href="generic.html" title="Generic usage recommendations">
@@ -20,27 +20,28 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="utf.usage-recommendations.dot-net-specific"></a>Microsoft Visual Studio .NET usage recommendations</h4></div></div></div>
<div class="qandaset">
-<dl>
-<dt> <a href="dot-net-specific.html#id663663">
+<a name="id502271"></a><dl>
+<dt> <a href="dot-net-specific.html#id502276">
Use custom build step to automatically start test program after compilation
</a>
</dt>
-<dt> <a href="dot-net-specific.html#id663766">
+<dt> <a href="dot-net-specific.html#id502379">
If you got fatal exception somewhere within test case, make debugger break at the point the failure by adding
extra command line argument
</a>
</dt>
</dl>
-<table border="0" summary="Q and A Set">
+<table border="0" width="100%" summary="Q and A Set">
<col align="left" width="1%">
+<col>
<tbody>
<tr class="question">
<td align="left" valign="top">
-<a name="id663663"></a><a name="id663665"></a>
+<a name="id502276"></a><a name="id502278"></a>
</td>
<td align="left" valign="top"><b><p>
Use custom build step to automatically start test program after compilation
@@ -68,7 +69,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id663766"></a><a name="id663768"></a>
+<a name="id502379"></a><a name="id502381"></a>
</td>
<td align="left" valign="top"><b><p>
If you got fatal exception somewhere within test case, make debugger break at the point the failure by adding
@@ -95,7 +96,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/usage-recommendations/generic.html
==============================================================================
--- trunk/libs/test/doc/html/utf/usage-recommendations/generic.html (original)
+++ trunk/libs/test/doc/html/utf/usage-recommendations/generic.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Generic usage recommendations</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
<link rel="up" href="../usage-recommendations.html" title="The unit test framework usage recommendations">
<link rel="prev" href="../usage-recommendations.html" title="The unit test framework usage recommendations">
@@ -20,39 +20,40 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="utf.usage-recommendations.generic"></a>Generic usage recommendations</h4></div></div></div>
<div class="qandaset">
-<dl>
-<dt> <a href="generic.html#id663440">
+<a name="id502066"></a><dl>
+<dt> <a href="generic.html#id502070">
Prefer offline compiled libraries to the inline included components
</a>
</dt>
-<dt> <a href="generic.html#id663471">
+<dt> <a href="generic.html#id502093">
If you use only free function based test cases advance to the automatic registration facility
</a>
</dt>
-<dt> <a href="generic.html#id663496">
+<dt> <a href="generic.html#id502118">
To find location of first error reported by test tool within reused template function, use special hook within
framework headers
</a>
</dt>
-<dt> <a href="generic.html#id663542">
+<dt> <a href="generic.html#id502164">
To test reusable template base component with different template parameter use test case template facility
</a>
</dt>
-<dt> <a href="generic.html#id663600">
+<dt> <a href="generic.html#id502222">
Prefer BOOST_CHECK_EQUAL to BOOST_CHECK
</a>
</dt>
</dl>
-<table border="0" summary="Q and A Set">
+<table border="0" width="100%" summary="Q and A Set">
<col align="left" width="1%">
+<col>
<tbody>
<tr class="question">
<td align="left" valign="top">
-<a name="id663440"></a><a name="id663443"></a>
+<a name="id502070"></a><a name="id502073"></a>
</td>
<td align="left" valign="top"><b><p>
Prefer offline compiled libraries to the inline included components
@@ -69,7 +70,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id663471"></a><a name="id663473"></a>
+<a name="id502093"></a><a name="id502095"></a>
</td>
<td align="left" valign="top"><b><p>
If you use only free function based test cases advance to the automatic registration facility
@@ -84,7 +85,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id663496"></a><a name="id663498"></a>
+<a name="id502118"></a><a name="id502120"></a>
</td>
<td align="left" valign="top"><b><p>
To find location of first error reported by test tool within reused template function, use special hook within
@@ -105,7 +106,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id663542"></a><a name="id663545"></a>
+<a name="id502164"></a><a name="id502166"></a>
</td>
<td align="left" valign="top"><b><p>
To test reusable template base component with different template parameter use test case template facility
@@ -144,7 +145,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="id663600"></a><a name="id663603"></a>
+<a name="id502222"></a><a name="id502225"></a>
</td>
<td align="left" valign="top"><b><p>
Prefer BOOST_CHECK_EQUAL to BOOST_CHECK
@@ -166,7 +167,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Unit Test Framework: User's guide</title>
<link rel="stylesheet" href="../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../index.html" title="Boost Test Library">
-<link rel="up" href="../utf.html" title="Part IV. Boost Test Library: The Unit Test Framework">
+<link rel="up" href="../utf.html" title="Boost Test Library: The Unit Test Framework">
<link rel="prev" href="compilation/direct-include.html" title="Including the UTF directly into your test module">
-<link rel="next" href="user-guide/usage-variants.html" title="The UTF usage variants or the Buridan's donkey parable">
+<link rel="next" href="user-guide/usage-variants.html" title="The UTF usage variants … or the Buridan's donkey parable">
<script language="JavaScript1.2" src="../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,9 +22,9 @@
</div></td>
</tr></table>
<hr>
-<div class="chapter" lang="en">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="utf.user-guide"></a>Unit Test Framework: User's guide</h2></div></div></div>
+<div class="section">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="utf.user-guide"></a>Unit Test Framework: User's guide</h3></div></div></div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
@@ -73,7 +73,7 @@
<dt>BOOST_TEST_MESSAGE</dt>
<dt>BOOST_TEST_CHECKPOINT</dt>
<dt>BOOST_TEST_PASSPOINT</dt>
-<dt>Logging floating point type numbers</dt>
+<dt>Logging floating point type numbers</dt>
<dt>Human readable format</dt>
<dt>XML based log output format</dt>
<dt>Compile time configuration</dt>
@@ -88,9 +88,9 @@
</dl>
</dl>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="utf.user-guide.intro"></a>Introduction or what's your name?</h4></div></div></div>
+<a name="utf.user-guide.intro"></a>Introduction … or what's your name?</h4></div></div></div>
<p class="first-line-indented">
Without further ado, let's define terms regularly used by the <acronym class="acronym">UTF</acronym>.
</p>
@@ -137,11 +137,11 @@
<tr>
<td><p><a name="test-assertion.def"></a><span class="term"><em class="firstterm">Test assertion</em></span></p></td>
<td>
-<p>
+<p class="simpara">
This is a single binary condition (binary in a sense that is has two outcomes: pass and fail) checked
by a test module.
</p>
-<p>
+<p class="simpara">
There are different schools of thought on how many test assertions a test case should consist of. Two polar
positions are the one advocated by TDD followers - one assertion per test case; and opposite of this - all test
assertions within single test case - advocated by those only interested in the first error in a
@@ -163,18 +163,18 @@
<tr>
<td><p><a name="test-suite.def"></a><span class="term"><em class="firstterm">The test suite</em></span></p></td>
<td>
-<p>
+<p class="simpara">
This is a container for one or more test cases. The test suite gives you an ability to group
test cases into a single referable entity. There are various reasons why you may opt to do so, including:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>To group test cases per subsystems of the unit being tested.</li>
-<li>To share test case setup/cleanup code.</li>
-<li>To run selected group of test cases only.</li>
-<li>To see test report split by groups of test cases</li>
-<li>To skip groups of test cases based on the result of another test unit in a test tree.</li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">To group test cases per subsystems of the unit being tested.</li>
+<li class="listitem">To share test case setup/cleanup code.</li>
+<li class="listitem">To run selected group of test cases only.</li>
+<li class="listitem">To see test report split by groups of test cases</li>
+<li class="listitem">To skip groups of test cases based on the result of another test unit in a test tree.</li>
</ul></div>
-<p>
+<p class="simpara">
A test suite can also contain other test suites, thus allowing a hierarchical test tree structure to be formed.
The <acronym class="acronym">UTF</acronym> requires the test tree to contain at least one test suite with at least one test case. The top level
test suite - root node of the test tree - is called the master test suite.
@@ -184,22 +184,22 @@
<tr>
<td><p><a name="test-setup.def"></a><span class="term"><em class="firstterm">The test setup</em></span></p></td>
<td>
-<p>
+<p class="simpara">
This is the part of a test module that is responsible for the test
preparation. It includes the following operations that take place prior to a start of the test:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">
The <acronym class="acronym">UTF</acronym> initialization
</li>
-<li>
+<li class="listitem">
Test tree construction
</li>
-<li>
+<li class="listitem">
Global test module setup code
</li>
</ul></div>
-<p>
+<p class="simpara">
Per test case" setup code, invoked for every test case it's assigned to, is also attributed to the
test initialization, even though it's executed as a part of the test case.
</p>
@@ -220,31 +220,31 @@
<tr>
<td><p><a name="test-runner.def"></a><span class="term"><em class="firstterm">The test runner</em></span></p></td>
<td>
-<p>
+<p class="simpara">
This is an "executive manager" that runs the show. The test runner's functionality should include
the following interfaces and operations:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">
Entry point to a test module. This is usually either the function main() itself or single function that can be
invoked from it to start testing.
</li>
-<li>
+<li class="listitem">
Initialize the <acronym class="acronym">UTF</acronym> based on runtime parameters
</li>
-<li>
+<li class="listitem">
Select an output media for the test log and the test results report
</li>
-<li>
+<li class="listitem">
Select test cases to execute based on runtime parameters
</li>
-<li>
+<li class="listitem">
Execute all or selected test cases
</li>
-<li>
+<li class="listitem">
Produce the test results report
</li>
-<li>
+<li class="listitem">
Generate a test module result code.
</li>
</ul></div>
@@ -272,8 +272,8 @@
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="left"><p><small>Last revised: , at </small></p></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/fixture.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/fixture.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/fixture.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Fixtures or let me repeat myself</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Fixtures … or let me repeat myself</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
<link rel="up" href="../user-guide.html" title="Unit Test Framework: User's guide">
<link rel="prev" href="test-organization/expected-failures.html" title="Expected failures specification">
@@ -24,17 +24,17 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="utf.user-guide.fixture"></a>Fixtures or let me repeat myself</h4></div></div></div>
+<a name="utf.user-guide.fixture"></a>Fixtures … or let me repeat myself</h4></div></div></div>
<p class="first-line-indented">
In general terms a test fixture or test context is the collection of one or more of the following items, required
to perform the test:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>preconditions</li>
-<li>particular states of tested unites</li>
-<li>necessary cleanup procedures</li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">preconditions</li>
+<li class="listitem">particular states of tested unites</li>
+<li class="listitem">necessary cleanup procedures</li>
</ul></div>
<p class="first-line-indented">
Though these tasks are encountered in many if not all test cases, what makes a test fixture different is
@@ -83,14 +83,14 @@
This is a generic solution that can be used to implement any kind of shared setup or cleanup procedure. Still
there are several more or less minor practical issues with this pure C++ based fixtures solution:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">
We need to add a fixture declaration statement into each test case manually.
</li>
-<li>
+<li class="listitem">
Objects defined in fixture are references with "<fixture-instance-name>." prefix.
</li>
-<li>
+<li class="listitem">
There is no place to execute a "global" fixture, which performs "global" setup/cleanup
procedures before and after testing.
</li>
@@ -102,15 +102,15 @@
teardown fixture functions should comply to. Based on the generic fixture model, the <acronym class="acronym">UTF</acronym> presents solution for
the following tasks:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li><a class="link" href="fixture/per-test-case.html" title="Per test case fixture">per test case fixture automation</a></li>
-<li><a class="link" href="fixture/test-suite-shared.html" title="Test suite level fixture">shared test suite level fixture</a></li>
-<li><a class="link" href="fixture/global.html" title="Global fixture">"global" fixture support</a></li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem"><a class="link" href="fixture/per-test-case.html" title="Per test case fixture">per test case fixture automation</a></li>
+<li class="listitem"><a class="link" href="fixture/test-suite-shared.html" title="Test suite level fixture">shared test suite level fixture</a></li>
+<li class="listitem"><a class="link" href="fixture/global.html" title="Global fixture">"global" fixture support</a></li>
</ul></div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/fixture/global.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/fixture/global.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/fixture/global.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Global fixture</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../fixture.html" title="Fixtures or let me repeat myself">
+<link rel="up" href="../fixture.html" title="Fixtures … or let me repeat myself">
<link rel="prev" href="test-suite-shared.html" title="Test suite level fixture">
-<link rel="next" href="../test-output.html" title="Test Output or let's see what you got for your money">
+<link rel="next" href="../test-output.html" title="Test Output … or let's see what you got for your money">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -24,7 +24,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.fixture.global"></a>Global fixture</h5></div></div></div>
<p class="first-line-indented">
@@ -35,29 +35,29 @@
Though some initialization can be implemented in the test module initialization function, there are several
reasons to prefer the global fixture approach:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>There is no place for cleanup/teardown operations in the initialization function.</li>
-<li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">There is no place for cleanup/teardown operations in the initialization function.</li>
+<li class="listitem">
Unlike the initialization function, the global fixture setup method invocation is guarded by the execution
monitor. That means that all uncaught errors that occur during initialization are properly reported.
</li>
-<li>
+<li class="listitem">
Any number of different global fixtures can be defined, which allows you to split initialization code by
category.
</li>
-<li>
+<li class="listitem">
The fixture allows you to place matching setup/teardown code in close vicinity in your test module code.
</li>
-<li>
+<li class="listitem">
If the whole test tree is constructed automatically the initialization function is empty and auto-generated by
the <acronym class="acronym">UTF</acronym>. To introduce the initialization function can be more work than the use of a global fixture facility,
while global fixture is more to the point.
</li>
-<li>
+<li class="listitem">
Since all fixtures follow the same generic model you can easily switch from local per test case fixtures to
the global one.
</li>
-<li>
+<li class="listitem">
If you are using the interactive test runner (non-supplied yet) global test fixtures are applied to every run,
while an initialization function is executed only once during a test module startup (just make sure that
it's what you really want).
@@ -73,7 +73,7 @@
The statement, that performs global fixture definition, has to reside at a test file scope.
</p>
<div class="example">
-<a name="utf.user-guide.fixture.global.example20"></a><p class="title"><b>Example 25. Global fixture</b></p>
+<a name="utf.user-guide.fixture.global.example20"></a><p class="title"><b>Example 25. Global fixture</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -98,10 +98,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example20-output">> example
global setup
@@ -116,7 +116,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/fixture/model.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/fixture/model.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/fixture/model.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Generic fixture model</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../fixture.html" title="Fixtures or let me repeat myself">
-<link rel="prev" href="../fixture.html" title="Fixtures or let me repeat myself">
+<link rel="up" href="../fixture.html" title="Fixtures … or let me repeat myself">
+<link rel="prev" href="../fixture.html" title="Fixtures … or let me repeat myself">
<link rel="next" href="per-test-case.html" title="Per test case fixture">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
</head>
@@ -24,7 +24,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.fixture.model"></a>Generic fixture model</h5></div></div></div>
<p class="first-line-indented">
@@ -54,7 +54,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/fixture/per-test-case.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/fixture/per-test-case.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/fixture/per-test-case.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Per test case fixture</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../fixture.html" title="Fixtures or let me repeat myself">
+<link rel="up" href="../fixture.html" title="Fixtures … or let me repeat myself">
<link rel="prev" href="model.html" title="Generic fixture model">
<link rel="next" href="test-suite-shared.html" title="Test suite level fixture">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
@@ -24,7 +24,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.fixture.per-test-case"></a>Per test case fixture</h5></div></div></div>
<p class="first-line-indented">
@@ -48,7 +48,7 @@
</p></td></tr>
</table></div>
<div class="example">
-<a name="utf.user-guide.fixture.per-test-case.example18"></a><p class="title"><b>Example 23. Per test case fixture</b></p>
+<a name="utf.user-guide.fixture.per-test-case.example18"></a><p class="title"><b>Example 23. Per test case fixture</b></p>
<div class="example-contents">
<p class="first-line-indented">
In this example only test_case1 and test_case2 have fixture F assigned. In the next section you going to see
@@ -80,10 +80,10 @@
BOOST_CHECK( true );
}
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example18-output">> example --log_level=message
Running 3 test cases...
@@ -101,7 +101,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/fixture/test-suite-shared.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/fixture/test-suite-shared.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/fixture/test-suite-shared.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Test suite level fixture</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../fixture.html" title="Fixtures or let me repeat myself">
+<link rel="up" href="../fixture.html" title="Fixtures … or let me repeat myself">
<link rel="prev" href="per-test-case.html" title="Per test case fixture">
<link rel="next" href="global.html" title="Global fixture">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
@@ -24,7 +24,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.fixture.test-suite-shared"></a>Test suite level fixture</h5></div></div></div>
<p class="first-line-indented">
@@ -63,7 +63,7 @@
</p></td></tr>
</table></div>
<div class="example">
-<a name="utf.user-guide.fixture.test-suite-shared.example19"></a><p class="title"><b>Example 24. Test suite level fixture</b></p>
+<a name="utf.user-guide.fixture.test-suite-shared.example19"></a><p class="title"><b>Example 24. Test suite level fixture</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -96,10 +96,10 @@
BOOST_AUTO_TEST_SUITE_END()
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example19-output">> example
Running 2 test cases...
@@ -113,7 +113,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/initialization.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/initialization.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/initialization.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Test module initialization or ready, set</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Test module initialization … or ready, set …</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
<link rel="up" href="../user-guide.html" title="Unit Test Framework: User's guide">
<link rel="prev" href="usage-variants/extern-test-runner.html" title="External test runner variant of the UTF">
-<link rel="next" href="test-organization.html" title="Test organization or the house that Jack built">
+<link rel="next" href="test-organization.html" title="Test organization … or the house that Jack built">
<script language="JavaScript1.2" src="../../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,17 +22,17 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="utf.user-guide.initialization"></a>Test module initialization or ready, set </h4></div></div></div>
+<a name="utf.user-guide.initialization"></a>Test module initialization … or ready, set …</h4></div></div></div>
<p class="first-line-indented">
There are two tasks that you may need to perform before actual testing can start:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">
The test tree needs to be built (unless you are using automated test units registration).
</li>
-<li>
+<li class="listitem">
Custom test module initialization needs to be performed. This includes
initialization of the code under test and custom tune-up of the <acronym class="acronym">UTF</acronym> parameters (for example the test log or the
test results report output streams redirection).
@@ -41,7 +41,7 @@
<p class="first-line-indented">
The function dedicated for this purpose is called the test module initialization function. Alternatively you can
employ global fixtures, covered in details, including differences in two approaches, in
- <a class="xref" href="fixture.html" title="Fixtures or let me repeat myself">the section called “Fixtures”</a>.
+ <a class="xref" href="fixture.html" title="Fixtures … or let me repeat myself">the section called “Fixtures”</a>.
</p>
<p class="first-line-indented">
The <acronym class="acronym">UTF</acronym> requires you to implement the test module initialization function. The test runner supplied with the static
@@ -59,7 +59,7 @@
specification became inconvenient and unnecessary unsafe. So the alternative initialization function specification
was introduced. This change is not backward compatible. The test runners supplied with the static library and
single-header variants of the <acronym class="acronym">UTF</acronym> by default still require original initialization function specification, but
- support <a class="link" href="../compilation.html#utf.compilation.flags" title="Table 3. The UTF compilation flags">compilation flags</a> that switch to the alternative one. The test
+ support <a class="link" href="../compilation.html#utf.compilation.flags" title="Table 3. The UTF compilation flags">compilation flags</a> that switch to the alternative one. The test
runner supplied with dynamic library variant of the <acronym class="acronym">UTF</acronym> requires new specification and doesn't support
original one. The plan is to deprecate the original initialization function specification in one of the future
releases and ultimately to stop supporting it.
@@ -69,7 +69,7 @@
exception or system error detected during initialization function invocation is treated as initialization error and
is reported as such.
</p>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.initialization.orig-signature"></a>Original initialization function signature and name</h5></div></div></div>
<p class="first-line-indented">
@@ -92,7 +92,7 @@
command line arguments using the master test suite interface.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.initialization.alt-signature"></a>Alternative initialization function signature and name</h5></div></div></div>
<p class="first-line-indented">
@@ -106,7 +106,7 @@
test suite interface. It's guarantied that any framework-specific command line arguments are excluded.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.initialization.signature-typedef"></a>Initialization function signature access</h5></div></div></div>
<p class="first-line-indented">
@@ -123,7 +123,7 @@
}
}</pre>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.initialization.auto-generation"></a>Automated generation of the test module initialization function</h5></div></div></div>
<p class="first-line-indented">
@@ -149,7 +149,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/runtime-config.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/runtime-config.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/runtime-config.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Runtime configuration or what are the strings I can pull?</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Runtime configuration … or what are the strings I can pull?</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
<link rel="up" href="../user-guide.html" title="Unit Test Framework: User's guide">
<link rel="prev" href="test-output/test-progress.html" title="Test progress display">
@@ -22,9 +22,9 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="utf.user-guide.runtime-config"></a>Runtime configuration or what are the strings I can pull?</h4></div></div></div>
+<a name="utf.user-guide.runtime-config"></a>Runtime configuration … or what are the strings I can pull?</h4></div></div></div>
<p class="first-line-indented">
The <acronym class="acronym">UTF</acronym> supports multiple parameters that affect test module execution. To set the parameter's value you can
either use a runtime configuration subsystem interface from within the test module initialization function or you can
@@ -56,7 +56,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/runtime-config/reference.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/runtime-config/reference.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/runtime-config/reference.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Runtime parameters reference</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../runtime-config.html" title="Runtime configuration or what are the strings I can pull?">
+<link rel="up" href="../runtime-config.html" title="Runtime configuration … or what are the strings I can pull?">
<link rel="prev" href="run-by-name.html" title="Running specific test units selected by their name">
-<link rel="next" href="../../testing-tools.html" title="The UTF testing tools or tester's toolbox for all occasions">
+<link rel="next" href="../../testing-tools.html" title="The UTF testing tools … or tester's toolbox for all occasions">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -22,7 +22,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.runtime-config.reference"></a>Runtime parameters reference</h5></div></div></div>
<p class="first-line-indented">
@@ -31,24 +31,24 @@
acceptable values list. All values are case sensitive and are required to exactly match the parameter specification.
</p>
<script language="JavaScript1.2">
- var id296286;
+ var id334357;
</script><table class="inline-reference"><tr>
<td class="index" valign="top"><ul>
-<li>auto_start_dbg</li>
-<li>build_info</li>
-<li>catch_system_errors</li>
-<li>detect_memory_leak</li>
-<li>detect_fp_exceptions</li>
-<li>log_format</li>
-<li>log_level</li>
-<li>output_format</li>
-<li>random</li>
-<li>report_format</li>
-<li>report_level</li>
-<li>result_code</li>
-<li>run_test</li>
-<li>show_progress</li>
-<li>use_alt_stack</li>
+<li>auto_start_dbg</li>
+<li>build_info</li>
+<li>catch_system_errors</li>
+<li>detect_memory_leak</li>
+<li>detect_fp_exceptions</li>
+<li>log_format</li>
+<li>log_level</li>
+<li>output_format</li>
+<li>random</li>
+<li>report_format</li>
+<li>report_level</li>
+<li>result_code</li>
+<li>run_test</li>
+<li>show_progress</li>
+<li>use_alt_stack</li>
</ul></td>
<td class="content" valign="top">
<div class="entry" id="utf.user-guide.runtime-config.parameters.auto_start_dbg"><div class="segmentedlist">
@@ -71,7 +71,7 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list">
+<td><table border="0" summary="Simple list" class="simplelist">
<tr><td><span class="bold"><strong>no</strong></span></td></tr>
<tr><td>yes</td></tr>
<tr><td>debugger identifier</td></tr>
@@ -110,7 +110,7 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list">
+<td><table border="0" summary="Simple list" class="simplelist">
<tr><td><span class="bold"><strong>no</strong></span></td></tr>
<tr><td>yes</td></tr>
</table></td>
@@ -146,7 +146,7 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list">
+<td><table border="0" summary="Simple list" class="simplelist">
<tr><td><span class="bold"><strong>yes</strong></span></td></tr>
<tr><td>no</td></tr>
</table></td>
@@ -177,12 +177,12 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Command line argument name</span></nobr></strong></td>
<td>: </td>
-<td><em class="parameter"><code>build_info</code></em></td>
+<td><em class="parameter"><code>detect_memory_leaks</code></em></td>
</tr>
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list">
+<td><table border="0" summary="Simple list" class="simplelist">
<tr><td>0</td></tr>
<tr><td><span class="bold"><strong>1</strong></span></td></tr>
<tr><td>integer value > 1</td></tr>
@@ -223,7 +223,7 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list">
+<td><table border="0" summary="Simple list" class="simplelist">
<tr><td><span class="bold"><strong>no</strong></span></td></tr>
<tr><td>yes</td></tr>
</table></td>
@@ -258,7 +258,7 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list">
+<td><table border="0" summary="Simple list" class="simplelist">
<tr><td>
<span class="bold"><strong>HRF</strong></span> - human readable format</td></tr>
<tr><td>XML - XML format for automated output processing</td></tr>
@@ -374,7 +374,7 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list">
+<td><table border="0" summary="Simple list" class="simplelist">
<tr><td>
<span class="bold"><strong>HRF</strong></span> - human readable format</td></tr>
<tr><td>XML - XML format for automated output processing</td></tr>
@@ -411,7 +411,7 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list">
+<td><table border="0" summary="Simple list" class="simplelist">
<tr><td><span class="bold"><strong>0</strong></span></td></tr>
<tr><td>1</td></tr>
<tr><td>integer value > 1</td></tr>
@@ -443,12 +443,12 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Command line argument name</span></nobr></strong></td>
<td>: </td>
-<td><em class="parameter"><code>report</code></em></td>
+<td><em class="parameter"><code>report_format</code></em></td>
</tr>
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list">
+<td><table border="0" summary="Simple list" class="simplelist">
<tr><td>
<span class="bold"><strong>HRF</strong></span> - human readable format</td></tr>
<tr><td>XML - XML format for automated output processing</td></tr>
@@ -475,17 +475,17 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Environment variable name</span></nobr></strong></td>
<td>: </td>
-<td><code class="varname">BOOST_TEST_LOG_FORMAT</code></td>
+<td><code class="varname">BOOST_TEST_REPORT_LEVEL</code></td>
</tr>
<tr class="seg">
<td><strong><nobr><span class="segtitle">Command line argument name</span></nobr></strong></td>
<td>: </td>
-<td><em class="parameter"><code>log_format</code></em></td>
+<td><em class="parameter"><code>report_level</code></em></td>
</tr>
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list">
+<td><table border="0" summary="Simple list" class="simplelist">
<tr><td>no</td></tr>
<tr><td><span class="bold"><strong>confirm</strong></span></td></tr>
<tr><td>short</td></tr>
@@ -524,7 +524,7 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list">
+<td><table border="0" summary="Simple list" class="simplelist">
<tr><td><span class="bold"><strong>yes</strong></span></td></tr>
<tr><td>no</td></tr>
</table></td>
@@ -561,7 +561,7 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list"><tr><td>
+<td><table border="0" summary="Simple list" class="simplelist"><tr><td>
<a class="link" href="run-by-name.html" title="Running specific test units selected by their name">specification</a> of test units to run
</td></tr></table></td>
</tr>
@@ -595,7 +595,7 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list">
+<td><table border="0" summary="Simple list" class="simplelist">
<tr><td><span class="bold"><strong>no</strong></span></td></tr>
<tr><td>yes</td></tr>
</table></td>
@@ -628,7 +628,7 @@
<tr class="seg">
<td><strong><nobr><span class="segtitle">Acceptable Values</span></nobr></strong></td>
<td>: </td>
-<td><table class="simplelist" border="0" summary="Simple list">
+<td><table border="0" summary="Simple list" class="simplelist">
<tr><td><span class="bold"><strong>yes</strong></span></td></tr>
<tr><td>no</td></tr>
</table></td>
@@ -649,7 +649,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/runtime-config/run-by-name.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/runtime-config/run-by-name.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/runtime-config/run-by-name.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Running specific test units selected by their name</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../runtime-config.html" title="Runtime configuration or what are the strings I can pull?">
-<link rel="prev" href="../runtime-config.html" title="Runtime configuration or what are the strings I can pull?">
+<link rel="up" href="../runtime-config.html" title="Runtime configuration … or what are the strings I can pull?">
+<link rel="prev" href="../runtime-config.html" title="Runtime configuration … or what are the strings I can pull?">
<link rel="next" href="reference.html" title="Runtime parameters reference">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
</head>
@@ -22,7 +22,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.runtime-config.run-by-name"></a>Running specific test units selected by their name</h5></div></div></div>
<p class="first-line-indented">
@@ -84,9 +84,9 @@
BOOST_AUTO_TEST_SUITE_END()
</pre>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>
-<p>Run single test case by specifying it's name.</p>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">
+<p class="simpara">Run single test case by specifying it's name.</p>
<pre class="test-execution-output">>example --log_level=test_suite --run_test=testA
Running 1 test case...
Entering test suite "example"
@@ -97,8 +97,8 @@
*** No errors detected</pre>
</li>
-<li>
-<p>
+<li class="listitem">
+<p class="simpara">
Running multiple test cases residing within the same test suite by listing their names in coma separated list.
</p>
<pre class="test-execution-output">>example --log_level=test_suite --run_test=testA,testB
@@ -114,13 +114,13 @@
*** No errors detected</pre>
</li>
-<li>
-<p>Incorrect test case name may lead to no test to be run.</p>
+<li class="listitem">
+<p class="simpara">Incorrect test case name may lead to no test to be run.</p>
<pre class="test-execution-output">>example --log_level=test_suite --run_test=testC
Test setup error: no test cases matching filter</pre>
</li>
-<li>
-<p>
+<li class="listitem">
+<p class="simpara">
Test unit name can refer to a test suite as well. All test units within the referred test suites are going to be
run.
</p>
@@ -139,8 +139,8 @@
*** No errors detected</pre>
</li>
-<li>
-<p>
+<li class="listitem">
+<p class="simpara">
Using '/' as levels separator you can refer to any test unit inside a test tree.
</p>
<pre class="test-execution-output">>example --log_level=test_suite --run_test=s2/in/test
@@ -157,8 +157,8 @@
*** No errors detected</pre>
</li>
-<li>
-<p>
+<li class="listitem">
+<p class="simpara">
The <acronym class="acronym">UTF</acronym> supports simple regular expression-like '*' wildcard. Single '*' match any name of test unit. Accordingly
expression 's1/*' is equivalent to the expression 's1' and matches all test units inside test suite s1. Similarly
expression '*/test1' refers to all test units named test1 that reside in master test suite's direct child suites.
@@ -180,8 +180,8 @@
*** No errors detected</pre>
</li>
-<li>
-<p>
+<li class="listitem">
+<p class="simpara">
The <acronym class="acronym">UTF</acronym> allows to match specific prefix in test unit names. For example, expression 's2/test*' filters out only
test units in test suite s2 with name that starts with 'test'. This avoids running test suite s2/in.
</p>
@@ -200,8 +200,8 @@
*** No errors detected</pre>
</li>
-<li>
-<p>
+<li class="listitem">
+<p class="simpara">
The <acronym class="acronym">UTF</acronym> allows to match specific suffix in test unit names. For example, expression '*/*1' filters out test units
with name that ends with '1' and reside in master test suite's direct child suites.
</p>
@@ -220,8 +220,8 @@
*** No errors detected</pre>
</li>
-<li>
-<p>
+<li class="listitem">
+<p class="simpara">
Finally, the <acronym class="acronym">UTF</acronym> allows to match specific substring in test unit names.
</p>
<pre class="test-execution-output">>example --log_level=test_suite --run_test=s1/*est*
@@ -243,7 +243,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-organization.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-organization.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-organization.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Test organization or the house that Jack built</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Test organization … or the house that Jack built</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
<link rel="up" href="../user-guide.html" title="Unit Test Framework: User's guide">
-<link rel="prev" href="initialization.html" title="Test module initialization or ready, set">
+<link rel="prev" href="initialization.html" title="Test module initialization … or ready, set …">
<link rel="next" href="test-organization/nullary-test-case.html" title="Nullary function based test case">
<script language="JavaScript1.2" src="../../../js/boost-test.js"></script>
</head>
@@ -24,30 +24,30 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="utf.user-guide.test-organization"></a>Test organization or the house that Jack built</h4></div></div></div>
+<a name="utf.user-guide.test-organization"></a>Test organization … or the house that Jack built</h4></div></div></div>
<p class="first-line-indented">
If you look at many legacy test modules, big chance is that it's implemented as one big test function that
consists of a mixture of check and output statements. Is there anything wrong with it? Yes. There are various
disadvantages in single test function approach:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="square">
-<li style="list-style-type: square">
+<div class="itemizedlist"><ul type="square">
+<li class="listitem" style="list-style-type: square">
One big function tends to become really difficult to manage if the number of checks exceeds a reasonable limit
(true for any large function). What is tested and where - who knows?
</li>
-<li style="list-style-type: square">
+<li class="listitem" style="list-style-type: square">
Many checks require similar preparations. This results in code repetitions within the test function.
</li>
-<li style="list-style-type: square">
+<li class="listitem" style="list-style-type: square">
If a fatal error or an exception is caused by any checks within the test function the rest of tests are
skipped and there is no way to prevent this.
</li>
-<li style="list-style-type: square">
+<li class="listitem" style="list-style-type: square">
No way to perform only checks for a particular subsystem of the tested unit.
</li>
-<li style="list-style-type: square">
+<li class="listitem" style="list-style-type: square">
No summary of how different subsystems of the tested unit performed under in the test.
</li>
</ul></div>
@@ -61,14 +61,14 @@
adopting any function or function object that matches the signature as a test case. The signatures the <acronym class="acronym">UTF</acronym>
supports are:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">
<a class="link" href="test-organization/nullary-test-case.html" title="Nullary function based test case">Nullary function</a>
</li>
-<li>
- <a class="link" href="test-organization/nullary-test-case.html" title="Nullary function based test case">Unary function</a>
+<li class="listitem">
+ <a class="link" href="test-organization/unary-test-case.html" title="Unary function based test case">Unary function</a>
</li>
-<li>
+<li class="listitem">
<a class="link" href="test-organization/test-case-template.html" title="Test case template">Nullary function template</a>
</li>
</ul></div>
@@ -100,7 +100,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-organization/auto-nullary-test-case.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-organization/auto-nullary-test-case.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-organization/auto-nullary-test-case.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Nullary function based test case with automated registration</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
<link rel="up" href="nullary-test-case.html" title="Nullary function based test case">
<link rel="prev" href="manual-nullary-test-case.html" title="Manually registered nullary function based test case">
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-organization.auto-nullary-test-case"></a>Nullary function based test case with automated registration</h6></div></div></div>
<p class="first-line-indented">
@@ -38,10 +38,10 @@
<p class="first-line-indented">
The macro is designed to closely mimic nullary free function syntax. Changes that are required to make an
existing test case, implemented as a free function, registered in place are illustrated in the following
- example (compare with <a class="xref" href="manual-nullary-test-case.html#utf.user-guide.test-organization.manual-nullary-test-case.example01" title="Example 5. Nullary free function manually registered">Example 5, “Nullary free function manually registered”</a>):
+ example (compare with <a class="xref" href="manual-nullary-test-case.html#utf.user-guide.test-organization.manual-nullary-test-case.example01" title="Example 5. Nullary free function manually registered">Example 5, “Nullary free function manually registered”</a>):
</p>
<div class="example">
-<a name="utf.user-guide.test-organization.auto-nullary-test-case.example06"></a><p class="title"><b>Example 10. Nullary function based test case with automated registration</b></p>
+<a name="utf.user-guide.test-organization.auto-nullary-test-case.example06"></a><p class="title"><b>Example 10. Nullary function based test case with automated registration</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -56,10 +56,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example06-output">> example --log_level=test_suite
Running 1 test case...
@@ -79,7 +79,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-organization/auto-test-case-template.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-organization/auto-test-case-template.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-organization/auto-test-case-template.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Test case template with automated registration</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
<link rel="up" href="test-case-template.html" title="Test case template">
<link rel="prev" href="manual-test-case-template.html" title="Manually registered test case template">
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-organization.auto-test-case-template"></a>Test case template with automated registration</h6></div></div></div>
<p class="first-line-indented">
@@ -62,11 +62,10 @@
</tbody>
</table></div>
<div class="example">
-<a name="utf.user-guide.test-organization.auto-test-case-template.example10"></a><p class="title"><b>Example 14. Test case template with automated registration</b></p>
+<a name="utf.user-guide.test-organization.auto-test-case-template.example10"></a><p class="title"><b>Example 14. Test case template with automated registration</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
-#include <boost/test/test_case_template.hpp>
#include <boost/mpl/list.hpp>
//____________________________________________________________________________//
@@ -80,10 +79,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example10-output">> example
Running 3 test cases...
@@ -97,7 +96,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-organization/auto-test-suite.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-organization/auto-test-suite.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-organization/auto-test-suite.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Test suites with automated registration</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
<link rel="up" href="test-suite.html" title="Test suite">
<link rel="prev" href="manual-test-suite.html" title="Manually registered test suites">
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-organization.auto-test-suite"></a>Test suites with automated registration</h6></div></div></div>
<p class="first-line-indented">
@@ -51,7 +51,7 @@
become members of the master test suite. There is no limit on depth of test suite inclusion.
</p>
<div class="example">
-<a name="utf.user-guide.test-organization.auto-test-suite.example12"></a><p class="title"><b>Example 16. Test suites with automated registration</b></p>
+<a name="utf.user-guide.test-organization.auto-test-suite.example12"></a><p class="title"><b>Example 16. Test suites with automated registration</b></p>
<div class="example-contents">
<p class="first-line-indented">
This example creates a test tree that matches exactly the one created in the manual test suite registration
@@ -88,10 +88,10 @@
BOOST_AUTO_TEST_SUITE_END()
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example12-output">> example
Running 4 test cases...
@@ -103,7 +103,7 @@
</div>
</div>
<br class="example-break"><div class="example">
-<a name="utf.user-guide.test-organization.auto-test-suite.example53"></a><p class="title"><b>Example 17. Example of test suite extension using automated registration facility</b></p>
+<a name="utf.user-guide.test-organization.auto-test-suite.example53"></a><p class="title"><b>Example 17. Example of test suite extension using automated registration facility</b></p>
<div class="example-contents">
<p class="first-line-indented">
In this example test suite test_suite consists of two parts. Their definition is remote and is separated by another
@@ -137,10 +137,10 @@
BOOST_AUTO_TEST_SUITE_END()
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example53-output">>example --report_level=detailed
Running 3 test cases...
@@ -171,7 +171,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-organization/expected-failures.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-organization/expected-failures.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-organization/expected-failures.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Expected failures specification</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../test-organization.html" title="Test organization or the house that Jack built">
+<link rel="up" href="../test-organization.html" title="Test organization … or the house that Jack built">
<link rel="prev" href="master-test-suite.html" title="Master Test Suite">
-<link rel="next" href="../fixture.html" title="Fixtures or let me repeat myself">
+<link rel="next" href="../fixture.html" title="Fixtures … or let me repeat myself">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -24,7 +24,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.test-organization.expected-failures"></a>Expected failures specification</h5></div></div></div>
<p class="first-line-indented">
@@ -63,7 +63,7 @@
case is going to fail, since the number of failures is smaller than expected.
</p></td></tr>
</table></div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-organization.manual-expected-failures"></a>Usage with manually registered test cases</h6></div></div></div>
<p class="first-line-indented">
@@ -71,7 +71,7 @@
test_suite::add call during test unit registration.
</p>
<div class="example">
-<a name="utf.user-guide.test-organization.manual-expected-failures.example16"></a><p class="title"><b>Example 21. Expected failures specification for manually registered test case</b></p>
+<a name="utf.user-guide.test-organization.manual-expected-failures.example16"></a><p class="title"><b>Example 21. Expected failures specification for manually registered test case</b></p>
<div class="example-contents">
<pre class="programlisting">#include <boost/test/included/unit_test.hpp>
using namespace boost::unit_test;
@@ -95,10 +95,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example16-output">> example --log_level=message
Running 1 test case...
@@ -111,7 +111,7 @@
</div>
<br class="example-break">
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-organization.auto-expected-failures"></a>Usage with automatically registered test cases</h6></div></div></div>
<p class="first-line-indented">
@@ -126,7 +126,7 @@
test suite where BOOST_AUTO_TEST_CASE_EXPECTED_FAILURES resides.
</p>
<div class="example">
-<a name="utf.user-guide.test-organization.auto-expected-failures.example17"></a><p class="title"><b>Example 22. Expected failures specification for automatically registered test case</b></p>
+<a name="utf.user-guide.test-organization.auto-expected-failures.example17"></a><p class="title"><b>Example 22. Expected failures specification for automatically registered test case</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -155,10 +155,10 @@
//____________________________________________________________________________//
BOOST_AUTO_TEST_SUITE_END()</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example17-output">> example --report_level=short
Running 2 test cases...
@@ -178,7 +178,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-organization/manual-nullary-test-case.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-organization/manual-nullary-test-case.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-organization/manual-nullary-test-case.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Manually registered nullary function based test case</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
<link rel="up" href="nullary-test-case.html" title="Nullary function based test case">
<link rel="prev" href="nullary-test-case.html" title="Nullary function based test case">
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-organization.manual-nullary-test-case"></a>Manually registered nullary function based test case</h6></div></div></div>
<p class="first-line-indented">
@@ -47,7 +47,7 @@
Note that the free function name is passed by address to the macro BOOST_TEST_CASE.
</p>
<div class="example">
-<a name="utf.user-guide.test-organization.manual-nullary-test-case.example01"></a><p class="title"><b>Example 5. Nullary free function manually registered</b></p>
+<a name="utf.user-guide.test-organization.manual-nullary-test-case.example01"></a><p class="title"><b>Example 5. Nullary free function manually registered</b></p>
<div class="example-contents">
<pre class="programlisting">#include <boost/test/included/unit_test.hpp>
using namespace boost::unit_test;
@@ -72,10 +72,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example01-output">> example
Running 1 test case...
@@ -101,7 +101,7 @@
</p></td></tr>
</table></div>
<div class="example">
-<a name="utf.user-guide.test-organization.manual-nullary-test-case.example02"></a><p class="title"><b>Example 6. Nullary method of a class bound to global class instance and manually registered</b></p>
+<a name="utf.user-guide.test-organization.manual-nullary-test-case.example02"></a><p class="title"><b>Example 6. Nullary method of a class bound to global class instance and manually registered</b></p>
<div class="example-contents">
<pre class="programlisting">#include <boost/test/included/unit_test.hpp>
#include <boost/bind.hpp>
@@ -130,10 +130,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example02-output">> example
Running 1 test case...
@@ -144,7 +144,7 @@
</div>
</div>
<br class="example-break"><div class="example">
-<a name="utf.user-guide.test-organization.manual-nullary-test-case.example03"></a><p class="title"><b>Example 7. Nullary method of a class bound to shared class instance and manually registered</b></p>
+<a name="utf.user-guide.test-organization.manual-nullary-test-case.example03"></a><p class="title"><b>Example 7. Nullary method of a class bound to shared class instance and manually registered</b></p>
<div class="example-contents">
<pre class="programlisting">#include <boost/test/included/unit_test.hpp>
#include <boost/bind.hpp>
@@ -180,10 +180,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example03-output">> example
Running 2 test cases...
@@ -198,7 +198,7 @@
instance globally it may be easier and safer to create an instance on the stack of free function:
</p>
<div class="example">
-<a name="utf.user-guide.test-organization.manual-nullary-test-case.example04"></a><p class="title"><b>Example 8. Nullary method of a class bound to local class instance inside free function</b></p>
+<a name="utf.user-guide.test-organization.manual-nullary-test-case.example04"></a><p class="title"><b>Example 8. Nullary method of a class bound to local class instance inside free function</b></p>
<div class="example-contents">
<pre class="programlisting">#include<boost/test/included/unit_test.hpp>
@@ -233,10 +233,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example04-output">> example
Running 1 test case...
@@ -260,13 +260,13 @@
</p></td></tr>
</table></div>
<div class="example">
-<a name="utf.user-guide.test-organization.manual-nullary-test-case.example05"></a><p class="title"><b>Example 9. Binary free function bound to set of different parameter pairs</b></p>
+<a name="utf.user-guide.test-organization.manual-nullary-test-case.example05"></a><p class="title"><b>Example 9. Binary free function bound to set of different parameter pairs</b></p>
<div class="example-contents">
<p class="first-line-indented">
This example employs the alternative test module initialization function specification.
</p>
<pre class="programlisting">#define BOOST_TEST_DYN_LINK
-#include <boost/test/included/unit_test.hpp>
+#include <boost/test/unit_test.hpp>
#include <boost/bind.hpp>
using namespace boost::unit_test;
@@ -302,10 +302,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example05-output">> example
Running 3 test cases...
@@ -321,7 +321,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-organization/manual-test-case-template.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-organization/manual-test-case-template.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-organization/manual-test-case-template.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Manually registered test case template</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
<link rel="up" href="test-case-template.html" title="Test case template">
<link rel="prev" href="test-case-template.html" title="Test case template">
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-organization.manual-test-case-template"></a>Manually registered test case template</h6></div></div></div>
<p class="first-line-indented">
@@ -49,14 +49,14 @@
<p class="first-line-indented">
There several problems/inconveniencies with above approach, including:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc"><li>
-<p>
+<div class="itemizedlist"><ul type="disc"><li class="listitem">
+<p class="simpara">
Fatal error in one of the invocation will stop whole test case and will skip invocations with different types
</p>
-<p>
+<p class="simpara">
You need to repeat function invocation manually for all the parameters you are interested in
</p>
-<p>
+<p class="simpara">
You need two functions to implement the test
</p>
</li></ul></div>
@@ -117,10 +117,9 @@
them causes termination of the sub test case.
</p>
<div class="example">
-<a name="utf.user-guide.test-organization.manual-test-case-template.example09"></a><p class="title"><b>Example 13. Manually registered test case template</b></p>
+<a name="utf.user-guide.test-organization.manual-test-case-template.example09"></a><p class="title"><b>Example 13. Manually registered test case template</b></p>
<div class="example-contents">
<pre class="programlisting">#include <boost/test/included/unit_test.hpp>
-#include <boost/test/test_case_template.hpp>
#include <boost/mpl/list.hpp>
using namespace boost::unit_test;
@@ -146,10 +145,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example09-output">> example
Running 3 test cases...
@@ -163,7 +162,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-organization/manual-test-suite.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-organization/manual-test-suite.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-organization/manual-test-suite.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Manually registered test suites</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
<link rel="up" href="test-suite.html" title="Test suite">
<link rel="prev" href="test-suite.html" title="Test suite">
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-organization.manual-test-suite"></a>Manually registered test suites</h6></div></div></div>
<p class="first-line-indented">
@@ -53,7 +53,7 @@
registration is performed in the test module initialization function.
</p>
<div class="example">
-<a name="utf.user-guide.test-organization.manual-test-suite.example11"></a><p class="title"><b>Example 15. Manually registered test suites</b></p>
+<a name="utf.user-guide.test-organization.manual-test-suite.example11"></a><p class="title"><b>Example 15. Manually registered test suites</b></p>
<div class="example-contents">
<pre class="programlisting">#include <boost/test/included/unit_test.hpp>
using namespace boost::unit_test;
@@ -86,10 +86,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example11-output">> example --log_level=test_suite
Running 4 test cases...
@@ -119,7 +119,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-organization/master-test-suite.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-organization/master-test-suite.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-organization/master-test-suite.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Master Test Suite</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
<link rel="up" href="test-suite.html" title="Test suite">
<link rel="prev" href="auto-test-suite.html" title="Test suites with automated registration">
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-organization.master-test-suite"></a>Master Test Suite</h6></div></div></div>
<p class="first-line-indented">
@@ -57,7 +57,7 @@
} // namespace framework
} // namespace unit_test
} // namespace boost</pre>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-organization.cla-access"></a>Command line arguments access interface</h6></div></div></div>
<p class="first-line-indented">
@@ -87,7 +87,7 @@
test module arguments.
</p>
<div class="example">
-<a name="utf.user-guide.test-organization.cla-access.example13"></a><p class="title"><b>Example 18. Command line access in initialization function</b></p>
+<a name="utf.user-guide.test-organization.cla-access.example13"></a><p class="title"><b>Example 18. Command line access in initialization function</b></p>
<div class="example-contents">
<pre class="programlisting">#include <boost/test/included/unit_test.hpp>
using namespace boost::unit_test;
@@ -116,10 +116,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example13-output">> example 1
Test setup error: test tree is empty</pre>
@@ -127,7 +127,7 @@
</div>
<br class="example-break">
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-organization.master-test-suite-name"></a>Naming</h6></div></div></div>
<p class="first-line-indented">
@@ -137,7 +137,7 @@
manually implemented initialization function. Following examples illustrate these methods.
</p>
<div class="example">
-<a name="utf.user-guide.test-organization.master-test-suite-name.example14"></a><p class="title"><b>Example 19. Naming master test suite using the macro <a class="xref" href="../../compilation.html#utf.flag.module">BOOST_TEST_MODULE</a></b></p>
+<a name="utf.user-guide.test-organization.master-test-suite-name.example14"></a><p class="title"><b>Example 19. Naming master test suite using the macro <a class="xref" href="../../compilation.html#utf.flag.module">BOOST_TEST_MODULE</a></b></p>
<div class="example-contents">
<p class="first-line-indented">
If the macro <a class="xref" href="../../compilation.html#utf.flag.module">BOOST_TEST_MODULE</a> is defined, the test module initialization
@@ -158,10 +158,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example14-output">> example --log_level=test_suite
Running 1 test case...
@@ -176,7 +176,7 @@
</div>
</div>
<br class="example-break"><div class="example">
-<a name="utf.user-guide.test-organization.master-test-suite-name.example15"></a><p class="title"><b>Example 20. Naming master test suite explicitly in the test module initialization function</b></p>
+<a name="utf.user-guide.test-organization.master-test-suite-name.example15"></a><p class="title"><b>Example 20. Naming master test suite explicitly in the test module initialization function</b></p>
<div class="example-contents">
<p class="first-line-indented">
Without the <a class="xref" href="../../compilation.html#utf.flag.main">BOOST_TEST_MAIN</a> and the <a class="xref" href="../../compilation.html#utf.flag.module">BOOST_TEST_MODULE</a> flags defined, the test module initialization function has to be manually implemented.
@@ -204,10 +204,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example15-output">> example --log_level=test_suite
Running 1 test case...
@@ -226,7 +226,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-organization/nullary-test-case.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-organization/nullary-test-case.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-organization/nullary-test-case.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Nullary function based test case</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../test-organization.html" title="Test organization or the house that Jack built">
-<link rel="prev" href="../test-organization.html" title="Test organization or the house that Jack built">
+<link rel="up" href="../test-organization.html" title="Test organization … or the house that Jack built">
+<link rel="prev" href="../test-organization.html" title="Test organization … or the house that Jack built">
<link rel="next" href="manual-nullary-test-case.html" title="Manually registered nullary function based test case">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
</head>
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.test-organization.nullary-test-case"></a>Nullary function based test case</h5></div></div></div>
<p class="first-line-indented">
@@ -35,18 +35,18 @@
instances. The simplest is a free function and the <acronym class="acronym">UTF</acronym> provides facilities to create a free function based test
case that is automatically registered. Here are the two construction interfaces:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">
<a class="link" href="manual-nullary-test-case.html" title="Manually registered nullary function based test case">Manually registered test case</a>
</li>
-<li>
+<li class="listitem">
<a class="link" href="auto-nullary-test-case.html" title="Nullary function based test case with automated registration">Test case with automated registration</a>
</li>
</ul></div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-organization/test-case-template.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-organization/test-case-template.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-organization/test-case-template.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Test case template</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../test-organization.html" title="Test organization or the house that Jack built">
+<link rel="up" href="../test-organization.html" title="Test organization … or the house that Jack built">
<link rel="prev" href="unary-test-case.html" title="Unary function based test case">
<link rel="next" href="manual-test-case-template.html" title="Manually registered test case template">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.test-organization.test-case-template"></a>Test case template</h5></div></div></div>
<p class="first-line-indented">
@@ -35,12 +35,12 @@
test cases based on a list of desired types and function similar to nullary function template. This facility is
called test case template. Here are the two construction interfaces:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">
<a class="link" href="manual-test-case-template.html" title="Manually registered test case template">Manually registered test case
template</a>
</li>
-<li>
+<li class="listitem">
<a class="link" href="auto-test-case-template.html" title="Test case template with automated registration">Test case template with automated
registration</a>
</li>
@@ -48,7 +48,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-organization/test-suite.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-organization/test-suite.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-organization/test-suite.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Test suite</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../test-organization.html" title="Test organization or the house that Jack built">
+<link rel="up" href="../test-organization.html" title="Test organization … or the house that Jack built">
<link rel="prev" href="auto-test-case-template.html" title="Test case template with automated registration">
<link rel="next" href="manual-test-suite.html" title="Manually registered test suites">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.test-organization.test-suite"></a>Test suite</h5></div></div></div>
<p class="first-line-indented">
@@ -36,15 +36,15 @@
want to construct a hierarchical test suite structure the <acronym class="acronym">UTF</acronym> provides both manual and automated
test suite creation and registration facilities:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">
<a class="link" href="manual-test-suite.html" title="Manually registered test suites">Manually registered test suite</a>
</li>
-<li>
+<li class="listitem">
<a class="link" href="auto-test-suite.html" title="Test suites with automated registration">Test suite with automated registration</a>
</li>
</ul></div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-organization.test-suite-registration-interface"></a>Test unit registration interface</h6></div></div></div>
<p class="first-line-indented">
@@ -73,7 +73,7 @@
The third optional parameter - timeout - defines the timeout value for the test unit. As of now the <acronym class="acronym">UTF</acronym>
isn't able to set a timeout for the test suite execution, so this parameter makes sense only for test case
registration. By default no timeout is set. See the method
- <code class="computeroutput"><a class="link" href="../../../execution-monitor/reference.html#id270361-bb">boost::execution_monitor::execute</a></code> for more details about the timeout value.
+ <code class="computeroutput"><a class="link" href="../../../execution-monitor/reference.html#id186126-bb">boost::execution_monitor::execute</a></code> for more details about the timeout value.
</p>
<p class="first-line-indented">
To register group of test units in one function call the boost::unit_test::test_suite provides another add
@@ -83,7 +83,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-organization/unary-test-case.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-organization/unary-test-case.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-organization/unary-test-case.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Unary function based test case</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../test-organization.html" title="Test organization or the house that Jack built">
+<link rel="up" href="../test-organization.html" title="Test organization … or the house that Jack built">
<link rel="prev" href="auto-nullary-test-case.html" title="Nullary function based test case with automated registration">
<link rel="next" href="test-case-template.html" title="Test case template">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
@@ -24,7 +24,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.test-organization.unary-test-case"></a>Unary function based test case</h5></div></div></div>
<p class="first-line-indented">
@@ -82,7 +82,7 @@
scope. The master test suite contains 5 independent test cases.
</p>
<div class="example">
-<a name="utf.user-guide.test-organization.unary-test-case.example07"></a><p class="title"><b>Example 11. Unary free function based test case</b></p>
+<a name="utf.user-guide.test-organization.unary-test-case.example07"></a><p class="title"><b>Example 11. Unary free function based test case</b></p>
<div class="example-contents">
<pre class="programlisting">#include <boost/test/included/unit_test.hpp>
#include <boost/test/parameterized_test.hpp>
@@ -110,10 +110,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example07-output">> example
Running 5 test cases...
@@ -130,7 +130,7 @@
This example employs the alternative test module initialization function specification.
</p>
<div class="example">
-<a name="utf.user-guide.test-organization.unary-test-case.example08"></a><p class="title"><b>Example 12. Unary class method based test case</b></p>
+<a name="utf.user-guide.test-organization.unary-test-case.example08"></a><p class="title"><b>Example 12. Unary class method based test case</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_ALTERNATIVE_INIT_API
#include <boost/test/included/unit_test.hpp>
@@ -167,10 +167,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example08-output">> example
Running 5 test cases...
@@ -185,7 +185,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-output.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-output.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-output.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Test Output or let's see what you got for your money</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Test Output … or let's see what you got for your money</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
<link rel="up" href="../user-guide.html" title="Unit Test Framework: User's guide">
<link rel="prev" href="fixture/global.html" title="Global fixture">
@@ -24,51 +24,51 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="utf.user-guide.test-output"></a>Test Output or let's see what you got for your money</h4></div></div></div>
+<a name="utf.user-guide.test-output"></a>Test Output … or let's see what you got for your money</h4></div></div></div>
<p class="first-line-indented">
The output produced by a test module is one of the major assets the <acronym class="acronym">UTF</acronym> brings to users. In comparison with any
kind of manual/assert based solution the <acronym class="acronym">UTF</acronym> provide following services:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>
-<p>All test errors are reported uniformly</p>
-<p>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">
+<p class="simpara">All test errors are reported uniformly</p>
+<p class="simpara">
The test execution monitor along with standardized output from all included
- <a class="link" href="../testing-tools.html" title="The UTF testing tools or tester's toolbox for all occasions">testing tools</a> provides uniform reporting for all errors including fatal
+ <a class="link" href="../testing-tools.html" title="The UTF testing tools … or tester's toolbox for all occasions">testing tools</a> provides uniform reporting for all errors including fatal
errors, like memory assess violation and uncaught exceptions.
</p>
</li>
-<li>
-<p>Detailed information on the source of an error</p>
-<p>
+<li class="listitem">
+<p class="simpara">Detailed information on the source of an error</p>
+<p class="simpara">
The <acronym class="acronym">UTF</acronym> test tool's based assertion provides as much information as possible about cause of error,
usually allowing you to deduce what is wrong without entering the debugger or core analysis.
</p>
</li>
-<li>
-<p>
+<li class="listitem">
+<p class="simpara">
Separation of the test errors description (test log) from the results report summary (test results report)
</p>
-<p>
+<p class="simpara">
The information produced during test execution, including all error, warning and info messages from the test
tools, executed test units notification constitute the test log. By default all entries in the test log are
directed to the standard output. Once testing is completed the <acronym class="acronym">UTF</acronym> may produce a summary test report with
different levels of detail. The test report is by default directed to the standard error output.
</p>
</li>
-<li>
-<p>Flexibility in what is shown in the output</p>
-<p>
+<li class="listitem">
+<p class="simpara">Flexibility in what is shown in the output</p>
+<p class="simpara">
The <acronym class="acronym">UTF</acronym> provides the ability to configure what if shown in both the test log and the test report. The
configuration is supported both at runtime, during test module invocation and at compile time from within a
test module.
</p>
</li>
-<li>
-<p>Flexibility in how output is formatted</p>
-<p>
+<li class="listitem">
+<p class="simpara">Flexibility in how output is formatted</p>
+<p class="simpara">
The <acronym class="acronym">UTF</acronym> provides the ability to configure the format of the test module output. At the moment only 2 formats
are supported by the <acronym class="acronym">UTF</acronym> itself, the well defined public interface allows you to customize an output for
your purposes almost any way you want.
@@ -78,7 +78,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-output/BOOST_TEST_CHECKPOINT.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-output/BOOST_TEST_CHECKPOINT.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-output/BOOST_TEST_CHECKPOINT.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>BOOST_TEST_CHECKPOINT</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
<link rel="up" href="test-log.html" title="Test log output">
<link rel="prev" href="BOOST_TEST_MESSAGE.html" title="BOOST_TEST_MESSAGE">
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.log.BOOST_TEST_CHECKPOINT"></a>BOOST_TEST_CHECKPOINT</h6></div></div></div>
<p class="first-line-indented">
@@ -41,7 +41,7 @@
output stream compliant components.
</p>
<div class="example">
-<a name="utf.user-guide.test-output.log.BOOST_TEST_CHECKPOINT.example22"></a><p class="title"><b>Example 28. BOOST_TEST_CHECKPOINT usage</b></p>
+<a name="utf.user-guide.test-output.log.BOOST_TEST_CHECKPOINT.example22"></a><p class="title"><b>Example 28. BOOST_TEST_CHECKPOINT usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -68,10 +68,10 @@
}
//____________________________________________________________________________//</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example22-output">> example
Running 1 test case...
@@ -86,7 +86,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-output/BOOST_TEST_MESSAGE.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-output/BOOST_TEST_MESSAGE.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-output/BOOST_TEST_MESSAGE.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>BOOST_TEST_MESSAGE</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
<link rel="up" href="test-log.html" title="Test log output">
<link rel="prev" href="test-log.html" title="Test log output">
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.log.BOOST_TEST_MESSAGE"></a>BOOST_TEST_MESSAGE</h6></div></div></div>
<p class="first-line-indented">
@@ -52,7 +52,7 @@
</p></td></tr>
</table></div>
<div class="example">
-<a name="utf.user-guide.test-output.log.BOOST_TEST_MESSAGE.example21"></a><p class="title"><b>Example 27. BOOST_TEST_MESSAGE usage</b></p>
+<a name="utf.user-guide.test-output.log.BOOST_TEST_MESSAGE.example21"></a><p class="title"><b>Example 27. BOOST_TEST_MESSAGE usage</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -80,10 +80,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example21-output">> example --log_level=message
Running 2 test cases...
@@ -100,7 +100,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-output/BOOST_TEST_PASSPOINT.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-output/BOOST_TEST_PASSPOINT.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-output/BOOST_TEST_PASSPOINT.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Logging floating point type numbers</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>BOOST_TEST_PASSPOINT</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
<link rel="up" href="test-log.html" title="Test log output">
-<link rel="prev" href="BOOST_TEST_PASSPOINT.html" title="BOOST_TEST_PASSPOINT">
-<link rel="next" href="log-hr-format.html" title="Human readable log output format">
+<link rel="prev" href="BOOST_TEST_CHECKPOINT.html" title="BOOST_TEST_CHECKPOINT">
+<link rel="next" href="FPT.html" title="Logging floating point type numbers">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,59 +19,73 @@
>
</a>Test log<a href="results-report.html">
>
- </a><b>Logging floating point type numbers</b>
+ </a><b>BOOST_TEST_PASSPOINT</b>
</td>
<td><div class="spirit-nav">
-
<a href="log-hr-format.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a href="FPT.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
-<a name="utf.user-guide.test-output.log.FPT"></a>Logging floating point type numbers</h6></div></div></div>
+<a name="utf.user-guide.test-output.log.BOOST_TEST_PASSPOINT"></a>BOOST_TEST_PASSPOINT</h6></div></div></div>
<p class="first-line-indented">
- It may appear that floating-point numbers are displayed by the <acronym class="acronym">UTF</acronym> with an excessive number of decimal digits.
- However the number of digits shown is chosen to avoid apparently nonsensical displays like <code class="computeroutput">[1.00000 != 1.00000]</code>
- when comparing exactly unity against a value which is increased by just one least significant binary digit using
- the default precision for float of just 6 decimal digits, given by
- <code class="computeroutput">std::numeric_limits</code><float>::digits10. The function used for the number of decimal
- digits displayed is that proposed for a future C++ Standard,
- <a href="http://www2.open-std.org/JTC1/SC22/WG21/docs/papers/2005/n1822.pdf" target="_top">A Proposal to add a max
- significant decimal digits value</a>, to be called <code class="computeroutput">std::numeric_limits</code>::max_digits10();.
- For 32-bit floats, 9 decimal digits are needed to ensure a single bit change produces a different decimal digit
- string.
+ The macro BOOST_TEST_PASSPOINT is intended to be used to inject an "unnamed" checkpoint position. The
+ macro signature is as follows:
</p>
+<pre class="inline-synopsis">
+<a name="BOOST_TEST_PASSPOINT"></a>BOOST_TEST_PASSPOINT()</pre>
<p class="first-line-indented">
- So a much more helpful display using 9 decimal digits is thus:
- <code class="computeroutput">[1.00000000 != 1.00000012]</code> showing that the two values are in fact different.
+ Unlike the macro <code class="computeroutput"><a class="link" href="BOOST_TEST_CHECKPOINT.html#BOOST_TEST_CHECKPOINT">BOOST_TEST_CHECKPOINT</a></code> this macro doesn't require any message to be
+ supplied with it. It's just a simple "been there" marker that records file name and line number
+ code passes through.
</p>
-<p class="first-line-indented">
- For <acronym class="acronym">IEEE754</acronym> 32-bit float values - 9 decimal digits are shown. For 64-bit <acronym class="acronym">IEEE754</acronym> double - 17 decimal digits. For
- <acronym class="acronym">IEEE754</acronym> extended long double using 80-bit - 21 decimal digits. For <acronym class="acronym">IEEE754</acronym> quadruple long double 128-bit, and Sparc
- extended long double 128-bit - 36 decimal digits. For floating-point types, a convenient formula to calculate
- max_digits10 is: 2 + <code class="computeroutput">std::numeric_limits</code><FPT>::digits * 3010/10000;
- </p>
-<div class="note"><table border="0" summary="Note">
-<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../../doc/html/images/note.png"></td>
-<th align="left">Note</th>
-</tr>
-<tr><td align="left" valign="top"><p>
- Note that a user defined floating point type UDFPT must define
- <code class="computeroutput">std::numeric_limits</code><UDFPT>::is_specialized = true and provide an appropriate value
- for <code class="computeroutput">std::numeric_limits</code><UDFPT>::digits, the number of bits used for the significand
- or mantissa. For example, for the Sparc extended long double 128, 113 bits are used for the significand (one of
- which is implicit).
- </p></td></tr>
-</table></div>
+<div class="example">
+<a name="utf.user-guide.test-output.log.BOOST_TEST_PASSPOINT.example23"></a><p class="title"><b>Example 29. BOOST_TEST_PASSPOINT usage</b></p>
+<div class="example-contents">
+<pre class="programlisting">#define BOOST_TEST_MODULE example
+#include <boost/test/included/unit_test.hpp>
+
+//____________________________________________________________________________//
+
+BOOST_AUTO_TEST_CASE( test_case )
+{
+ int* p = 0;
+
+ BOOST_TEST_PASSPOINT();
+ ++p;
+
+ BOOST_TEST_PASSPOINT();
+ ++p;
+
+ BOOST_TEST_PASSPOINT();
+ int j = *p;
+}
+
+//____________________________________________________________________________//</pre>
+<table border="0" summary="Simple list" class="simplelist"><tr>
+<td><code class="literal">Source code</code></td>
+<td> | </td>
+<td><code class="literal">Show output</code></td>
+</tr></table>
+<pre class="example-output" id="example23-output">> example
+Running 1 test case...
+unknown location(0): fatal error in "test_case": memory access violation at address: 0x00000008: no mapping at fault address
+test.cpp(16): last checkpoint
+
+*** 1 failure detected in test suite "example"
+</pre>
+</div>
+</div>
+<br class="example-break">
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="BOOST_TEST_PASSPOINT.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="test-log.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="log-hr-format.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="BOOST_TEST_CHECKPOINT.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="test-log.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="FPT.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
</div>
</body>
</html>
Added: trunk/libs/test/doc/html/utf/user-guide/test-output/FPT.html
==============================================================================
--- (empty file)
+++ trunk/libs/test/doc/html/utf/user-guide/test-output/FPT.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -0,0 +1,77 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Logging floating point type numbers</title>
+<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
+<link rel="home" href="../../../index.html" title="Boost Test Library">
+<link rel="up" href="test-log.html" title="Test log output">
+<link rel="prev" href="BOOST_TEST_PASSPOINT.html" title="BOOST_TEST_PASSPOINT">
+<link rel="next" href="log-hr-format.html" title="Human readable log output format">
+<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table width="100%"><tr>
+<td width="10%">
</td>
+<td valign="middle" align="left"> > The Unit Test Framework > User's guide<a href="../../testing-tools.html">
+ >
+ </a>Test Output <a href="../runtime-config.html">
+ >
+ </a>Test log<a href="results-report.html">
+ >
+ </a><b>Logging floating point type numbers</b>
+</td>
+<td><div class="spirit-nav">
+<a href="log-hr-format.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+</div></td>
+</tr></table>
+<hr>
+<div class="section">
+<div class="titlepage"><div><div><h6 class="title">
+<a name="utf.user-guide.test-output.log.FPT"></a>Logging floating point type numbers</h6></div></div></div>
+<p class="first-line-indented">
+ It may appear that floating-point numbers are displayed by the <acronym class="acronym">UTF</acronym> with an excessive number of decimal digits.
+ However the number of digits shown is chosen to avoid apparently nonsensical displays like <code class="computeroutput">[1.00000 != 1.00000]</code>
+ when comparing exactly unity against a value which is increased by just one least significant binary digit using
+ the default precision for float of just 6 decimal digits, given by
+ <code class="computeroutput">std::numeric_limits</code><float>::digits10. The function used for the number of decimal
+ digits displayed is that proposed for a future C++ Standard,
+ <a href="http://www2.open-std.org/JTC1/SC22/WG21/docs/papers/2005/n1822.pdf" target="_top">A Proposal to add a max
+ significant decimal digits value</a>, to be called <code class="computeroutput">std::numeric_limits</code>::max_digits10();.
+ For 32-bit floats, 9 decimal digits are needed to ensure a single bit change produces a different decimal digit
+ string.
+ </p>
+<p class="first-line-indented">
+ So a much more helpful display using 9 decimal digits is thus:
+ <code class="computeroutput">[1.00000000 != 1.00000012]</code> showing that the two values are in fact different.
+ </p>
+<p class="first-line-indented">
+ For <acronym class="acronym">IEEE754</acronym> 32-bit float values - 9 decimal digits are shown. For 64-bit <acronym class="acronym">IEEE754</acronym> double - 17 decimal digits. For
+ <acronym class="acronym">IEEE754</acronym> extended long double using 80-bit - 21 decimal digits. For <acronym class="acronym">IEEE754</acronym> quadruple long double 128-bit, and Sparc
+ extended long double 128-bit - 36 decimal digits. For floating-point types, a convenient formula to calculate
+ max_digits10 is: 2 + <code class="computeroutput">std::numeric_limits</code><FPT>::digits * 3010/10000;
+ </p>
+<div class="note"><table border="0" summary="Note">
+<tr>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../../../../../../../doc/html/images/note.png"></td>
+<th align="left">Note</th>
+</tr>
+<tr><td align="left" valign="top"><p>
+ Note that a user defined floating point type UDFPT must define
+ <code class="computeroutput">std::numeric_limits</code><UDFPT>::is_specialized = true and provide an appropriate value
+ for <code class="computeroutput">std::numeric_limits</code><UDFPT>::digits, the number of bits used for the significand
+ or mantissa. For example, for the Sparc extended long double 128, 113 bits are used for the significand (one of
+ which is implicit).
+ </p></td></tr>
+</table></div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="BOOST_TEST_PASSPOINT.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="test-log.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="log-hr-format.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>
Modified: trunk/libs/test/doc/html/utf/user-guide/test-output/log-ct-config.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-output/log-ct-config.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-output/log-ct-config.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Compile time configuration</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
<link rel="up" href="test-log.html" title="Test log output">
<link rel="prev" href="log-xml-format.html" title="XML based log output format">
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.log.ct-config"></a>Compile time configuration</h6></div></div></div>
<p class="first-line-indented">
@@ -35,7 +35,7 @@
log. The interface is provided by singleton class <code class="computeroutput">boost::unit_test::unit_test_log_t</code> and is
accessible through local file scope reference to single instance of this class: boost::unit_test::unit_test_log.
</p>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.log.ct-config.output-stream"></a>Log output stream redirection</h6></div></div></div>
<p class="first-line-indented">
@@ -48,7 +48,7 @@
cases. There are no limitations on number of output stream resets either.
</p>
<div class="example">
-<a name="utf.user-guide.test-output.log.ct-config.output-stream.example50"></a><p class="title"><b>Example 30. Test log output redirection</b></p>
+<a name="utf.user-guide.test-output.log.ct-config.output-stream.example50"></a><p class="title"><b>Example 30. Test log output redirection</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -75,10 +75,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example50-output">> example
@@ -91,7 +91,7 @@
</div>
<br class="example-break">
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.log.ct-config.log-level"></a>Log level configuration</h6></div></div></div>
<p class="first-line-indented">
@@ -103,7 +103,7 @@
the one supplied at test execution time. Prefer to use runtime parameters for log level selection.
</p>
<div class="example">
-<a name="utf.user-guide.test-output.log.ct-config.log-level.example51"></a><p class="title"><b>Example 31. Compile time log level configuration</b></p>
+<a name="utf.user-guide.test-output.log.ct-config.log-level.example51"></a><p class="title"><b>Example 31. Compile time log level configuration</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -123,10 +123,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example51-output">> example
Running 1 test case...
@@ -138,7 +138,7 @@
</div>
<br class="example-break">
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.log.ct-config.log-format"></a>Predefined log format selection</h6></div></div></div>
<p class="first-line-indented">
@@ -150,7 +150,7 @@
format selection.
</p>
<div class="example">
-<a name="utf.user-guide.test-output.log.ct-config.log-format.example52"></a><p class="title"><b>Example 32. Compile time log format selection</b></p>
+<a name="utf.user-guide.test-output.log.ct-config.log-format.example52"></a><p class="title"><b>Example 32. Compile time log format selection</b></p>
<div class="example-contents">
<pre class="programlisting">#define BOOST_TEST_MODULE example
#include <boost/test/included/unit_test.hpp>
@@ -175,10 +175,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example52-output">> example --report_level=no
<TestLog><Error file="test.cpp" line="18">check false failed</Error></TestLog>
@@ -187,12 +187,12 @@
</div>
<br class="example-break">
</div>
-<div class="section" lang="en"><div class="titlepage"><div><div><h6 class="title">
+<div class="section"><div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.log.ct-config.log-formatter"></a>Custom log format support</h6></div></div></div></div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-output/log-hr-format.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-output/log-hr-format.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-output/log-hr-format.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Human readable log output format</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
<link rel="up" href="test-log.html" title="Test log output">
-<link rel="prev" href="BOOST_TEST_PASSPOINT.html" title="Logging floating point type numbers">
+<link rel="prev" href="FPT.html" title="Logging floating point type numbers">
<link rel="next" href="log-xml-format.html" title="XML based log output format">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
</head>
@@ -22,11 +22,11 @@
</a><b>Human readable format</b>
</td>
<td><div class="spirit-nav">
-<a href="log-xml-format.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a href="log-xml-format.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.log.human-readabe-format"></a>Human readable log output format</h6></div></div></div>
<p class="first-line-indented">
@@ -55,7 +55,7 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p>Running <span class="userinput"><total number of test cases></span> test case(s) </p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p>Running <span class="userinput"><total number of test cases></span> test case(s) …</p></div></code>
</td>
</tr>
</table>
@@ -74,10 +74,10 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p>Platform: $BOOST_PLATFORM<br>
-Compiler: $BOOST_COMPILER<br>
-STL : $BOOST_STDLIB<br>
-Boost : $BOOST_VERSION</p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p>Platform: $BOOST_PLATFORM<br>
+Compiler: $BOOST_COMPILER<br>
+STL     : $BOOST_STDLIB<br>
+Boost   : $BOOST_VERSION</p></div></code>
</td>
</tr>
</table>
@@ -96,7 +96,7 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p>Test is aborted</p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p>Test is aborted</p></div></code>
</td>
</tr>
</table>
@@ -115,7 +115,7 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p>Entering test <span class="userinput"><test unit type></span> <span class="userinput"><test unit name></span></p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p>Entering test <span class="userinput"><test unit type></span> <span class="userinput"><test unit name></span></p></div></code>
</td>
</tr>
</table>
@@ -134,7 +134,7 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p>Leaving test <span class="userinput"><test unit type></span> <span class="userinput"><test unit name></span>; testing time <span class="userinput"><value></span></p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p>Leaving test <span class="userinput"><test unit type></span> <span class="userinput"><test unit name></span>; testing time <span class="userinput"><value></span></p></div></code>
</td>
</tr>
</table>
@@ -153,7 +153,7 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p>Test <span class="userinput"><test unit type></span> <span class="userinput"><test unit name></span> is skipped</p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p>Test <span class="userinput"><test unit type></span> <span class="userinput"><test unit name></span> is skipped</p></div></code>
</td>
</tr>
</table>
@@ -172,8 +172,8 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p>unknown location(0): fatal error in <span class="userinput"><test case name></span>: <span class="userinput"><explanation></span><br>
-<span class="userinput"><last checkpoint location></span>: last checkpoint: <span class="userinput"><checkpoint message></span></p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p>unknown location(0): fatal error in <span class="userinput"><test case name></span>: <span class="userinput"><explanation></span><br>
+<span class="userinput"><last checkpoint location></span>: last checkpoint: <span class="userinput"><checkpoint message></span></p></div></code>
</td>
</tr>
</table>
@@ -192,8 +192,8 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p>unknown location(0): fatal error in <span class="userinput"><test case name></span>: <span class="userinput"><explanation></span><br>
-<span class="userinput"><last checkpoint location></span>: last checkpoint: <span class="userinput"><checkpoint message></span></p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p>unknown location(0): fatal error in <span class="userinput"><test case name></span>: <span class="userinput"><explanation></span><br>
+<span class="userinput"><last checkpoint location></span>: last checkpoint: <span class="userinput"><checkpoint message></span></p></div></code>
</td>
</tr>
</table>
@@ -212,8 +212,8 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p>unknown location(0): fatal error in <span class="userinput"><test case name></span>: <span class="userinput"><explanation></span><br>
-<span class="userinput"><last checkpoint location></span>: last checkpoint: <span class="userinput"><checkpoint message></span></p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p>unknown location(0): fatal error in <span class="userinput"><test case name></span>: <span class="userinput"><explanation></span><br>
+<span class="userinput"><last checkpoint location></span>: last checkpoint: <span class="userinput"><checkpoint message></span></p></div></code>
</td>
</tr>
</table>
@@ -232,7 +232,7 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p><span class="userinput"><assertion location></span>: info: check<span class="userinput"><assertion expression></span> passed</p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p><span class="userinput"><assertion location></span>: info: check<span class="userinput"><assertion expression></span> passed</p></div></code>
</td>
</tr>
</table>
@@ -251,7 +251,7 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p><span class="userinput"><assertion location></span>: warning in <span class="userinput"><test case name></span>: condition <span class="userinput"><assertion description></span> is not satisfied</p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p><span class="userinput"><assertion location></span>: warning in <span class="userinput"><test case name></span>: condition <span class="userinput"><assertion description></span> is not satisfied</p></div></code>
</td>
</tr>
</table>
@@ -270,7 +270,7 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p><span class="userinput"><assertion location></span>: error in <span class="userinput"><test case name></span>: check <span class="userinput"><assertion description></span> failed</p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p><span class="userinput"><assertion location></span>: error in <span class="userinput"><test case name></span>: check <span class="userinput"><assertion description></span> failed</p></div></code>
</td>
</tr>
</table>
@@ -289,7 +289,7 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p><span class="userinput"><assertion location></span>: fatal error in <span class="userinput"><test case name></span>: critical check <span class="userinput"><assertion description></span> failed</p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p><span class="userinput"><assertion location></span>: fatal error in <span class="userinput"><test case name></span>: critical check <span class="userinput"><assertion description></span> failed</p></div></code>
</td>
</tr>
</table>
@@ -308,23 +308,23 @@
<td><strong><nobr><span class="segtitle">Output</span></nobr></strong></td>
<td>: </td>
<td>
- <code class="computeroutput"><div class="literallayout"><p><span class="userinput"><Message content></span></p></div></code>
+ <code class="computeroutput"><div class="literallayout"><p><span class="userinput"><Message content></span></p></div></code>
</td>
</tr>
</table>
<br>
</div>
<p class="first-line-indented">
- Advanced <a class="link" href="../../testing-tools.html" title="The UTF testing tools or tester's toolbox for all occasions">testing tools</a> may produce more complicated error messages.
+ Advanced <a class="link" href="../../testing-tools.html" title="The UTF testing tools … or tester's toolbox for all occasions">testing tools</a> may produce more complicated error messages.
</p>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="BOOST_TEST_PASSPOINT.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="test-log.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="log-xml-format.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
+<a accesskey="p" href="FPT.html"><img src="../../../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="test-log.html"><img src="../../../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../doc/html/images/home.png" alt="Home"></a><a accesskey="n" href="log-xml-format.html"><img src="../../../../../../../doc/html/images/next.png" alt="Next"></a>
</div>
</body>
</html>
Modified: trunk/libs/test/doc/html/utf/user-guide/test-output/log-xml-format.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-output/log-xml-format.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-output/log-xml-format.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>XML based log output format</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
<link rel="up" href="test-log.html" title="Test log output">
<link rel="prev" href="log-hr-format.html" title="Human readable log output format">
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.log.xml-format"></a>XML based log output format</h6></div></div></div>
<p class="first-line-indented">
@@ -36,7 +36,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-output/results-report.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-output/results-report.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-output/results-report.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Test report output</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../test-output.html" title="Test Output or let's see what you got for your money">
+<link rel="up" href="../test-output.html" title="Test Output … or let's see what you got for your money">
<link rel="prev" href="log-ct-config.html" title="Compile time configuration">
<link rel="next" href="test-progress.html" title="Test progress display">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
@@ -24,27 +24,27 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.test-output.results-report"></a>Test report output</h5></div></div></div>
-<div class="section" lang="en"><div class="titlepage"><div><div><h6 class="title">
+<div class="section"><div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.results-report.runtime-config"></a>Runtime configuration</h6></div></div></div></div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.results-report.ct-config"></a>Compile time configuration</h6></div></div></div>
-<div class="section" lang="en"><div class="titlepage"><div><div><h6 class="title">
+<div class="section"><div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.results-report.ct-config.output-stream"></a>Report output stream redirection and access</h6></div></div></div></div>
-<div class="section" lang="en"><div class="titlepage"><div><div><h6 class="title">
+<div class="section"><div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.results-report.ct-config.report-level"></a>Report level configuration</h6></div></div></div></div>
-<div class="section" lang="en"><div class="titlepage"><div><div><h6 class="title">
+<div class="section"><div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.results-report.ct-config.report-format"></a>Predefined report format selection</h6></div></div></div></div>
-<div class="section" lang="en"><div class="titlepage"><div><div><h6 class="title">
+<div class="section"><div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.results-report.ct-config.report-formatter"></a>Custom report format support</h6></div></div></div></div>
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-output/test-log.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-output/test-log.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-output/test-log.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Test log output</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../test-output.html" title="Test Output or let's see what you got for your money">
-<link rel="prev" href="../test-output.html" title="Test Output or let's see what you got for your money">
+<link rel="up" href="../test-output.html" title="Test Output … or let's see what you got for your money">
+<link rel="prev" href="../test-output.html" title="Test Output … or let's see what you got for your money">
<link rel="next" href="BOOST_TEST_MESSAGE.html" title="BOOST_TEST_MESSAGE">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
</head>
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.test-output.log"></a>Test log output</h5></div></div></div>
<p class="first-line-indented">
@@ -35,57 +35,57 @@
appear in the test log output. Log levels are arranged by the "importance" of the log entries. Here is
the list of all levels in order of increasing "importance":
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>
-<p>Success information messages</p>
-<p>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">
+<p class="simpara">Success information messages</p>
+<p class="simpara">
This category includes messages that provide information on successfully passed assertions
</p>
</li>
-<li>
-<p>Test tree traversal notifications</p>
-<p>
+<li class="listitem">
+<p class="simpara">Test tree traversal notifications</p>
+<p class="simpara">
This category includes messages that are produced by the <acronym class="acronym">UTF</acronym> core and indicate which test suites/cases are
currently being executed or skipped
</p>
</li>
-<li>
-<p>General information messages</p>
-<p>
+<li class="listitem">
+<p class="simpara">General information messages</p>
+<p class="simpara">
This category includes general information massages produced in most cases by a test module author using the
macro <code class="computeroutput"><a class="link" href="BOOST_TEST_MESSAGE.html#BOOST_TEST_MESSAGE">BOOST_TEST_MESSAGE</a></code>.
</p>
</li>
-<li>
-<p>Warning messages</p>
-<p>
+<li class="listitem">
+<p class="simpara">Warning messages</p>
+<p class="simpara">
This category includes messages produced by failed warning level assertions.
</p>
</li>
-<li>
-<p>Non fatal error messages</p>
-<p>
+<li class="listitem">
+<p class="simpara">Non fatal error messages</p>
+<p class="simpara">
This category includes messages produced by failed check level assertions
</p>
</li>
-<li>
-<p>Uncaught C++ exceptions notifications</p>
-<p>
+<li class="listitem">
+<p class="simpara">Uncaught C++ exceptions notifications</p>
+<p class="simpara">
This category includes messages that are produced by the <acronym class="acronym">UTF</acronym> and provide detailed information on the C++
exceptions uncaught by the test case body.
</p>
</li>
-<li>
-<p>Non-fatal system error</p>
-<p>
+<li class="listitem">
+<p class="simpara">Non-fatal system error</p>
+<p class="simpara">
This category includes messages that are produced by the <acronym class="acronym">UTF</acronym> itself and provides information about caught
non-fatal system error. For example it includes messages produced in the case of test case timeout or if
floating point values calculation errors are caught.
</p>
</li>
-<li>
-<p>Fatal system error</p>
-<p>
+<li class="listitem">
+<p class="simpara">Fatal system error</p>
+<p class="simpara">
This category includes messages produced by failed require level assertions and by the <acronym class="acronym">UTF</acronym> itself in case of
abnormal test case termination.
</p>
@@ -106,17 +106,17 @@
In addition to the levels described above the test log defines two special log levels. The current log level can
be set to:
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li>
-<p>All messages</p>
-<p>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem">
+<p class="simpara">All messages</p>
+<p class="simpara">
If active log level threshold is set to this value, all test log entries appear in the output. In practice
this is equivalent to setting the active log level threshold to "success information messages"
</p>
</li>
-<li>
-<p>Nothing</p>
-<p>
+<li class="listitem">
+<p class="simpara">Nothing</p>
+<p class="simpara">
If the active log level threshold is set to this value, none of test log entries appear in the output. This log level
is used to execute a "silent" test that doesn't produce any test log and only generates a result code indicating whether test failed or passed.
</p>
@@ -137,21 +137,21 @@
macros for this purpose: <code class="computeroutput"><a class="link" href="BOOST_TEST_CHECKPOINT.html#BOOST_TEST_CHECKPOINT">BOOST_TEST_CHECKPOINT</a></code> - to specify a "named" checkpoint
and <code class="computeroutput"><a class="link" href="BOOST_TEST_PASSPOINT.html#BOOST_TEST_PASSPOINT">BOOST_TEST_PASSPOINT</a></code> - to specify an "unnamed" checkpoint.
</p>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.log.testing-tool-args"></a>Logging tool arguments</h6></div></div></div>
<p class="first-line-indented">
- Most of the <a class="link" href="../../testing-tools.html" title="The UTF testing tools or tester's toolbox for all occasions">testing tools</a> print values of their arguments to the output
+ Most of the <a class="link" href="../../testing-tools.html" title="The UTF testing tools … or tester's toolbox for all occasions">testing tools</a> print values of their arguments to the output
stream in some form of log statement. If arguments type does not support <code class="computeroutput">operator<<(std::ostream&,
ArgumentType const&)</code> interface you will get a compilation error. You can either implement above
- interface or prohibit the <a class="link" href="../../testing-tools.html" title="The UTF testing tools or tester's toolbox for all occasions">testing tools</a> from logging argument values for
+ interface or prohibit the <a class="link" href="../../testing-tools.html" title="The UTF testing tools … or tester's toolbox for all occasions">testing tools</a> from logging argument values for
specified type. To do so use following statement on file level before first test case that includes statement
failing to compile:
</p>
<pre class="inline-synopsis">
<a name="BOOST_TEST_DONT_PRINT_LOG_VALUE"></a>BOOST_TEST_DONT_PRINT_LOG_VALUE(<span class="emphasis"><em>ArgumentType</em></span>)</pre>
<div class="example">
-<a name="utf.user-guide.test-output.log.testing-tool-args.example32"></a><p class="title"><b>Example 26. BOOST_TEST_DONT_PRINT_LOG_VALUE usage</b></p>
+<a name="utf.user-guide.test-output.log.testing-tool-args.example32"></a><p class="title"><b>Example 26. BOOST_TEST_DONT_PRINT_LOG_VALUE usage</b></p>
<div class="example-contents">
<p>
Try to comment out BOOST_TEST_DONT_PRINT_LOG_VALUE statement and you end up with compile time error.
@@ -176,10 +176,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example32-output">Running 1 test case...
test.cpp(16): error in "test_list": check p1 == p2 failed [ != ]
@@ -190,7 +190,7 @@
</div>
<br class="example-break">
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h6 class="title">
<a name="utf.user-guide.test-output.log.runtime-config"></a>Runtime configuration</h6></div></div></div>
<p class="first-line-indented">
@@ -203,7 +203,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-output/test-progress.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-output/test-progress.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-output/test-progress.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Test progress display</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../test-output.html" title="Test Output or let's see what you got for your money">
+<link rel="up" href="../test-output.html" title="Test Output … or let's see what you got for your money">
<link rel="prev" href="results-report.html" title="Test report output">
-<link rel="next" href="../runtime-config.html" title="Runtime configuration or what are the strings I can pull?">
+<link rel="next" href="../runtime-config.html" title="Runtime configuration … or what are the strings I can pull?">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -24,13 +24,13 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.test-output.progress"></a>Test progress display</h5></div></div></div>
<p class="first-line-indented">
In case if the test module involves lengthy computation split among multiple test cases you may be interested in
progress monitor. The test runners supplied with the <acronym class="acronym">UTF</acronym> support simple text progress display, implemented based
- on <code class="computeroutput">boost::progress_display</code><sup>[<a name="id655789" href="#ftn.id655789" class="footnote">5</a>]</sup>. The progress display output
+ on <code class="computeroutput">boost::progress_display</code><sup>[<a name="id494316" href="#ftn.id494316" class="footnote">5</a>]</sup>. The progress display output
is enabled using the <acronym class="acronym">UTF</acronym> parameter <a class="link" href="../runtime-config/reference.html#utf.user-guide.runtime-config.parameters">show_progress</a>.
</p>
<p class="first-line-indented">
@@ -46,7 +46,7 @@
</p>
<pre class="programlisting">boost::unit_test::progress_monitor.set_stream( std::ostream& )</pre>
<div class="example">
-<a name="utf.user-guide.test-output.progress.example49"></a><p class="title"><b>Example 33. Progress report for the test module with large amount of test cases</b></p>
+<a name="utf.user-guide.test-output.progress.example49"></a><p class="title"><b>Example 33. Progress report for the test module with large amount of test cases</b></p>
<div class="example-contents">
<pre class="programlisting">#include <boost/test/included/unit_test.hpp>
using namespace boost::unit_test;
@@ -72,10 +72,10 @@
//____________________________________________________________________________//
</pre>
-<table class="simplelist" border="0" summary="Simple list"><tr>
+<table border="0" summary="Simple list" class="simplelist"><tr>
<td><code class="literal">Source code</code></td>
<td> | </td>
-<td><code class="literal">Show output</code></td>
+<td><code class="literal">Show output</code></td>
</tr></table>
<pre class="example-output" id="example49-output">> example --show_progress=yes --log_level=nothing
@@ -89,12 +89,12 @@
</div>
<br class="example-break"><div class="footnotes">
<br><hr width="100" align="left">
-<div class="footnote"><acronym class="acronym"><sup>[<a name="ftn.id655789" href="#id655789" class="acronym">5</a>] </sup>UTF</acronym></div>
+<div class="footnote"><acronym class="acronym"><sup>[<a name="ftn.id494316" href="#id494316" class="acronym">5</a>] </sup>UTF</acronym></div>
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/test-runners.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/test-runners.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/test-runners.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>The supplied test runners or where is the entrance?</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>The supplied test runners … or where is the entrance?</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
<link rel="up" href="../user-guide.html" title="Unit Test Framework: User's guide">
<link rel="prev" href="usage-variants/extern-test-runner-variant.html" title="The external test runner variant of the UTF">
@@ -24,9 +24,9 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="utf.user-guide.test-runners"></a>The supplied test runners or where is the entrance?</h4></div></div></div>
+<a name="utf.user-guide.test-runners"></a>The supplied test runners … or where is the entrance?</h4></div></div></div>
<p class="first-line-indented">
All usage variants of the <acronym class="acronym">UTF</acronym>, excluding the
<a class="link" href="usage-variants/extern-test-runner.html" title="External test runner variant of the UTF">external test runner</a>, supply the test runner in a form of
@@ -56,7 +56,7 @@
and dynamic library usage variants incompatible and they can't be easily switched on a fly.
</p></td></tr>
</table></div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.static-lib-runner"></a>Static library variant of the <acronym class="acronym">UTF</acronym>
</h5></div></div></div>
@@ -70,7 +70,7 @@
default function main() implementation assumes the name of initialization function is init_unit_test_suite
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.dynamic-lib-runner"></a>Dynamic library variant of the <acronym class="acronym">UTF</acronym>
</h5></div></div></div>
@@ -93,13 +93,13 @@
</tr>
<tr><td align="left" valign="top"><p>
The same flags also govern generation of an empty
- <a class="link" href="initialization.html" title="Test module initialization or ready, set">test module initialization function</a>. This means that if you
+ <a class="link" href="initialization.html" title="Test module initialization … or ready, set …">test module initialization function</a>. This means that if you
need to implement either function main() or initialization function manually, you can't define the above flags
and are required to manually implement both of them.
</p></td></tr>
</table></div>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.single-header-runner"></a>Single-header variant of the <acronym class="acronym">UTF</acronym>
</h5></div></div></div>
@@ -111,7 +111,7 @@
implementation won't be generated.
</p>
</div>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.runners-exit-status"></a>Generated exit status values</h5></div></div></div>
<p class="first-line-indented">
@@ -119,11 +119,11 @@
the summary of all possible generated values:
</p>
<div class="table">
-<a name="utf.user-guide.runners-exit-status-summary"></a><p class="title"><b>Table 4. Generated exit status values</b></p>
+<a name="utf.user-guide.runners-exit-status-summary"></a><p class="title"><b>Table 4. Generated exit status values</b></p>
<div class="table-contents"><table class="table" summary="Generated exit status values">
<colgroup>
-<col>
-<col>
+<col class="c1">
+<col class="c2">
</colgroup>
<thead><tr>
<th>Value</th>
@@ -158,7 +158,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/usage-variants.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/usage-variants.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/usage-variants.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,9 +1,9 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>The UTF usage variants or the Buridan's donkey parable</title>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>The UTF usage variants … or the Buridan's donkey parable</title>
<link rel="stylesheet" href="../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../index.html" title="Boost Test Library">
<link rel="up" href="../user-guide.html" title="Unit Test Framework: User's guide">
<link rel="prev" href="../user-guide.html" title="Unit Test Framework: User's guide">
@@ -24,17 +24,17 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h4 class="title">
-<a name="utf.user-guide.usage-variants"></a>The <acronym class="acronym">UTF</acronym> usage variants or the Buridan's donkey parable</h4></div></div></div>
+<a name="utf.user-guide.usage-variants"></a>The <acronym class="acronym">UTF</acronym> usage variants … or the Buridan's donkey parable</h4></div></div></div>
<p class="first-line-indented">
The <acronym class="acronym">UTF</acronym> presents you with 4 different variants how it can be used.
</p>
-<div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="itemizedlist"><ul type="disc">
-<li><a class="link" href="usage-variants/static-lib-variant.html" title="The static library variant of the UTF">The static library variant</a></li>
-<li><a class="link" href="usage-variants/dynamic-lib-variant.html" title="The dynamic library variant of the UTF">The dynamic library variant</a></li>
-<li><a class="link" href="usage-variants/single-header-variant.html" title="The single-header variant of the UTF">The single-header variant</a></li>
-<li><a class="link" href="usage-variants/extern-test-runner-variant.html" title="The external test runner variant of the UTF">The external test runner variant</a></li>
+<div class="itemizedlist"><ul type="disc">
+<li class="listitem"><a class="link" href="usage-variants/static-lib-variant.html" title="The static library variant of the UTF">The static library variant</a></li>
+<li class="listitem"><a class="link" href="usage-variants/dynamic-lib-variant.html" title="The dynamic library variant of the UTF">The dynamic library variant</a></li>
+<li class="listitem"><a class="link" href="usage-variants/single-header-variant.html" title="The single-header variant of the UTF">The single-header variant</a></li>
+<li class="listitem"><a class="link" href="usage-variants/extern-test-runner-variant.html" title="The external test runner variant of the UTF">The external test runner variant</a></li>
</ul></div>
<p class="first-line-indented">
Unlike the Buridan's donkey though, you shouldn't have problems deciding which one to use, since there are
@@ -49,7 +49,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/usage-variants/dynamic-lib-variant.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/usage-variants/dynamic-lib-variant.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/usage-variants/dynamic-lib-variant.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>The dynamic library variant of the UTF</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../usage-variants.html" title="The UTF usage variants or the Buridan's donkey parable">
+<link rel="up" href="../usage-variants.html" title="The UTF usage variants … or the Buridan's donkey parable">
<link rel="prev" href="static-lib-variant.html" title="The static library variant of the UTF">
<link rel="next" href="single-header-variant.html" title="The single-header variant of the UTF">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
@@ -24,7 +24,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.dynamic-lib-variant"></a>The dynamic library variant of the <acronym class="acronym">UTF</acronym>
</h5></div></div></div>
@@ -57,7 +57,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/usage-variants/extern-test-runner-variant.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/usage-variants/extern-test-runner-variant.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/usage-variants/extern-test-runner-variant.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>The external test runner variant of the UTF</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../usage-variants.html" title="The UTF usage variants or the Buridan's donkey parable">
+<link rel="up" href="../usage-variants.html" title="The UTF usage variants … or the Buridan's donkey parable">
<link rel="prev" href="single-header-variant.html" title="The single-header variant of the UTF">
-<link rel="next" href="../test-runners.html" title="The supplied test runners or where is the entrance?">
+<link rel="next" href="../test-runners.html" title="The supplied test runners … or where is the entrance?">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -24,7 +24,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.extern-test-runner-variant"></a>The external test runner variant of the <acronym class="acronym">UTF</acronym>
</h5></div></div></div>
@@ -57,7 +57,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/usage-variants/extern-test-runner.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/usage-variants/extern-test-runner.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/usage-variants/extern-test-runner.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,13 +1,13 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>External test runner variant of the UTF</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../test-runners.html" title="The supplied test runners or where is the entrance?">
-<link rel="prev" href="../test-runners.html" title="The supplied test runners or where is the entrance?">
-<link rel="next" href="../initialization.html" title="Test module initialization or ready, set">
+<link rel="up" href="../test-runners.html" title="The supplied test runners … or where is the entrance?">
+<link rel="prev" href="../test-runners.html" title="The supplied test runners … or where is the entrance?">
+<link rel="next" href="../initialization.html" title="Test module initialization … or ready, set …">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -26,7 +26,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.external-test-runner"></a>External test runner variant of the <acronym class="acronym">UTF</acronym>
</h5></div></div></div>
@@ -41,7 +41,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/usage-variants/single-header-variant.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/usage-variants/single-header-variant.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/usage-variants/single-header-variant.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,11 +1,11 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>The single-header variant of the UTF</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../usage-variants.html" title="The UTF usage variants or the Buridan's donkey parable">
+<link rel="up" href="../usage-variants.html" title="The UTF usage variants … or the Buridan's donkey parable">
<link rel="prev" href="dynamic-lib-variant.html" title="The dynamic library variant of the UTF">
<link rel="next" href="extern-test-runner-variant.html" title="The external test runner variant of the UTF">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
@@ -24,7 +24,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.single-header-variant"></a>The single-header variant of the <acronym class="acronym">UTF</acronym>
</h5></div></div></div>
@@ -55,7 +55,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
Modified: trunk/libs/test/doc/html/utf/user-guide/usage-variants/static-lib-variant.html
==============================================================================
--- trunk/libs/test/doc/html/utf/user-guide/usage-variants/static-lib-variant.html (original)
+++ trunk/libs/test/doc/html/utf/user-guide/usage-variants/static-lib-variant.html 2010-06-10 18:57:00 EDT (Thu, 10 Jun 2010)
@@ -1,12 +1,12 @@
<html>
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>The static library variant of the UTF</title>
<link rel="stylesheet" href="../../../../style/style.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.0-pre">
<link rel="home" href="../../../index.html" title="Boost Test Library">
-<link rel="up" href="../usage-variants.html" title="The UTF usage variants or the Buridan's donkey parable">
-<link rel="prev" href="../usage-variants.html" title="The UTF usage variants or the Buridan's donkey parable">
+<link rel="up" href="../usage-variants.html" title="The UTF usage variants … or the Buridan's donkey parable">
+<link rel="prev" href="../usage-variants.html" title="The UTF usage variants … or the Buridan's donkey parable">
<link rel="next" href="dynamic-lib-variant.html" title="The dynamic library variant of the UTF">
<script language="JavaScript1.2" src="../../../../js/boost-test.js"></script>
</head>
@@ -24,7 +24,7 @@
</div></td>
</tr></table>
<hr>
-<div class="section" lang="en">
+<div class="section">
<div class="titlepage"><div><div><h5 class="title">
<a name="utf.user-guide.static-lib-variant"></a>The static library variant of the <acronym class="acronym">UTF</acronym>
</h5></div></div></div>
@@ -56,7 +56,7 @@
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2007 Gennadiy Rozental</div></td>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2008 Gennadiy Rozental</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
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