diff --git a/doc/html/aknowledgements.html b/doc/html/aknowledgements.html index e7c62f93..6705bdfb 100755 --- a/doc/html/aknowledgements.html +++ b/doc/html/aknowledgements.html @@ -41,7 +41,7 @@ - +
Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/execution-monitor.html b/doc/html/execution-monitor.html index 482c4e4c..cc1d9bea 100755 --- a/doc/html/execution-monitor.html +++ b/doc/html/execution-monitor.html @@ -61,8 +61,8 @@
- - + +

Last revised: , at

Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/execution-monitor/compilation.html b/doc/html/execution-monitor/compilation.html index 3a6b166b..7cf041c4 100755 --- a/doc/html/execution-monitor/compilation.html +++ b/doc/html/execution-monitor/compilation.html @@ -69,7 +69,7 @@
- +
Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/execution-monitor/reference.html b/doc/html/execution-monitor/reference.html index b8e06abc..2d6bd651 100755 --- a/doc/html/execution-monitor/reference.html +++ b/doc/html/execution-monitor/reference.html @@ -50,14 +50,14 @@ class execution_monitor { public: // construct/copy/destruct - execution_monitor(); + execution_monitor(); - // execution - int execute(unit_test::callback0<int> const&); + // execution + int execute(unit_test::callback0<int> const&); - // registration + // registration template<typename Exception, typename ExceptionTranslator> - void register_exception_translator(ExceptionTranslator const&, + void register_exception_translator(ExceptionTranslator const&, boost::type<Exception>* = 0); // public data members @@ -80,14 +80,14 @@ };
-

Description

+

Description

-

+

execution_monitor public construct/copy/destruct

  1. -
    execution_monitor();
    +
    execution_monitor();
    @@ -104,10 +104,10 @@
    -

    -execution_monitor execution

    +

    +execution_monitor execution

    1. -
      int execute(unit_test::callback0<int> const& F);
      +
      int execute(unit_test::callback0<int> const& F);
    @@ -141,11 +141,11 @@
    -

    -execution_monitor registration

    +

    +execution_monitor registration

    1. template<typename Exception, typename ExceptionTranslator> 
-  void register_exception_translator(ExceptionTranslator const& tr, 
+  void register_exception_translator(ExceptionTranslator const& tr, 
                                      boost::type<Exception>* dummy = 0);
      register custom (user supplied) exception translator
    @@ -187,7 +187,7 @@ enumerror_code;};
    -

    Description

    +

    Description

    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 @@ -206,7 +206,7 @@ enum error_code { no_error, user_error, cpp_exception_error, system_error, timeout_error, user_fatal_error, system_fatal_error };

    -

    Description

    +

    Description

    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 @@ -272,7 +272,7 @@ class system_error { public: // construct/copy/destruct - system_error(); + system_error(); // public data members unit_test::readonly_property<long> p_errno; // @@ -280,14 +280,14 @@ };

    -

    Description

    +

    Description

    -

    +

    system_error public construct/copy/destruct

    1. -
      system_error();
      +
      system_error();
    @@ -309,7 +309,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/execution-monitor/user-guide.html b/doc/html/execution-monitor/user-guide.html index 6948d2c8..503affd3 100755 --- a/doc/html/execution-monitor/user-guide.html +++ b/doc/html/execution-monitor/user-guide.html @@ -54,7 +54,7 @@

    Monitored function execution

    - To start the monitored function, invoke the method execution_monitor::execute and pass + To start the monitored function, invoke the method execution_monitor::execute 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:

    @@ -128,7 +128,7 @@

    Finally, if you need to abort the monitored function execution without reporting any errors, you can throw an exception execution_aborted. As a result the execution is aborted and zero result code - is produced by the method execution_monitor::execute. + is produced by the method execution_monitor::execute.

    @@ -154,7 +154,7 @@ void break_memory_alloc( long mem_alloc_order_num );
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/faq.html b/doc/html/faq.html index 8225cfcc..ed291975 100755 --- a/doc/html/faq.html +++ b/doc/html/faq.html @@ -28,40 +28,40 @@

    Frequently Asked Questions

    -
    -
    +
    +
    Where the latest version of the Boost Test Library is located?
    -
    +
    I found a bug. Where can I report it?
    -
    +
    I have a request for a new feature. Where can I ask for it?
    -
    +
    How to create test case using the Unit Test Framework?
    -
    +
    How to create test suite using the Unit Test Framework?
    -
    +
    Why did I get a linker error when compiling my test program?
    -
    +
    How can I redirect testing output?
    -
    +
    I want different default log trace level
    -
    +
    Is there DLL version of Boost.Test components available on Win32 platform?
    @@ -72,7 +72,7 @@ - +

    Where the latest version of the Boost Test Library is located? @@ -86,7 +86,7 @@ - +

    I found a bug. Where can I report it? @@ -96,12 +96,12 @@

    You can send a bug report to the boost users' mailing list and/or directly to - Gennadiy Rozental. + Gennadiy Rozental.

    - +

    I have a request for a new feature. Where can I ask for it? @@ -111,12 +111,12 @@

    You can send a request to the boost developers' mailing list and/or directly to - Gennadiy Rozental. + Gennadiy Rozental.

    - +

    How to create test case using the Unit Test Framework? @@ -131,7 +131,7 @@ - +

    How to create test suite using the Unit Test Framework? @@ -146,7 +146,7 @@ - +

    Why did I get a linker error when compiling my test program? @@ -172,7 +172,7 @@ - +

    How can I redirect testing output? @@ -187,7 +187,7 @@ - +

    I want different default log trace level @@ -203,7 +203,7 @@ - +

    Is there DLL version of Boost.Test components available on Win32 platform? @@ -221,7 +221,7 @@

    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/index.html b/doc/html/index.html index b1185c02..d73ce80f 100755 --- a/doc/html/index.html +++ b/doc/html/index.html @@ -25,9 +25,9 @@
    -

    Copyright © 2001-2011 Gennadiy Rozental

    +

    Copyright © 2001-2012 Gennadiy Rozental

    -

    +

    Use, modification and distribution is subject to the Boost Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt ) @@ -125,7 +125,7 @@

    Test module initialization
    Supplied test runners
    External test runner
    -
    Introduction
    +
    Glossary
    Usage recommendations
    @@ -151,7 +151,7 @@
    - +

    Last revised: , at

    diff --git a/doc/html/intro.html b/doc/html/intro.html index 48db26b9..28c3f2a5 100755 --- a/doc/html/intro.html +++ b/doc/html/intro.html @@ -80,7 +80,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/minimal.html b/doc/html/minimal.html index ef8e8644..a0196e4a 100755 --- a/doc/html/minimal.html +++ b/doc/html/minimal.html @@ -92,9 +92,9 @@ int test_main( int, char *[] ) // note the name! - + - +
    Source code | Show annotationsShow annotations | Show outputShow output
    @@ -183,8 +183,8 @@ BOOST_FAIL(message)
    - - + +

    Last revised: , at

    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/open-issues.html b/doc/html/open-issues.html index a153bae3..a29d6288 100755 --- a/doc/html/open-issues.html +++ b/doc/html/open-issues.html @@ -56,7 +56,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/prg-exec-monitor.html b/doc/html/prg-exec-monitor.html index c6ee80b8..c6dbfb05 100755 --- a/doc/html/prg-exec-monitor.html +++ b/doc/html/prg-exec-monitor.html @@ -95,7 +95,7 @@ int cpp_main( int, char* [] ) // note name cpp_main, not main. - +
    Source code | Show outputShow output 
    Hello, world
 
@@ -141,7 +141,7 @@ int cpp_main( int, char* [] ) // note the name
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    **** exception(205): std::runtime_error: big trouble
 ******** errors detected; see standard output for details ********
    
@@ -175,7 +175,7 @@ int cpp_main( int, char* [] ) // note the name
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    **** error return code: 5
 ******** errors detected; see standard output for details ********
    
@@ -239,8 +239,8 @@ int cpp_main( int, char* [] ) // note the name
    - - + +

    Last revised: , at

    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/prg-exec-monitor/compilation.html b/doc/html/prg-exec-monitor/compilation.html index 15a0cd3c..fd7a3e08 100755 --- a/doc/html/prg-exec-monitor/compilation.html +++ b/doc/html/prg-exec-monitor/compilation.html @@ -65,7 +65,7 @@

    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 implementation need to be - listed as source files in your makefile[10]. + listed as source files in your makefile[10].

    The makefile for use with Boost.Build system is supplied in libs/test/build @@ -88,7 +88,7 @@

    Dynamic library compilation

    - To build the dynamic library[11] you + To build the dynamic library[11] you need to add BOOST_TEST_DYN_LINK 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 libs/test/build directory: @@ -142,19 +142,19 @@


    -

    [10] There are varieties of make systems that can be used. To name +

    [10] There are varieties of make systems that can be used. To name a few: GNU make (and other make clones) and build systems integrated into IDEs (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.

    -

    [11] What is meant by the term dynamic library is a dynamically +

    [11] What is meant by the term dynamic library is a dynamically loaded library, alternatively called a shared library.

    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/prg-exec-monitor/impl.html b/doc/html/prg-exec-monitor/impl.html index 465960d6..e70026d2 100755 --- a/doc/html/prg-exec-monitor/impl.html +++ b/doc/html/prg-exec-monitor/impl.html @@ -54,7 +54,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/tutorials/hello-the-testing-world.html b/doc/html/tutorials/hello-the-testing-world.html index 981028ae..8b0e02f5 100755 --- a/doc/html/tutorials/hello-the-testing-world.html +++ b/doc/html/tutorials/hello-the-testing-world.html @@ -183,7 +183,7 @@ BOOST_AUTO_TEST_CASE( my_test )
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/tutorials/intro-in-testing.html b/doc/html/tutorials/intro-in-testing.html index 1a56c89c..fb25df41 100755 --- a/doc/html/tutorials/intro-in-testing.html +++ b/doc/html/tutorials/intro-in-testing.html @@ -36,7 +36,7 @@

    Copyright © 2006 John R. Phillips

    -

    +

    Use, modification and distribution is subject to the Boost Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt ) @@ -207,7 +207,7 @@ int main()

    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/tutorials/new-year-resolution.html b/doc/html/tutorials/new-year-resolution.html index 31d5c232..c111ad29 100755 --- a/doc/html/tutorials/new-year-resolution.html +++ b/doc/html/tutorials/new-year-resolution.html @@ -198,7 +198,7 @@ BOOST_AUTO_TEST_CASE( data_access_test )
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf.html b/doc/html/utf.html index ffcb6a3c..64fe57e9 100644 --- a/doc/html/utf.html +++ b/doc/html/utf.html @@ -108,7 +108,7 @@
    Test module initialization
    Supplied test runners
    External test runner
    -
    Introduction
    +
    Glossary
    Usage recommendations
    @@ -121,8 +121,8 @@
    - - + +

    Last revised: , at

    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/compilation.html b/doc/html/utf/compilation.html index 2564b129..2d3bfca5 100755 --- a/doc/html/utf/compilation.html +++ b/doc/html/utf/compilation.html @@ -41,7 +41,7 @@ The UTF is comparatively complicated component and is implemented in close to hundred header and source files, so for long term usage the preferable solution is to build the UTF as a reusable standalone library. Depending on your platform this may save you a significant time during test module compilation and doesn't - really require that much effort [1]. + really require that much effort [1]. Boost Getting started tells you how to get pre-built libraries for some platforms. If available, this is the easiest option and you can ignore standalone library compilation instructions below. @@ -143,14 +143,14 @@

    -

    [1] If you are using Visual studio compilers do not forget to +

    [1] If you are using Visual studio compilers do not forget to set a subsystem to console when you build test modules. You can do it either in project properties or by setting command line /SUBSYTEM:CONSOLE. Number of people reported link error caused specifically by this omission

    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/compilation/auto-linking.html b/doc/html/utf/compilation/auto-linking.html index 297c1d1c..ea035ee2 100755 --- a/doc/html/utf/compilation/auto-linking.html +++ b/doc/html/utf/compilation/auto-linking.html @@ -37,7 +37,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/compilation/direct-include.html b/doc/html/utf/compilation/direct-include.html index 46c3f2a6..6e83fd44 100755 --- a/doc/html/utf/compilation/direct-include.html +++ b/doc/html/utf/compilation/direct-include.html @@ -43,7 +43,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/compilation/standalone.html b/doc/html/utf/compilation/standalone.html index 4d69fd44..639aaa04 100755 --- a/doc/html/utf/compilation/standalone.html +++ b/doc/html/utf/compilation/standalone.html @@ -30,7 +30,7 @@

    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 UTF implementation need to be - listed as source files in your makefile[2]. + listed as source files in your makefile[2].

    The Jamfile for use with Boost.Build system is supplied in libs/test/build @@ -54,7 +54,7 @@

    Dynamic library compilation

    - To build the dynamic library[3] you + To build the dynamic library[3] you need to add BOOST_TEST_DYN_LINK 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 libs/test/build directory: @@ -77,19 +77,19 @@


    -

    [2] There are varieties of make systems that can be used. To name +

    [2] There are varieties of make systems that can be used. To name a few: GNU make (and other make clones) and build systems integrated into IDEs (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.

    -

    [3] What is meant by the term dynamic library is a dynamically +

    [3] What is meant by the term dynamic library is a dynamically loaded library, alternatively called a shared library.

    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/examples-collection.html b/doc/html/utf/examples-collection.html index 7b2f1cd3..4e2c8bd6 100644 --- a/doc/html/utf/examples-collection.html +++ b/doc/html/utf/examples-collection.html @@ -204,7 +204,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/intro.html b/doc/html/utf/intro.html index 24544394..f87dae38 100755 --- a/doc/html/utf/intro.html +++ b/doc/html/utf/intro.html @@ -94,7 +94,7 @@

- The UTF keeps track of all passed/failed testing tools assertions, + The UTF keeps track of all passed/failed testing tools assertions, provides an ability to check the test progress and generates a result report in several different formats. The UTF supplies command line test runners that initialize the framework and run the requested tests. @@ -129,7 +129,7 @@

- +
Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/utf/tutorials.html b/doc/html/utf/tutorials.html index e86340d1..233446b6 100755 --- a/doc/html/utf/tutorials.html +++ b/doc/html/utf/tutorials.html @@ -44,7 +44,7 @@
- +
Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/utf/usage-recommendations.html b/doc/html/utf/usage-recommendations.html index 8b9dddb0..30f5f739 100755 --- a/doc/html/utf/usage-recommendations.html +++ b/doc/html/utf/usage-recommendations.html @@ -6,7 +6,7 @@ - + @@ -42,7 +42,7 @@
- +
Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/utf/usage-recommendations/command-line-specific.html b/doc/html/utf/usage-recommendations/command-line-specific.html index 1c8ff5b9..fcb23162 100755 --- a/doc/html/utf/usage-recommendations/command-line-specific.html +++ b/doc/html/utf/usage-recommendations/command-line-specific.html @@ -28,13 +28,13 @@

Command line usage recommendations

-
-
+
+
If you got fatal exception somewhere within test case, make program generate coredump by adding extra command line argument
-
+
How to use test module build with Boost.Test framework under management of automated regression test facilities?
@@ -45,7 +45,7 @@ - +

If you got fatal exception somewhere within test case, make program generate coredump by adding extra command @@ -63,7 +63,7 @@ - +

How to use test module build with Boost.Test framework under management of automated regression test facilities? @@ -89,7 +89,7 @@

- +
Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/utf/usage-recommendations/dot-net-specific.html b/doc/html/utf/usage-recommendations/dot-net-specific.html index 9e3f5354..d76cdec3 100755 --- a/doc/html/utf/usage-recommendations/dot-net-specific.html +++ b/doc/html/utf/usage-recommendations/dot-net-specific.html @@ -28,12 +28,12 @@

Microsoft Visual Studio .NET usage recommendations

-
-
+
+
Use custom build step to automatically start test program after compilation
-
+
If you got fatal exception somewhere within test case, make debugger break at the point the failure by adding extra command line argument @@ -45,7 +45,7 @@ - +

Use custom build step to automatically start test program after compilation @@ -73,7 +73,7 @@ - +

If you got fatal exception somewhere within test case, make debugger break at the point the failure by adding @@ -100,7 +100,7 @@

- +
Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/utf/usage-recommendations/generic.html b/doc/html/utf/usage-recommendations/generic.html index 06992d7c..d98f6ecd 100755 --- a/doc/html/utf/usage-recommendations/generic.html +++ b/doc/html/utf/usage-recommendations/generic.html @@ -28,25 +28,25 @@

Generic usage recommendations

-
-
+
+
Prefer offline compiled libraries to the inline included components
-
+
If you use only free function based test cases advance to the automatic registration facility
-
+
To find location of first error reported by test tool within reused template function, use special hook within framework headers
-
+
To test reusable template base component with different template parameter use test case template facility
-
+
Prefer BOOST_CHECK_EQUAL to BOOST_CHECK
@@ -57,7 +57,7 @@ - +

Prefer offline compiled libraries to the inline included components @@ -74,7 +74,7 @@ - +

If you use only free function based test cases advance to the automatic registration facility @@ -89,7 +89,7 @@ - +

To find location of first error reported by test tool within reused template function, use special hook within @@ -110,7 +110,7 @@ - +

To test reusable template base component with different template parameter use test case template facility @@ -149,7 +149,7 @@ void my_component_test() - +

Prefer BOOST_CHECK_EQUAL to BOOST_CHECK @@ -171,7 +171,7 @@ void my_component_test()

- +
Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/utf/user-guide.html b/doc/html/utf/user-guide.html index 5083d5ed..8a355c1d 100644 --- a/doc/html/utf/user-guide.html +++ b/doc/html/utf/user-guide.html @@ -95,7 +95,7 @@
Test module initialization
Supplied test runners
External test runner
-
Introduction
+
Glossary
@@ -112,7 +112,7 @@

Well … This is a User's Guide after all. Let's go by what you need to know to successfully use the UTF. Thus I follow the order of decisions you as a user have to make and order of complexity of the problems you have to solve. If you find yourself - faces with some unclear term feel free to jump directly to the Glossary section, + faces with some unclear term feel free to jump directly to the Glossary section, where I collection short definition for all used terms. And again if you want to jump right into coding the Tutorials section would be a better place to start.

@@ -148,8 +148,8 @@
- - + +

Last revised: , at

Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/utf/user-guide/fixture.html b/doc/html/utf/user-guide/fixture.html index 259c5f7e..8647b8f4 100755 --- a/doc/html/utf/user-guide/fixture.html +++ b/doc/html/utf/user-guide/fixture.html @@ -112,7 +112,7 @@ BOOST_AUTO_TEST_CASE( test_case2 )
- +
Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/utf/user-guide/fixture/global.html b/doc/html/utf/user-guide/fixture/global.html index 2d5aeafb..2092dddb 100755 --- a/doc/html/utf/user-guide/fixture/global.html +++ b/doc/html/utf/user-guide/fixture/global.html @@ -103,7 +103,7 @@ BOOST_AUTO_TEST_CASE( test_case ) - +
Source code | Show outputShow output 
> example
 global setup
@@ -118,7 +118,7 @@ global teardown
- +
Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/utf/user-guide/fixture/model.html b/doc/html/utf/user-guide/fixture/model.html index c767d52b..4d70f502 100755 --- a/doc/html/utf/user-guide/fixture/model.html +++ b/doc/html/utf/user-guide/fixture/model.html @@ -56,7 +56,7 @@
- +
Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/utf/user-guide/fixture/per-test-case.html b/doc/html/utf/user-guide/fixture/per-test-case.html index b02bd527..639e8f73 100755 --- a/doc/html/utf/user-guide/fixture/per-test-case.html +++ b/doc/html/utf/user-guide/fixture/per-test-case.html @@ -85,7 +85,7 @@ BOOST_AUTO_TEST_CASE( test_case3 ) - +
Source code | Show outputShow output 
> example --log_level=message
 Running 3 test cases...
@@ -103,7 +103,7 @@ teardown fixture
- +
Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/utf/user-guide/fixture/test-suite-shared.html b/doc/html/utf/user-guide/fixture/test-suite-shared.html index e9aaf293..b4230651 100755 --- a/doc/html/utf/user-guide/fixture/test-suite-shared.html +++ b/doc/html/utf/user-guide/fixture/test-suite-shared.html @@ -101,7 +101,7 @@ BOOST_AUTO_TEST_SUITE_END() - +
Source code | Show outputShow output 
> example
 Running 2 test cases...                                                         
@@ -115,7 +115,7 @@ test.cpp(17): error in "test_case1": check i == 1 failed
- +
Copyright © 2001-2011 Gennadiy Rozental
Copyright © 2001-2012 Gennadiy Rozental
diff --git a/doc/html/utf/user-guide/glossary.html b/doc/html/utf/user-guide/glossary.html index 61d3910d..4cb1a8cc 100644 --- a/doc/html/utf/user-guide/glossary.html +++ b/doc/html/utf/user-guide/glossary.html @@ -1,7 +1,7 @@ -Glossary … or what's your name? + @@ -25,81 +25,82 @@
-

-Glossary … or what's your name?

+
+
+
+Glossary … or what's your name?

- Here the list of terms used throughout the this documentation. -

-
-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The test module:

 + Here is the list of terms used throughout this documentation. +

+
+
+The test module +
+

This is a single binary that performs the test. Physically a test module consists of one or more test source files, which can be built into an executable or a dynamic library. A test module that consists of a single test source file is called single-file test module. Otherwise it's called multi-file test module. Logically a test - module consists of four parts: test setup (or test initialization), - test body, test cleanup and - test runner. The test runner part is optional. If a test module is built as + module consists of four parts: test setup (or test initialization), + test body, test cleanup and + test runner. The test runner part is optional. If a test module is built as an executable the test runner is built-in. If a test module is built as a dynamic library, it is run by an external test runner. -

The test body:

 +

+
+The test body +
+

This is the part of a test module that actually performs the test. - Logically test body is a collection of test assertions wrapped in - test cases, which are organized in a test tree + Logically test body is a collection of test assertions wrapped in + test cases, which are organized in a test tree . -

The test tree:

 - This is a hierarchical structure of test suites (non-leaf nodes) and - test cases (leaf nodes). -

The test unit:

 - This is a collective name when referred to either test suite or - test case -

Test assertion:

 -

+

+
+The test tree +
+

+ This is a hierarchical structure of test suites (non-leaf nodes) and + test cases (leaf nodes). +

+
+The test unit +
+

+ This is a collective name when referred to either test suite or + test case +

+
+Test assertion +
+
+

This is a single binary condition (binary in a sense that is has two outcomes: pass and fail) checked by a test module.

-

+

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 test module. The UTF supports both approaches.

-

The test case:

 + +
+The test case +
+

This is an independently monitored function within a test module that consists of one or more test assertions. The term "independently monitored" in the definition above is used to emphasize the fact, that all test cases are monitored independently. An uncaught exception or other normal test case execution termination doesn't cause the testing to cease. Instead the error is caught by the test case execution monitor, reported by the UTF and testing proceeds to the next test case. Later on you are going to see that this is on of the primary reasons to prefer multiple small test cases to a single big test function. -

The test suite:

 -

+

+
+The test suite +
+
+

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:

@@ -110,17 +111,17 @@
  • To see test report split by groups of test cases
  • To skip groups of test cases based on the result of another test unit in a test tree.
    • -

    +

    A test suite can also contain other test suites, thus allowing a hierarchical test tree structure to be formed. The UTF 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.

    -

    The test setup:

    		 -

    + +

    +The test setup +
    +
    +

    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:

    @@ -135,28 +136,28 @@ Global test module setup code -

    +

    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.

    -

    The test cleanup:

    		 + +
    +The test cleanup +
    +

    This is the part of test module that is responsible for cleanup operations. -

    The test fixture:

    		 +

    +
    +The test fixture +
    +

    Matching setup and cleanup operations are frequently united into a single entity called test fixture. -

    The test runner:

    		 -

    +

    +
    +The test runner +
    +
    +

    This is an "executive manager" that runs the show. The test runner's functionality should include the following interfaces and operations:

    @@ -188,27 +189,26 @@ An advanced test runner may provide additional features, including interactive GUI interfaces, test coverage and profiling support.

    -

    The test log:

    		 + +
    +The test log +
    +

    This is the record of all events that occur during the testing. -

    The test results report:

    		 +

    +
    +The test results report +
    +

    This is the report produced by the UTF after the testing is completed, that indicates which test cases/test suites passed and which failed. -

    +

    + +
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/initialization.html b/doc/html/utf/user-guide/initialization.html index 97a407bc..4f1b07f7 100755 --- a/doc/html/utf/user-guide/initialization.html +++ b/doc/html/utf/user-guide/initialization.html @@ -51,7 +51,7 @@ with the dynamic library variant of the UTF requires the specific initialization function signature only.

    - For many test modules you don't need to do any custom initialization + For many test modules you don't need to do any custom initialization and test tree construction is automated. In this case you don't really need the initialization function and the UTF provides a way to automatically generate an empty one for you.

    @@ -150,7 +150,7 @@ typedef test_suite* (*init_unit_test_func)( int, char* [] );
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/runtime-config.html b/doc/html/utf/user-guide/runtime-config.html index 1cda36bc..a32eb724 100755 --- a/doc/html/utf/user-guide/runtime-config.html +++ b/doc/html/utf/user-guide/runtime-config.html @@ -60,7 +60,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/runtime-config/reference.html b/doc/html/utf/user-guide/runtime-config/reference.html index 685e20b3..d10c4348 100755 --- a/doc/html/utf/user-guide/runtime-config/reference.html +++ b/doc/html/utf/user-guide/runtime-config/reference.html @@ -35,29 +35,29 @@ acceptable values list. All values are case sensitive and are required to exactly match the parameter specification.

    @@ -844,7 +844,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/runtime-config/run-by-name.html b/doc/html/utf/user-guide/runtime-config/run-by-name.html index df860930..850e94be 100755 --- a/doc/html/utf/user-guide/runtime-config/run-by-name.html +++ b/doc/html/utf/user-guide/runtime-config/run-by-name.html @@ -247,7 +247,7 @@ Leaving test suite "example"
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-organization.html b/doc/html/utf/user-guide/test-organization.html index e850e632..f09f4808 100755 --- a/doc/html/utf/user-guide/test-organization.html +++ b/doc/html/utf/user-guide/test-organization.html @@ -54,7 +54,7 @@

    - The above points should make it clear that it's preferable to split test module + The above points should make it clear that it's preferable to split test module into smaller units. These units are test cases. A test case has to be constructed based on some kind of function and registered in a test tree, so that the test runner knows how to invoke it. There are different possible designs for the test case construction problem: inheritance from the predefined base class, specifically @@ -102,7 +102,7 @@

    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-organization/auto-nullary-test-case.html b/doc/html/utf/user-guide/test-organization/auto-nullary-test-case.html index f3f12924..e51beb82 100755 --- a/doc/html/utf/user-guide/test-organization/auto-nullary-test-case.html +++ b/doc/html/utf/user-guide/test-organization/auto-nullary-test-case.html @@ -61,7 +61,7 @@ BOOST_AUTO_TEST_CASE( free_test_function ) - +
    Source code | Show outputShow output 
    > example --log_level=test_suite
 Running 1 test case...
@@ -81,7 +81,7 @@ Leaving test suite "example"
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-organization/auto-test-case-template.html b/doc/html/utf/user-guide/test-organization/auto-test-case-template.html index becbdcbb..cf0bc39a 100755 --- a/doc/html/utf/user-guide/test-organization/auto-test-case-template.html +++ b/doc/html/utf/user-guide/test-organization/auto-test-case-template.html @@ -75,7 +75,7 @@ BOOST_AUTO_TEST_CASE_TEMPLATE( my_test, T, test_types ) - +
    Source code | Show outputShow output 
    > example
 Running 3 test cases...
@@ -89,7 +89,7 @@ test.cpp(12): error in "my_test<unsigned char>": check sizeof(T) == 4 fail
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-organization/auto-test-suite.html b/doc/html/utf/user-guide/test-organization/auto-test-suite.html index 86c92bd1..7d996242 100755 --- a/doc/html/utf/user-guide/test-organization/auto-test-suite.html +++ b/doc/html/utf/user-guide/test-organization/auto-test-suite.html @@ -93,7 +93,7 @@ BOOST_AUTO_TEST_SUITE_END() - +
    Source code | Show outputShow output 
    > example
 Running 4 test cases...
@@ -142,7 +142,7 @@ BOOST_AUTO_TEST_SUITE_END()
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    >example --report_level=detailed
 Running 3 test cases...
@@ -173,7 +173,7 @@ Test suite "example" failed with:
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-organization/expected-failures.html b/doc/html/utf/user-guide/test-organization/expected-failures.html index 00f76233..bddaee9a 100755 --- a/doc/html/utf/user-guide/test-organization/expected-failures.html +++ b/doc/html/utf/user-guide/test-organization/expected-failures.html @@ -100,7 +100,7 @@ init_unit_test_suite( int, char* [] ) { - +
    Source code | Show outputShow output 
    > example --log_level=message
 Running 1 test case...
@@ -160,7 +160,7 @@ BOOST_AUTO_TEST_SUITE_END()
    - +
    Source code | Show outputShow output 
    > example --report_level=short
 Running 2 test cases...
@@ -180,7 +180,7 @@ Test suite "example" passed with:
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-organization/manual-nullary-test-case.html b/doc/html/utf/user-guide/test-organization/manual-nullary-test-case.html index 373ce57e..9d4d529a 100755 --- a/doc/html/utf/user-guide/test-organization/manual-nullary-test-case.html +++ b/doc/html/utf/user-guide/test-organization/manual-nullary-test-case.html @@ -77,7 +77,7 @@ init_unit_test_suite( int argc, char* argv[] ) - +
    Source code | Show outputShow output 
    > example
 Running 1 test case...
@@ -135,7 +135,7 @@ init_unit_test_suite( int argc, char* argv[] )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -185,7 +185,7 @@ init_unit_test_suite( int argc, char* argv[] )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 2 test cases...
@@ -238,7 +238,7 @@ init_unit_test_suite( int argc, char* argv[] )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -307,7 +307,7 @@ main( int argc, char* argv[] )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 3 test cases...
@@ -323,7 +323,7 @@ Running 3 test cases...
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-organization/manual-test-case-template.html b/doc/html/utf/user-guide/test-organization/manual-test-case-template.html index bc5c880c..58812312 100755 --- a/doc/html/utf/user-guide/test-organization/manual-test-case-template.html +++ b/doc/html/utf/user-guide/test-organization/manual-test-case-template.html @@ -150,7 +150,7 @@ init_unit_test_suite( int argc, char* argv[] ) - +
    Source code | Show outputShow output 
    > example
 Running 3 test cases...
@@ -164,7 +164,7 @@ test.cpp(10): error in "my_test<unsigned char>": check sizeof(T) == 4 fail
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-organization/manual-test-suite.html b/doc/html/utf/user-guide/test-organization/manual-test-suite.html index 30174e30..0dca2495 100755 --- a/doc/html/utf/user-guide/test-organization/manual-test-suite.html +++ b/doc/html/utf/user-guide/test-organization/manual-test-suite.html @@ -64,7 +64,7 @@ The third optional parameter - timeout - defines the timeout value for the test unit. As of now the UTF 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 - boost::execution_monitor::execute for more details about the timeout value. + boost::execution_monitor::execute for more details about the timeout value.

    To register group of test units in one function call the boost::unit_test::test_suite provides another add @@ -136,7 +136,7 @@ init_unit_test_suite( int argc, char* argv[] ) - +
    Source code | Show outputShow output 

    > example --log_level=test_suite
 Running 4 test cases...
@@ -166,7 +166,7 @@ Leaving test suite "Master Test Suite"
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-organization/master-test-suite.html b/doc/html/utf/user-guide/test-organization/master-test-suite.html index c828f3f8..136638f4 100755 --- a/doc/html/utf/user-guide/test-organization/master-test-suite.html +++ b/doc/html/utf/user-guide/test-organization/master-test-suite.html @@ -121,7 +121,7 @@ init_unit_test_suite( int argc, char* argv[] ) - +
    Source code | Show outputShow output 
    > example 1
 Test setup error: test tree is empty
    @@ -163,7 +163,7 @@ BOOST_AUTO_TEST_CASE( free_test_function ) - +
    Source code | Show outputShow output 
    > example --log_level=test_suite
 Running 1 test case...
@@ -209,7 +209,7 @@ init_unit_test_suite( int argc, char* argv[] )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example --log_level=test_suite
 Running 1 test case...
@@ -228,7 +228,7 @@ Leaving test suite "my master test suite name"
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-organization/nullary-test-case.html b/doc/html/utf/user-guide/test-organization/nullary-test-case.html index fe52452c..4e3dda32 100755 --- a/doc/html/utf/user-guide/test-organization/nullary-test-case.html +++ b/doc/html/utf/user-guide/test-organization/nullary-test-case.html @@ -48,7 +48,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-organization/test-case-template.html b/doc/html/utf/user-guide/test-organization/test-case-template.html index 06f4c34b..56633b5d 100755 --- a/doc/html/utf/user-guide/test-organization/test-case-template.html +++ b/doc/html/utf/user-guide/test-organization/test-case-template.html @@ -50,7 +50,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-organization/test-suite.html b/doc/html/utf/user-guide/test-organization/test-suite.html index 7d6a30fa..16e5304b 100755 --- a/doc/html/utf/user-guide/test-organization/test-suite.html +++ b/doc/html/utf/user-guide/test-organization/test-suite.html @@ -55,7 +55,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-organization/unary-test-case.html b/doc/html/utf/user-guide/test-organization/unary-test-case.html index 76926c77..f712fe78 100755 --- a/doc/html/utf/user-guide/test-organization/unary-test-case.html +++ b/doc/html/utf/user-guide/test-organization/unary-test-case.html @@ -115,7 +115,7 @@ init_unit_test_suite( int argc, char* argv[] ) - +
    Source code | Show outputShow output 
    > example
 Running 5 test cases...
@@ -172,7 +172,7 @@ bool init_unit_test()
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 5 test cases...
@@ -187,7 +187,7 @@ test.cpp(14): error in "tm": difference between d * 100{100.01} and (double)(int
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-output.html b/doc/html/utf/user-guide/test-output.html index c904845f..74a7319f 100755 --- a/doc/html/utf/user-guide/test-output.html +++ b/doc/html/utf/user-guide/test-output.html @@ -80,7 +80,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-output/BOOST_TEST_CHECKPOINT.html b/doc/html/utf/user-guide/test-output/BOOST_TEST_CHECKPOINT.html index d0f1da89..b72f7341 100755 --- a/doc/html/utf/user-guide/test-output/BOOST_TEST_CHECKPOINT.html +++ b/doc/html/utf/user-guide/test-output/BOOST_TEST_CHECKPOINT.html @@ -73,7 +73,7 @@ void foo( int i ) - +
    Source code | Show outputShow output 
    > example
 Running 1 test case...
@@ -88,7 +88,7 @@ test.cpp(13): last checkpoint: Calling foo with i=1
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-output/BOOST_TEST_MESSAGE.html b/doc/html/utf/user-guide/test-output/BOOST_TEST_MESSAGE.html index 0ce94dd0..f5d4b55c 100755 --- a/doc/html/utf/user-guide/test-output/BOOST_TEST_MESSAGE.html +++ b/doc/html/utf/user-guide/test-output/BOOST_TEST_MESSAGE.html @@ -85,7 +85,7 @@ BOOST_AUTO_TEST_CASE( test_update ) - +
    Source code | Show outputShow output 
    > example --log_level=message
 Running 2 test cases...
@@ -102,7 +102,7 @@ Update Volume with 100
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-output/BOOST_TEST_PASSPOINT.html b/doc/html/utf/user-guide/test-output/BOOST_TEST_PASSPOINT.html index 9993cb84..0147c51b 100755 --- a/doc/html/utf/user-guide/test-output/BOOST_TEST_PASSPOINT.html +++ b/doc/html/utf/user-guide/test-output/BOOST_TEST_PASSPOINT.html @@ -68,7 +68,7 @@ BOOST_AUTO_TEST_CASE( test_case ) - +
    Source code | Show outputShow output 
    > example
 Running 1 test case...
@@ -83,7 +83,7 @@ test.cpp(16): last checkpoint
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-output/FPT.html b/doc/html/utf/user-guide/test-output/FPT.html index 6e44cca3..8ca6560c 100644 --- a/doc/html/utf/user-guide/test-output/FPT.html +++ b/doc/html/utf/user-guide/test-output/FPT.html @@ -69,7 +69,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-output/log-ct-config.html b/doc/html/utf/user-guide/test-output/log-ct-config.html index 95f26b4a..4cb72f74 100755 --- a/doc/html/utf/user-guide/test-output/log-ct-config.html +++ b/doc/html/utf/user-guide/test-output/log-ct-config.html @@ -80,7 +80,7 @@ BOOST_AUTO_TEST_CASE( test_case ) - +
    Source code | Show outputShow output 
    > example
 
@@ -128,7 +128,7 @@ BOOST_AUTO_TEST_CASE( test_case0 )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -180,7 +180,7 @@ BOOST_AUTO_TEST_CASE( test_case0 )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example --report_level=no
 <TestLog><Error file="test.cpp" line="18">check false failed</Error></TestLog>
@@ -194,7 +194,7 @@ BOOST_AUTO_TEST_CASE( test_case0 )
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-output/log-hr-format.html b/doc/html/utf/user-guide/test-output/log-hr-format.html index aa0fd07f..7ea4d915 100755 --- a/doc/html/utf/user-guide/test-output/log-hr-format.html +++ b/doc/html/utf/user-guide/test-output/log-hr-format.html @@ -322,7 +322,7 @@ Boost   : $BOOST_VERSION

    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-output/log-xml-format.html b/doc/html/utf/user-guide/test-output/log-xml-format.html index b21eeade..5dc65aad 100755 --- a/doc/html/utf/user-guide/test-output/log-xml-format.html +++ b/doc/html/utf/user-guide/test-output/log-xml-format.html @@ -38,7 +38,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-output/results-report.html b/doc/html/utf/user-guide/test-output/results-report.html index fd039cfa..012b2de6 100755 --- a/doc/html/utf/user-guide/test-output/results-report.html +++ b/doc/html/utf/user-guide/test-output/results-report.html @@ -46,7 +46,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-output/test-log.html b/doc/html/utf/user-guide/test-output/test-log.html index 78ff92ba..52be0604 100755 --- a/doc/html/utf/user-guide/test-output/test-log.html +++ b/doc/html/utf/user-guide/test-output/test-log.html @@ -181,7 +181,7 @@ BOOST_AUTO_TEST_CASE( test_list ) - +
    Source code | Show outputShow output 
    Running 1 test case...
 test.cpp(16): error in "test_list": check p1 == p2 failed [ != ]
@@ -205,7 +205,7 @@ test.cpp(16): error in "test_list": check p1 == p2 failed [ != ]
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-output/test-progress.html b/doc/html/utf/user-guide/test-output/test-progress.html index e4d174df..5593b04d 100755 --- a/doc/html/utf/user-guide/test-output/test-progress.html +++ b/doc/html/utf/user-guide/test-output/test-progress.html @@ -32,7 +32,7 @@

    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 UTF support simple text progress display, implemented based - on boost::progress_display[9]. The progress display output + on boost::progress_display[9]. The progress display output is enabled using the UTF parameter show_progress.

    @@ -77,7 +77,7 @@ init_unit_test_suite( int argc, char* argv[] ) - +
    Source code | Show outputShow output 

    > example --show_progress=yes --log_level=nothing
 
@@ -91,12 +91,12 @@ init_unit_test_suite( int argc, char* argv[] )


    -
    [9] UTF
    +
    [9] UTF
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/test-runners.html b/doc/html/utf/user-guide/test-runners.html index 003dbad6..02ed8147 100755 --- a/doc/html/utf/user-guide/test-runners.html +++ b/doc/html/utf/user-guide/test-runners.html @@ -36,7 +36,7 @@ 

    int unit_test_main( init_unit_test_func init_func, int argc, char* argv[] );

    - To invoke the test runner you are required to supply the pointer to the test module + To invoke the test runner you are required to supply the pointer to the test module initialization function as the first argument to the test runner function. In majority of the cases this function is invoked directly from test executable entry point - function main(). In most usage variants the UTF can automatically generate default function main() implementation as either part of the library or test module itself. @@ -160,7 +160,7 @@

    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/testing-tools.html b/doc/html/utf/user-guide/testing-tools.html index 53848cf9..b40322d3 100644 --- a/doc/html/utf/user-guide/testing-tools.html +++ b/doc/html/utf/user-guide/testing-tools.html @@ -50,8 +50,8 @@ All the tools are supplied in three flavors(levels): WARN, CHECK and REQUIRE. For example: BOOST_WARN_EQUAL, BOOST_CHECK_EQUAL, BOOST_REQUIRE_EQUAL. If an assertion designated by - the tool passes, confirmation message can be printed in log output[4]. If an assertion designated by the tool failed, depending on the level following - will happened[5]: + the tool passes, confirmation message can be printed in log output[4]. If an assertion designated by the tool failed, depending on the level following + will happened[5]:

    Table 2. Testing tools levels differences

    @@ -107,16 +107,16 @@

    -

    [4] to manage what messages appear +

    [4] to manage what messages appear in the test log stream set the proper log level

    -

    [5] in some cases log message can be slightly different to reflect failed tool +

    [5] in some cases log message can be slightly different to reflect failed tool specifics

    - - + +

    Last revised: , at

    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/testing-tools/custom-predicate.html b/doc/html/utf/user-guide/testing-tools/custom-predicate.html index 550743d2..ba940713 100644 --- a/doc/html/utf/user-guide/testing-tools/custom-predicate.html +++ b/doc/html/utf/user-guide/testing-tools/custom-predicate.html @@ -64,7 +64,7 @@ BOOST_AUTO_TEST_CASE( test_is_even ) - +
    Source code | Show outputShow output 
    > example
 Running 1 test case...
@@ -127,7 +127,7 @@ BOOST_AUTO_TEST_CASE( test_list_comparizon )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    Running 1 test case...
 test.cpp(28): error in "test_list_comparizon": check compare_lists( l1, l2 ) failed. Different sizes [2!=0]
@@ -140,7 +140,7 @@ test.cpp(28): error in "test_list_comparizon": check compare_lists( l1, l2 ) fai
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/testing-tools/floating_point_comparison.html b/doc/html/utf/user-guide/testing-tools/floating_point_comparison.html index 1a137cc6..67adb721 100644 --- a/doc/html/utf/user-guide/testing-tools/floating_point_comparison.html +++ b/doc/html/utf/user-guide/testing-tools/floating_point_comparison.html @@ -129,8 +129,8 @@

    Checks based on equations (4) and (5) are implemented by two predicates with - alternative interfaces: binary predicate close_at_tolerance[6] and predicate with four arguments - check_is_close[7]. + alternative interfaces: binary predicate close_at_tolerance[6] and predicate with four arguments + check_is_close[7].

    While equations (4) and @@ -138,7 +138,7 @@ 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 UTF implements an algorithm based on equation (1) in - binary predicate check_is_small[8]. + binary predicate check_is_small[8].

    On top of the generic, flexible predicates the UTF implements macro based family of tools @@ -238,16 +238,16 @@


    -

    [6] check type +

    [6] check type and tolerance value are fixed at predicate construction time

    -

    [7] check type and tolerance value are the arguments of the +

    [7] check type and tolerance value are the arguments of the predicate

    -

    [8] v is zero

    +

    [8] v is zero

    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/testing-tools/output-test.html b/doc/html/utf/user-guide/testing-tools/output-test.html index 4da19809..f2914ec5 100644 --- a/doc/html/utf/user-guide/testing-tools/output-test.html +++ b/doc/html/utf/user-guide/testing-tools/output-test.html @@ -99,7 +99,7 @@ BOOST_AUTO_TEST_CASE( test ) - +
    Source code | Show outputShow output 
    > example
 Running 1 test case...
@@ -145,7 +145,7 @@ BOOST_AUTO_TEST_CASE( test )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -161,7 +161,7 @@ test.cpp(16): error in "test": check output.match_pattern() failed. Mismatch at
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/testing-tools/reference.html b/doc/html/utf/user-guide/testing-tools/reference.html index 559cf229..017ec28b 100644 --- a/doc/html/utf/user-guide/testing-tools/reference.html +++ b/doc/html/utf/user-guide/testing-tools/reference.html @@ -30,29 +30,29 @@
    The UTF testing tools reference
    @@ -87,7 +87,7 @@ BOOST_AUTO_TEST_CASE( test ) - +
    Source code | Show outputShow output 
    > example --log_level=warning
 Running 1 test case...
@@ -100,7 +100,7 @@ test.cpp(11): fatal error in "test": critical check i > 5 failed

    See also: - BOOST_<level>_MESSAGE + BOOST_<level>_MESSAGE 
    @@ -133,7 +133,7 @@ BOOST_AUTO_TEST_CASE( test )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...                                                          
@@ -146,7 +146,7 @@ Operands bit sizes mismatch: 8 != 32

    See also: - BOOST_<level>_EQUAL + BOOST_<level>_EQUAL 
    @@ -156,7 +156,7 @@ Operands bit sizes mismatch: 8 != 32
 
    
      These tools are used to check on closeness using strong relationship defined by the predicate 
      check_is_close( left, right, tolerance ). To check for the weak relationship use 
-     BOOST_<level>_PREDICATE family of tools with explicit check_is_close
+     BOOST_<level>_PREDICATE family of tools with explicit check_is_close
      invocation.
     
    
 
    
@@ -208,7 +208,7 @@ BOOST_AUTO_TEST_CASE( test )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -243,7 +243,7 @@ BOOST_AUTO_TEST_CASE( test )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -253,7 +253,7 @@ Running 1 test case...

    See also: - BOOST_<level>_CLOSE_FRACTION, BOOST_<level>_SMALL, BOOST_<level>_EQUAL, + BOOST_<level>_CLOSE_FRACTION, BOOST_<level>_SMALL, BOOST_<level>_EQUAL, Floating point comparison algorithms
    @@ -264,7 +264,7 @@ Running 1 test case...

    These tools are used to check on closeness using strong relationship defined by the predicate check_is_close( left, right, tolerance ). To check for the weak relationship use - BOOST_<level>_PREDICATE family of tools with explicit check_is_close + BOOST_<level>_PREDICATE family of tools with explicit check_is_close invocation.

    @@ -314,7 +314,7 @@ BOOST_AUTO_TEST_CASE( test ) - +
    Source code | Show outputShow output 

    > example
 Running 1 test case...
@@ -325,7 +325,7 @@ test.cpp(12): error in "test": difference between v1{1.111e-010} and v2{1.112e-0

    See also: - BOOST_<level>_CLOSE, BOOST_<level>_SMALL, BOOST_<level>_EQUAL, + BOOST_<level>_CLOSE, BOOST_<level>_SMALL, BOOST_<level>_EQUAL, Floating point comparison algorithms
    @@ -334,7 +334,7 @@ test.cpp(12): error in "test": difference between v1{1.111e-010} and v2{1.112e-0 BOOST_CHECK_EQUAL(left, right) BOOST_REQUIRE_EQUAL(left, right)

    - 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.

    @@ -343,8 +343,8 @@ test.cpp(12): error in "test": difference between v1{1.111e-010} and v2{1.112e-0
    Note

    - 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.

    @@ -367,7 +367,7 @@ BOOST_AUTO_TEST_CASE( test ) - +
    Source code | Show outputShow output 
    > example
 Running 1 test case...
@@ -378,7 +378,7 @@ test.cpp(10): fatal error in "test": critical check i == j failed [2 != 1]

    See also: - BOOST_<level>, BOOST_<level>_CLOSE, BOOST_<level>_NE + BOOST_<level>, BOOST_<level>_CLOSE, BOOST_<level>_NE 
    @@ -412,7 +412,7 @@ BOOST_AUTO_TEST_CASE( test )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -425,7 +425,7 @@ Mismatch in a position 5: 6 != 7

    See also: - BOOST_<level>_EQUAL + BOOST_<level>_EQUAL 
    @@ -436,7 +436,7 @@ Mismatch in a position 5: 6 != 7
      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.
     
    
@@ -466,7 +466,7 @@ BOOST_AUTO_TEST_CASE( test )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -477,7 +477,7 @@ test.cpp(16): error in "test": incorrect exception my_exception is caught

    See also: - BOOST_<level>_THROW + BOOST_<level>_THROW 
    @@ -485,7 +485,7 @@ test.cpp(16): error in "test": incorrect exception my_exception is caught
 BOOST_CHECK_GE(left, right)
 BOOST_REQUIRE_GE(left, right)

    - 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.

    @@ -508,7 +508,7 @@ BOOST_AUTO_TEST_CASE( test ) - +
    Source code | Show outputShow output 
    >example
 Running 1 test case...
@@ -519,7 +519,7 @@ test.cpp(10): error in "test": check i >= j failed [1 < 4]

    See also: - BOOST_<level>_LE, BOOST_<level>_LT, BOOST_<level>_GT + BOOST_<level>_LE, BOOST_<level>_LT, BOOST_<level>_GT 
    @@ -527,7 +527,7 @@ test.cpp(10): error in "test": check i >= j failed [1 < 4]
 BOOST_CHECK_GT(left, right)
 BOOST_REQUIRE_GT(left, right)

    - 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.

    @@ -550,7 +550,7 @@ BOOST_AUTO_TEST_CASE( test ) - +
    Source code | Show outputShow output 
    >example
 Running 1 test case...
@@ -561,7 +561,7 @@ test.cpp(10): error in "test": check i > j failed [2 < 14]

    See also: - BOOST_<level>_LE, BOOST_<level>_LT, BOOST_<level>_GE + BOOST_<level>_LE, BOOST_<level>_LT, BOOST_<level>_GE 
    @@ -569,7 +569,7 @@ test.cpp(10): error in "test": check i > j failed [2 < 14]
 BOOST_CHECK_LE(left, right)
 BOOST_REQUIRE_LE(left, right)

    - 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.

    @@ -592,7 +592,7 @@ BOOST_AUTO_TEST_CASE( test ) - +
    Source code | Show outputShow output 
    >example
 Running 1 test case...
@@ -603,7 +603,7 @@ test.cpp(10): error in "test": check i <= j failed [9 > 6]

    See also: - BOOST_<level>_LT, BOOST_<level>_GE, BOOST_<level>_GT + BOOST_<level>_LT, BOOST_<level>_GE, BOOST_<level>_GT 
    @@ -611,7 +611,7 @@ test.cpp(10): error in "test": check i <= j failed [9 > 6]
 BOOST_CHECK_LT(left, right)
 BOOST_REQUIRE_LT(left, right)

    - 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.

    @@ -634,7 +634,7 @@ BOOST_AUTO_TEST_CASE( test ) - +
    Source code | Show outputShow output 
    >example
 Running 1 test case...
@@ -645,7 +645,7 @@ test.cpp(10): error in "test": check i < j failed [7 >= 7]

    See also: - BOOST_<level>_LE, BOOST_<level>_GE, BOOST_<level>_GT + BOOST_<level>_LE, BOOST_<level>_GE, BOOST_<level>_GT 
    @@ -653,7 +653,7 @@ test.cpp(10): error in "test": check i < j failed [7 >= 7]
 BOOST_CHECK_MESSAGE(predicate, message)
 BOOST_REQUIRE_MESSAGE(predicate, message)

    - 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.

    @@ -683,7 +683,7 @@ BOOST_AUTO_TEST_CASE( test ) - +
    Source code | Show outputShow output 

    > example --log_level=warning
 Running 1 test case...
@@ -693,7 +693,7 @@ test.cpp(12): warning in "test": sin(45){0.850904} is > 0.71. Arg is not in r

    See also: - BOOST_<level> + BOOST_<level> 
    @@ -701,7 +701,7 @@ test.cpp(12): warning in "test": sin(45){0.850904} is > 0.71. Arg is not in r
 BOOST_CHECK_NE(left, right)
 BOOST_REQUIRE_NE(left, right)

    - 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.

    @@ -724,7 +724,7 @@ BOOST_AUTO_TEST_CASE( test ) - +
    Source code | Show outputShow output 
    >example
 Running 1 test case...
@@ -735,7 +735,7 @@ test.cpp(10): error in "test": check i != j failed [3 == 3]

    See also: - BOOST_<level>_EQUAL + BOOST_<level>_EQUAL 
    @@ -775,7 +775,7 @@ BOOST_AUTO_TEST_CASE( test )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -785,7 +785,7 @@ test.cpp(10): error in "test": exception thrown by throw my_exception()

    See also: - BOOST_<level>_THROW + BOOST_<level>_THROW 
    @@ -795,7 +795,7 @@ test.cpp(10): error in "test": exception thrown by throw my_exception()
 
    
      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 BOOST_TEST_MAX_PREDICATE_ARITY). 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.
     
    
 
    
@@ -830,7 +830,7 @@ BOOST_AUTO_TEST_CASE( test )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -841,7 +841,7 @@ test.cpp(15): warning in "test": condition moo( 12, i, j ) is not satisfied for

    See also: - BOOST_<level> + BOOST_<level> 
    @@ -851,7 +851,7 @@ test.cpp(15): warning in "test": condition moo( 12, i, j ) is not satisfied for
 
    
      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. 
     
    
 
    
      The first parameter is the value to check. The second parameter is the tolerance.
@@ -886,7 +886,7 @@ BOOST_AUTO_TEST_CASE( test )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -897,7 +897,7 @@ test.cpp(11): error in "test": absolute value of v{-0.00123456} exceeds 1e-006

    See also: - BOOST_<level>_CLOSE, BOOST_<level>_CLOSE_FRACTION, + BOOST_<level>_CLOSE, BOOST_<level>_CLOSE_FRACTION, Floating point comparison algorithms
    @@ -939,7 +939,7 @@ BOOST_AUTO_TEST_CASE( test ) - +
    Source code | Show outputShow output 
    > example
 Running 1 test case...
@@ -949,7 +949,7 @@ test.cpp(11): error in "test": exception my_exception is expected

    See also: - BOOST_<level>NO_THROW + BOOST_<level>NO_THROW 
    @@ -979,7 +979,7 @@ BOOST_AUTO_TEST_CASE( test )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -989,7 +989,7 @@ test.cpp(8): error in "test": Nothing to test

    See also: - BOOST_<level> + BOOST_<level> 
    @@ -1019,7 +1019,7 @@ BOOST_AUTO_TEST_CASE( test )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -1029,7 +1029,7 @@ test.cpp(8): fatal error in "test": Test is not ready yet

    See also: - BOOST_<level> + BOOST_<level> 
    @@ -1037,7 +1037,7 @@ test.cpp(8): fatal error in "test": Test is not ready yet
 
    
      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.
     
    
 
    
@@ -1062,7 +1062,7 @@ BOOST_AUTO_TEST_CASE( test )
 
-
+
    
 Source code
  | Show outputShow output
 
    
 
    > example
 Running 1 test case...
@@ -1073,14 +1073,14 @@ test.cpp(9): error in "test": check ::boost::test_tools::tt_detail::is_defined_i

    See also: - BOOST_<level> + BOOST_<level>
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/usage-variants.html b/doc/html/utf/user-guide/usage-variants.html index 7530e009..4781eef1 100755 --- a/doc/html/utf/user-guide/usage-variants.html +++ b/doc/html/utf/user-guide/usage-variants.html @@ -51,7 +51,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/usage-variants/dynamic-lib-variant.html b/doc/html/utf/user-guide/usage-variants/dynamic-lib-variant.html index 353b8ff1..34191e55 100755 --- a/doc/html/utf/user-guide/usage-variants/dynamic-lib-variant.html +++ b/doc/html/utf/user-guide/usage-variants/dynamic-lib-variant.html @@ -40,7 +40,7 @@ inclusion.

    - The test runner supplied with this variant requires you to implement the test + The test runner supplied with this variant requires you to implement the test module initialization function that matches the alternative initialization function signature. The UTF provides an ability to automatically generate an empty test module initialization function with correct signature if no custom initialization is required by a @@ -59,7 +59,7 @@

    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/usage-variants/extern-test-runner-variant.html b/doc/html/utf/user-guide/usage-variants/extern-test-runner-variant.html index aba2c0aa..02bbdf63 100755 --- a/doc/html/utf/user-guide/usage-variants/extern-test-runner-variant.html +++ b/doc/html/utf/user-guide/usage-variants/extern-test-runner-variant.html @@ -40,7 +40,7 @@

    If an external test runner is based on the test runner built in to the dynamic library (like the standalone - boost_test_runner utility supplied by the UTF), it requires you to implement the + boost_test_runner utility supplied by the UTF), it requires you to implement the test module initialization function that matches the alternative initialization function signature. The UTF provides an ability to automatically generate an empty test module initialization function with correct signature if no custom initialization is required @@ -59,7 +59,7 @@

    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/usage-variants/extern-test-runner.html b/doc/html/utf/user-guide/usage-variants/extern-test-runner.html index b33231ce..6580f993 100755 --- a/doc/html/utf/user-guide/usage-variants/extern-test-runner.html +++ b/doc/html/utf/user-guide/usage-variants/extern-test-runner.html @@ -7,7 +7,7 @@ - + @@ -43,7 +43,7 @@
    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/usage-variants/single-header-variant.html b/doc/html/utf/user-guide/usage-variants/single-header-variant.html index fc3c08ef..7ec1b203 100755 --- a/doc/html/utf/user-guide/usage-variants/single-header-variant.html +++ b/doc/html/utf/user-guide/usage-variants/single-header-variant.html @@ -45,7 +45,7 @@ boost/test/unit_test.hpp.

    - The test runner supplied with this variant requires you to implement the test + The test runner supplied with this variant requires you to implement the test module initialization function that matches one of the two specifications depending on the compilation flag BOOST_TEST_ALTERNATIVE_INIT_API. If flag isn't defined you are required to match the original specification. If you define the flag @@ -57,7 +57,7 @@

    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental
    diff --git a/doc/html/utf/user-guide/usage-variants/static-lib-variant.html b/doc/html/utf/user-guide/usage-variants/static-lib-variant.html index 66a59be6..3c508661 100755 --- a/doc/html/utf/user-guide/usage-variants/static-lib-variant.html +++ b/doc/html/utf/user-guide/usage-variants/static-lib-variant.html @@ -36,7 +36,7 @@ variant of the UTF.

    - The test runner supplied with this variant required you to implement the test + The test runner supplied with this variant required you to implement the test module initialization function that matches one of the two specifications depending on the compilation flag BOOST_TEST_ALTERNATIVE_INIT_API. If flag isn't defined you are required to match the original specification. If you define the flag BOOST_TEST_ALTERNATIVE_INIT_API during a test module compilation you are required to use the alternative @@ -58,7 +58,7 @@

    - +
    Copyright © 2001-2011 Gennadiy Rozental
    Copyright © 2001-2012 Gennadiy Rozental