|
|
Boost-Commit : |
From: gennadiy.rozental_at_[hidden]
Date: 2008-07-24 21:53:12
Author: rogeeff
Date: 2008-07-24 21:53:12 EDT (Thu, 24 Jul 2008)
New Revision: 47770
URL: http://svn.boost.org/trac/boost/changeset/47770
Log:
removed old docs
Removed:
trunk/libs/test/doc/acknowledgements.html
trunk/libs/test/doc/btl1.gif
trunk/libs/test/doc/components/
trunk/libs/test/doc/examples/
trunk/libs/test/doc/faq.html
trunk/libs/test/doc/index.html
trunk/libs/test/doc/open_issues.html
trunk/libs/test/doc/portability.html
trunk/libs/test/doc/release_notes.html
trunk/libs/test/doc/style/
trunk/libs/test/doc/tests/
trunk/libs/test/doc/tutorials/
trunk/libs/test/doc/usage/
Deleted: trunk/libs/test/doc/acknowledgements.html
==============================================================================
--- trunk/libs/test/doc/acknowledgements.html 2008-07-24 21:53:12 EDT (Thu, 24 Jul 2008)
+++ (empty file)
@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<HTML>
-<HEAD>
-<TITLE>Boost Test Library: acknowledgements</TITLE>
-<LINK rel="stylesheet" type="text/css" href="style/btl.css" media="screen">
-<LINK rel="stylesheet" type="text/css" href="style/btl-print.css" media="print">
-<META http-equiv="Content-Language" content="en-us">
-<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</HEAD>
-<BODY>
-<DIV class="header"> Boost.Test > <SPAN class="current_article">Acknowledgements</SPAN> </DIV>
-<DIV class="body"> <IMG src='btl1.gif' width="252" height="43" alt="Boost Test logo">
- <H1 class="subtitle"><A name="Acknowledgements">Acknowledgements</A></H1>
- <P>Original Test Library:</P>
- <P class="first-line-indented">Ed Brey, Kevlin Henney, Ullrich Koethe, and Thomas
- Matelich provided very helpful comments during development. Dave Abrahams, Ed
- Brey, William Kempf, Jens Maurer, and Wilka suggested numerous improvements during
- the Formal Review. Jens Maurer was the review manager. Beman Dawes is the developer
- and maintainer.</P>
- <P>Second Release:</P>
- <P class="first-line-indented">Beman Dawes and Ullrich Koethe started the library.
- Fernando Cacciola, Jeremy Siek, Beman Dawes, Ullrich Koethe, Dave Abrahams suggested
- numerous improvements during the Formal Review. Jeremy Siek was the review manager.
- Dave Abrahams edited this documentation. Beman Dawes was a great help in both final
- testing and merging library with rest of the boost. Gennadiy Rozental is the developer
- and maintainer. </P>
-</DIV>
-<DIV class="footer">
-<DIV class="footer-body">
- <P> © <A name="Copyright">Copyright</A> <A href="mailto:boost-test%20at%20emailaccount%20dot%20com%20%28please%20unobscure%29">Gennadiy Rozental</A> 2001-2006. <BR>
- Distributed under the Boost Software License, Version 1.0.
- (See accompanying file LICENSE_1_0.txt or copy at
- www.boost.org/LICENSE_1_0.txt)</P>
- <P>Revised: <!-- #BeginDate format:Sw1 -->18 February, 2006<!-- #EndDate --> </P>
-</DIV>
-</DIV>
-</BODY>
-</HTML>
Deleted: trunk/libs/test/doc/btl1.gif
==============================================================================
Binary file. No diff available.
Deleted: trunk/libs/test/doc/faq.html
==============================================================================
--- trunk/libs/test/doc/faq.html 2008-07-24 21:53:12 EDT (Thu, 24 Jul 2008)
+++ (empty file)
@@ -1,90 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<HTML>
-<HEAD>
-<TITLE>Boost Test Library: FAQ</TITLE>
-<LINK rel="stylesheet" type="text/css" href="style/btl.css" media="screen">
-<LINK rel="stylesheet" type="text/css" href="style/btl-print.css" media="print">
-<META http-equiv="Content-Language" content="en-us">
-<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</HEAD>
-<BODY>
-<DIV class="header"> Boost.Test > <SPAN class="current_article">FAQ</SPAN> </DIV>
-<DIV class="body"> <IMG src='btl1.gif' width="252" height="43" alt="Boost Test logo">
- <H1 class="subtitle">Frequently Asked Questions</H1>
- <UL>
- <LI><A href="#Item_1">Where the latest version of the Boost Test Library
- is located?</A></LI>
- <LI>I found a bug. Where could I report it?</LI>
- <LI><A href="#Item_3">I have a request for a new feature. Where could I ask
- for it? </A></LI>
- <LI>How to create test case?</LI>
- <LI>How to create test suite?</LI>
- <LI><A href="#Item_7">Why did I get a linker error when compiling my test
- program?</A></LI>
- <LI>How could I redirect testing output?</LI>
- <LI>I want different default log trace level</LI>
- <LI><A href="#Item_9">Is there dll version of Boost.Test components available
- on Win32 platform?</A></LI>
- </UL>
- <H2><A name="Item_1">Where the latest version of the Boost Test Library is
- located?</A></H2>
- <P class="first-line-indented">The latest version of Boost Test Library is
- available online on www.boost.org.</P>
- <H2><A name="Item_2">I found a bug. Where could I report it?</A></H2>
- <P class="first-line-indented">Send a bug report to <A href="mailto:boost-test%20at%20emailaccount%20dot%20com%20%28please%20unobscure%29">Gennadiy
- Rozental</A>.</P>
- <H2><A name="Item_3">I have a request for a new feature. Where could I ask
- for it?</A></H2>
- <P class="first-line-indented">You can send a request to <A href="mailto:boost-test%20at%20emailaccount%20dot%20com%20%28please%20unobscure%29">Gennadiy
- Rozental</A>.</P>
- <H2><A name="Item_4">How to create test case?</A></H2>
- <P class="first-line-indented">To create a test case use the macro BOOST_AUTO_TEST_CASE(
- test_function ). For more details see the <A href="components/utf/components/test_case/index.html">Unit
- Test Framework</A> documentation.</P>
- <H2><A name="Item_5">How to create test suite?</A></H2>
- <P class="first-line-indented">To create a test suite use the macro BOOST_AUTO_TEST_SUITE(
- suite_name ). For more details see the <A href="components/utf/components/test_suite/index.html">Unit
- Test Framework</A> documentation.</P>
- <H2><A name="Item_6">Why did I get a linker error when compiling my test program?</A></H2>
- <P class="first-line-indented">Boost Test Library is intended to be used off-line.
- To create a test program you should link with the one of the precompiled
- library components or use "included" version of the component located
- in a boost/test/included directory. For example, to use Unit Test Framework
- you may either include the <boost/test/unit_test.hpp> and link with
- libunit_test_framework.lib or you could include <boost/test/included/unit_test.hpp> in
- which case you would not need to link with any precompiled component. Note
- also that you should strictly follow specification on integration function
- in other case some compilers may produce linker error like this:</P>
- <P>Unresolved external init_unit_test_suite(int, char**).</P>
-
- <P>The reasons for this error is that in your implementation you should specify
- second argument of init_unit_test_suite exactly as in a specification, i.e.:
- char* [].</P>
- <H2><A name="Item_7">How could I redirect testing output?</A></H2>
- <P class="first-line-indented">Use unit_test_log::instance().set_log_output(
- std::ostream& ). For more details see the <A href="components/utf/components/test_log/index.html">Unit
- Test Framework </A>documentation.</P>
- <H2><A name="Item_8">I want different default log trace level</A></H2>
- <P class="first-line-indented">Use environment variable BOOST_TEST_LOG_LEVEL
- to define desired log trace level. You still will be able to reset this value
- from the command line. For the list of acceptable values see the <A href="components/utf/parameters/log_level.html">Unit
- Test Framework</A> documentation. </P>
- <H2><A name="Item_9">Is there DLL version of Boost.Test components available
- on Win32 platform?</A></H2>
- <P class="first-line-indented">No. At the moment Boost Test components could
- not be compiled into dlls to be loaded at runtime.</P>
-</DIV>
-<DIV class="footer">
- <DIV class="footer-body">
- <P> © <A name="Copyright">Copyright</A> <A href="mailto:boost-test%20at%20emailaccount%20dot%20com%20%28please%20unobscure%29">Gennadiy
- Rozental</A> 2001-2006. <BR>
- Distributed under the Boost Software License, Version 1.0.
- (See accompanying file LICENSE_1_0.txt or
- copy at www.boost.org/LICENSE_1_0.txt)</P>
- <P>Revised:
- <!-- #BeginDate format:Sw1 -->8 March, 2006<!-- #EndDate -->
- </P>
- </DIV>
-</DIV>
-</BODY>
-</HTML>
Deleted: trunk/libs/test/doc/index.html
==============================================================================
--- trunk/libs/test/doc/index.html 2008-07-24 21:53:12 EDT (Thu, 24 Jul 2008)
+++ (empty file)
@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<HTML>
-<HEAD>
-<TITLE>Boost Test Library</TITLE>
-<LINK rel="stylesheet" type="text/css" href="style/btl.css" media="screen">
-<LINK rel="stylesheet" type="text/css" href="style/btl-print.css" media="print">
-<META http-equiv="Content-Language" content="en-us">
-<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</HEAD>
-<BODY>
-<DIV class="body"> <IMG src="../../../boost.png" alt="Boost logo"
- height="86" width="277">
- <H1>Boost Test Library</H1>
- <P class="epigraph">"Test everything that could possibly break"</P>
- <P class="epigraph">XP maxim</P>
- <P class="page-toc"> Introduction<BR>
- Components </P>
- <P class="page-toc-indented">
- Unit Test Framework<BR>
- Minimal testing facility<BR>
- Program Execution Monitor<BR>
- Execution Monitor
- </P>
- <P class="page-toc">
- Tutorials and usage recommendations<BR>
- FAQ<BR>
- Release notes<BR>
- Open Issues<BR>
- Examples<BR>
- Tests<BR>
- Portability<BR>
- Acknowledgements</P>
- <H2><A name="Introduction">Introduction</A></H2>
- <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 <A href="./components/prg_exec_monitor/index.html"> Program
- Execution Monitor</A> is also useful in some production (non-test) environments. </P>
- <H2><A name="ReleaseNotes">Release notes</A></H2>
- <P class="first-line-indented"><EM>In this release most of
- Boost.Test components undergo a major or significant change in both design
- and implementation</EM>. I've strived to keep an interface unchanged as much as possible. The primary goals for this update were: </P>
- <UL>
- <LI>Make a Unit Test Framework better suited for different 'runners'</LI>
- <LI>Make Unit Test Framework simpler internally by eliminating test cases hierarchy</LI>
- <LI>Make test tools more uniform</LI>
- <LI>Make auto Unit Test Framework as usable as possible</LI>
- </UL>
- <P>For more details see complete <A href="release_notes.html#v1_33_0">release
- notes</A>. I may not be able to make all necessary changes in documentation within bounds of this release. In case of any discrepancies either consult library code or ask for support in users list. </P>
-</DIV>
-<DIV class="footer">
- <DIV class="footer-body">
- <P> © <A name="Copyright">Copyright</A> <A href="mailto:boost-test%20at%20emailaccount%20dot%20com%20%28please%20unobscure%29">Gennadiy
- Rozental</A> 2001-2006. <BR>
- Distributed under the Boost Software License, Version 1.0.
- (See accompanying file LICENSE_1_0.txt or
- copy at www.boost.org/LICENSE_1_0.txt)</P>
- <P>Revised:
- <!-- #BeginDate format:Sw1 -->28 February, 2006<!-- #EndDate -->
- </P>
- </DIV>
-</DIV>
-</BODY>
-</HTML>
Deleted: trunk/libs/test/doc/open_issues.html
==============================================================================
--- trunk/libs/test/doc/open_issues.html 2008-07-24 21:53:12 EDT (Thu, 24 Jul 2008)
+++ (empty file)
@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<HTML>
-<HEAD>
-<TITLE>Boost Test Library: open issues</TITLE>
-<LINK rel="stylesheet" type="text/css" href="style/btl.css" media="screen">
-<LINK rel="stylesheet" type="text/css" href="style/btl-print.css" media="print">
-<META http-equiv="Content-Language" content="en-us">
-<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</HEAD>
-<BODY>
-<DIV class="header"> Boost.Test > <SPAN class="current_article">Open
- Issues</SPAN> </DIV>
-<DIV class="body"> <IMG src='btl1.gif' width="252" height="43" alt="Boost Test logo">
- <H1 class="subtitle">Open Issues</H1>
- <UL>
- <LI> Finish update for CLA support </LI>
- <LI> Selective test cases run by name</LI>
- <LI>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>Some performance testing tools (aka profiler). Unless somebody else will come up with something like this</LI>
- <LI> 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>Projects that could be very interesting, but I may not be able to do
- it by myself:
- <UL>
- <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>
- </UL>
- </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>
- </UL>
-</DIV>
-<DIV class="footer">
- <DIV class="footer-body">
- <P> © <A name="Copyright">Copyright</A> <A href="mailto:boost-test%20at%20emailaccount%20dot%20com%20%28please%20unobscure%29">Gennadiy
- Rozental</A> 2001-2006. <BR>
- Distributed under the Boost Software License, Version 1.0.
- (See accompanying file LICENSE_1_0.txt or
- copy at www.boost.org/LICENSE_1_0.txt)</P>
- <P>Revised:
- <!-- #BeginDate format:Sw1 -->28 February, 2006<!-- #EndDate -->
- </P>
- </DIV>
-</DIV>
-</BODY>
-</HTML>
Deleted: trunk/libs/test/doc/portability.html
==============================================================================
--- trunk/libs/test/doc/portability.html 2008-07-24 21:53:12 EDT (Thu, 24 Jul 2008)
+++ (empty file)
@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<HTML>
-<HEAD>
-<TITLE>Boost Test Library portability</TITLE>
-<LINK rel="stylesheet" type="text/css" href="style/btl.css" media="screen">
-<LINK rel="stylesheet" type="text/css" href="style/btl-print.css" media="print">
-<META http-equiv="Content-Language" content="en-us">
-<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</HEAD>
-<BODY>
-<DIV class="header"> Boost.Test > <SPAN class="current_article">Portability</SPAN> </DIV>
-<DIV class="body"> <IMG src='btl1.gif' width="252" height="43" alt="Boost Test logo">
- <H1 class="subtitle"><A name="Portability">Portability</A></H1>
- <P class="first-line-indented">Because the Boost Test Library is critical for
- porting and testing Boost libraries, it has been written to be extremely
- conservative in its use of C++ features, and to keep dependencies to a bare
- minimum.</P>
- <P class="first-line-indented">Boost.Test internal tests have been run (and
- work) under numerous compilers. Check the <A href="http://boost.sourceforge.net/regression-logs/">compiler
- status pages</A> and developer status pages to see how Boost.Test works on different compilers platforms. </P>
-</DIV>
-<DIV class="footer">
- <DIV class="footer-body">
- <P> © <A name="Copyright">Copyright</A> <A href="mailto:boost-test%20at%20emailaccount%20dot%20com%20%28please%20unobscure%29">Gennadiy
- Rozental</A> 2001-2006. <BR>
- Distributed under the Boost Software License, Version 1.0.
- (See accompanying file LICENSE_1_0.txt or
- copy at www.boost.org/LICENSE_1_0.txt)</P>
- <P>Revised:
- <!-- #BeginDate format:Sw1 -->18 January, 2004<!-- #EndDate -->
- </P>
- </DIV>
-</DIV>
-</BODY>
-</HTML>
Deleted: trunk/libs/test/doc/release_notes.html
==============================================================================
--- trunk/libs/test/doc/release_notes.html 2008-07-24 21:53:12 EDT (Thu, 24 Jul 2008)
+++ (empty file)
@@ -1,350 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<HTML>
-<HEAD>
-<TITLE>Boost Test Library: release rotes</TITLE>
-<LINK rel="stylesheet" type="text/css" href="style/btl.css" media="screen">
-<LINK rel="stylesheet" type="text/css" href="style/btl-print.css" media="print">
-<META http-equiv="Content-Language" content="en-us">
-<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</HEAD>
-<BODY>
-<DIV class="header"> Boost.Test > <SPAN class="current_article">Release
- Notes</SPAN> </DIV>
-<DIV class="body"> <IMG src='btl1.gif' width="252" height="43" alt="Boost Test logo">
- <H1 class="subtitle">Release Notes</H1>
- <P class="page-toc">Boost release 1.33.0</P>
- <P class="page-toc">Boost release 1.32.0</P>
- <P class="page-toc">Boost release 1.31.0 </P>
- <P class="page-toc">Boost release 1.30.0<BR>
- Migration guide from Boost Test v1 </P>
- <H2><A name="v1_33_0">Boost release 1.33.0</A></H2>
- <P class="first-line-indented"><EM>In this release Most
- of Boost.Test components undergo a major or significant change in both
- design and implementation</EM>.
- I've strived to keep an interface unchanged as much as
- possible. The primary goals for this update were: </P>
- <UL>
- <LI>Make a Unit Test Framework better suited for different 'runners'</LI>
- <LI>Make Unit Test Framework simpler internally by eliminating test cases
- hierarchy</LI>
- <LI>Make test tools more uniform</LI>
- <LI>Make auto Unit Test Framework as usable as possible</LI>
- </UL>
- <P class="first-line-indented">Following are details of what updated/changed specifically in each area of
- Boost.Test:</P>
- <OL type="I">
- <LI>
- <H3> Execution Monitor</H3>
- </LI>
- </OL>
- <P class="first-line-indented">The execution monitor design changes from inheritance to delegation. If
- previously one needed to inherit from the boost::execution monitor to do a
- monitored run of a function, now one need to employ an instance of the
- boost::execution_monitor</P>
-
- <P class="first-line-indented">In addition following features implemented:</P>
- <UL>
- <LI>Debugger presence detected, in which case catching system errors (SEH) is
- disabled unless explicitly enabled. For now only works for msvc family</LI>
- <LI> Automatic detection of memory leaks introduced. For now only works for
- msvc family.
- Unit Test Framework turns this feature on by default.</LI>
- </UL>
- <OL start="2">
- <LI type="I">
- <H3>Unit Test Framework (UTF)</H3>
- </LI>
- </OL>
- <P class="first-line-indented">This component of Boost.Test undergo a most dramatic changes in both
- design and implementation. </P>
- <UL>
- <LI> UTF doesn't employ test cases hierarchy anymore. There is single class
- test_case that model one testing unit and class test_suite that model a
- collection of test units. Previously UTF employed compound test cases (for
- example parameterized test case) which went through it's components (simple
- subtests) during testing run time. Now compound test present itself as test
- case generator which produce a collection if test_case instances during test
- tree construction time. One consequence of this is that user doesn't need to
- keep track of compound test case parameters is it used be. test_case now
- employs a polymorphic callback to a actual test function. As a result of
- this one could supply any zero arity function as an argument of
- BOOST_TEST_CASE. So no extra support needed to be able to create
- boost::function or boost::bind based tests cases. </LI>
- <LI>Introduced generic mechanism to traverse the test tree. Anyone willing
- to do so just need to implement test_tree_visitor interface and employ
- traverse_test_tree. This allows to implement any pre/post processing over
- test tree. </LI>
- <LI>Introduced a notion of framework. The framework is responsible for:
- <UL>
- <LI>initializing and providing access to master test suite</LI>
- <LI>providing access to current test case</LI>
- <LI> running testing from given test tree node (simple or compound). By default it runs from
- root - master test suite. Supports both sequential and random order.</LI>
- <LI>one may register any test observer agent (implements test_observer
- interface) and framework notifies it of all test events</LI>
- <LI>provides access to any test case based to unique test unit id</LI>
- <LI>Using the framework one could implement different test runners. UTF library
- supplies one console runner (unit_test_main.cpp). But it's possible to do
- one winmain based or anything else. For example GUI program that build test
- tree and then run tests by request from any point in test tree.</LI>
- </UL>
- </LI>
- <LI>Unit test log interface changed to single line (used to be begin/end
- macros). Unit test log formatter interface changed. How it much simpler and
- straightforward. Two supplied implementation are separated. </LI>
- <LI> Notion of unit test result that was responsible for result collection
- and reporting eliminated. Instead introduced independent notions:
- results_collector and results_reporter. Results reporting formatter
- interface made public. Also results_reporter now allows to change an output
- stream.</LI>
- <LI> Progress monitor functionality (which used to be activated in log
- level log_progress) now is an independent test observer and implemented by
- class progress_monitor.</LI>
- <LI> Test case template interface changed. Now user doesn't need to
- explicitly register meta class.</LI>
- <LI>In addition couple more features implemented:
- <UL>
- <LI>Added support for test case timing</LI>
- <LI>UTF made __cdecl - safe</LI>
- <LI> Result report include skipped tests</LI>
- <LI> io saver facilities employed to guard against undesirable modification
- in output streams formatting</LI>
- <LI> template test case automatically generate name that includes type name</LI>
- <LI> --detect_memory_leak and --random command line arguments added</LI>
- </UL>
- </LI>
- </UL>
- <OL start="3">
- <LI type="I">
- <H3> Test Tools</H3>
- </LI>
- </OL>
- <UL>
- <LI> Test Tools interfaces now provide 3 version for each tool:
- <UL>
- <LI>CHECK- reports an error if assertion failed</LI>
- <LI>WARN - reports a warning if assertion failed</LI>
- <LI>REQUIRE - reports an error if assertion failed and aborts test case execution</LI>
- </UL>
- </LI>
- <LI>Implementation completely reworked. All tools implemented now through single vararg function</LI>
- <LI>In addition following modifications made:
- <UL>
- <LI>CHECK_COLLECTION interface changed: it now expect 4 arguments</LI>
- <LI>BITWISE_EQUAL renamed to CHECK_BITWISE_EQUAL; old name still provided,
- but is deprecated</LI>
- <LI>CHECK_COLLECTION interface changed to use PP_SEQ and as a result
- support arbitrary(actually maximum is fixed but configurable) number of
- predicate arguments</LI>
- <LI>most of templates eliminated speeding up test modules compilation</LI>
- <LI> floating-point precision set to include all significant digits
- (actually the formula may require some rework since it obviously doesn't do
- a good job sometimes)</LI>
- <LI>BOOST_CHECK/WARN/REQUIRE_SMALL test tool added</LI>
- <LI>deprecated test tools names are removed </LI>
- </UL>
- </LI>
- </UL>
- <OL start="4" type="I">
- <LI type="I">
- <H3>Auto Unit Test Framework</H3>
- </LI>
- </OL>
- <UL>
- <LI>BOOST_AUTO_UNIT_TEST renamed to BOOST_AUTO_TEST_CASE. Old name still
- provided but deprecated</LI>
- <LI>BOOST_AUTO_TEST_CASE_TEMPLATE provides an ability to write a
- self-registering test case template</LI>
- <LI>BOOST_FIXTURE_TEST_CASE provides an ability to write a self-registering
- test case with fixture</LI>
- <LI>BOOST_AUTO_TEST_CASE_EXPECTED_FAILURES provides an ability to specify a
- number of expected failures in any self-registering test case</LI>
- <LI>BOOST_AUTO_TEST_SUITE and BOOST_AUTO_TEST_SUITE_END provide an ability
- to structure test cases into self-registering test suites</LI>
- </UL>
- <OL start="5" type="I">
- <LI>
- <H3> Included components</H3>
- </LI>
- </OL>
- <UL>
- <LI>Implementation moved from source files (.cpp) under lib/test/src into
- implementation files (.ipp) under boost/test/impl to eliminate dependency of
- included/minimal components on lib/test/src directory. </LI>
- </UL>
- <H2><A name="v1_32_0">Boost release 1.32.0</A></H2>
- <UL>
- <LI>Licence updated to use common Boost software licence</LI>
- <LI>basic_cstring introduced and used in most places instead of std::string
- and char const*</LI>
- <LI>namespace names shortened; old one still supported till next release</LI>
- <LI>numerous portability workaround for several new supported configurations</LI>
- <LI>class properties facilities reworked to be more powerful</LI>
- <LI>added proper encoding of XML PCDATA</LI>
- <LI>support for wide string comparison implemented</LI>
- </UL>
- <H2><A name="v1_31_0">Boost release 1.31.0</A></H2>
- <UL>
- <LI>Zero arity function template based test case </LI>
- <LI><A href="components/execution_monitor/execution_monitor.html#register_exception_translator">Custom
- exception translators support </A> in execution monitor and register_exception_translator added for Unit Test Framework </LI>
- <LI><A href="components/utf/components/test_case/abstract_interface.html">Test
- cases dependency support </A></LI>
- <LI><A href="components/utf/components/test_case/auto_register_facility.html">Added
- support for multi-module unit tests in automatic registration facility </A></LI>
- <LI>Floating point comparison algorithm reworked (Is not backward compatible!!!)
- <UL>
- <LI><STRONG>tolerance now expected in percent units</STRONG></LI>
- <LI>eliminated tolerance definition by number of rounding errors</LI>
- <LI>switch to comparison type enumeration instead of boolean value </LI>
- </UL>
- </LI>
- <LI>First failed assertion support</LI>
- <LI>Major
- documentation structure rework and update<BR>
- I hope you will find handy new navigation system </LI>
- <LI>Switched to new boost license</LI>
- <LI><A href="components/test_tools/custom_predicate_support.html">Added support
- for custom users predicate returning both boolean result code and possibly
- error message </A></LI>
- <LI>BOOST_CHECK_EXCEPTION test
- tool introduced - to perform complex validation of expected exception </LI>
- <LI>BOOST_IGNORE_CHECK test tool introduced - to be used with BOOST_CHECK_EXCEPTION </LI>
- <LI>Straiten return code logic for Unit Test Framework and in case
- of failed initialization in Unit Test Framework </LI>
- <LI>Added position in the collection comparison results error message </LI>
- <LI>Disable SEH if BOOST_DISABLE_WIN32 in effect</LI>
- <LI>Como can't do structured exceptions</LI>
- <LI>Added support for catch_system_error in Test Execution Monitor</LI>
- <LI><A href="components/utf/components/test_log/custom_log_formatter.html">Move
- log formatter in public interface</A></LI>
- <LI>Custom char value log print procedures</LI>
- <LI>Support for logging variable values of types that does not support operator<< </LI>
- <LI>match_pattern updated to show an error mismatch snippet</LI>
- <LI>force UNIX slash for file name </LI>
- <LI>Some annoying MSVC warnings suppressed </LI>
- <LI>test_case_scope_tracker introduced for correct exception unwinding handling </LI>
- <LI>unit_test_result_tracker introduced for correct exception handling </LI>
- <LI>several minor bug and warnings fixes </LI>
- </UL>
- <H2><A name="v1_30_0">Boost release 1.30.0</A></H2>
- <UL>
- <LI>Facility for automatic registration of unit tests is introduced<BR>
- It was requested during original Boost Test review and now it supports
- automatic registration for free function based test cases. Here an example:<BR>
- <PRE class="code">#<SPAN class="reserv-word">include</SPAN> <boost/test/auto_unit_test.hpp>
-
-BOOST_AUTO_UNIT_TEST( test1 )
-{
- BOOST_CHECK( true );
-}
-
-BOOST_AUTO_UNIT_TEST( test2 )
-{
- BOOST_CHECK( true );
-}</PRE>
- </LI>
- <LI>XML log format is introduced<BR>
- Now user willing to automate errors processing could get a log in XML format.
- Command line switch is introduced that manage log format:<BR>
- --log_format=[XML|HRF] will force XML or human readable format respectively</LI>
- <LI>XML report format is introduced<BR>
- Now user willing to automate results analysis could get a result report
- in XML format. Command line switch is introduced that manage report format:<BR>
- --report_format=[XML|HRF] will force XML or human readable format respectively</LI>
- <LI>BOOST_CHECK_NO_THROW test tool is introduced</LI>
- <LI>BOOST_BITWISE_EQUAL test tool is introduced</LI>
- <LI>libraries file names changed to:<BR>
- boost_prg_exec_monitor<BR>
- boost_test_exec_monitor<BR>
- boost_unit_test_framework</LI>
- <LI>Components examples and test documentation page is introduced<BR>
- Now all test/examples links lead to this page that has summary information
- about all of them, that include expected output, type of test and so
- on</LI>
- <LI>Catch system errors switch introduced<BR>
- This will work among the lines described in http://lists.boost.org/MailArchives/boost/msg40028.php<BR>
- Environment variable name: BOOST_TEST_CATCH_SYSTEM_ERRORS[="no"]<BR>
- Unit Test Framework command line argument: --catch_system_errors[="no"]</LI>
- <LI>Added building dynamic libraries into Jamfile</LI>
- <LI>MS C runtime debug hooks introduced<BR>
- It allows to catch _ASSERT bases assertion for MSVC</LI>
- <LI>SIGABRT catch added</LI>
- <LI>Eliminated NULLs all over the place<BR>
- I switched to use typedef c_string literal instead of char const* and to
- c_string literal() instead of NULL. Different definition of NULL symbol
- causing small problems for some compilers</LI>
- <LI>class wrapstrstream separated in standalone file and renamed to wrap_stringstream<BR>
- For now it will be located in test/detail. Once I prepare doc page for
- it I will present it for adding into utility</LI>
- <LI>unit_test_result_saver introduced to properly managed reset_current_test_set
- calls in case of exceptions</LI>
- <LI>switch back to use scoped_ptr instead of raw test_suite pointer in unit_test_main.cpp</LI>
- <LI>BOOST_CPP_MAIN_CONFIRMATION renamed to BOOST_PRG_MON_CONFIRM and changed
- it's logic a bit<BR>
- It now should have value "no" to turn off pass confirmation</LI>
- <LI>added tests for auto unit test facility and catching assert statements</LI>
- <LI>Jamfile added info examples directory</LI>
- <LI>Added example input for the unit_test_example5</LI>
- <LI>Command line option --output_format is introduced that both log/report
- format simultaneously</LI>
- <LI>Allows to perform bitwise comparisons of the two arguments provided.
- Will report as many errors as many bits mismatch. Mismatch position is
- reported.</LI>
- <LI>Documentation default palette changed to white</LI>
- <LI>Signal handling selection algorithm fixed<BR>
- BOOST_HAS_SIGACTION is used to select sigaction based signal handling alternative.
- It allowed use of signal handling with gcc on win32 platform.</LI>
- <LI>C strings usage in minimized as much as possible</LI>
- <LI>class_properties header modified to use Boost.Preprocessor for friends
- declaration</LI>
- <LI>other minor code/doc changes and bug fixes</LI>
- </UL>
- <H2><A name="Migration">Boost Test migration guide</A></H2>
- <P class="first-line-indented">This version of Boost.Test library substitute
- the original testing library used in a Boost. These are several simple steps
- you need to follow to smoothly migrate to the latest software.</P>
- <P class="first-line-indented">If your code were using the original version
- of cpp_main facility, to migrate you will need to delete the inclusion of
- the <boost/test/cpp_main.cpp>, since this file is not present any more.
- After that you have following choices:</P>
- <UL>
- <LI>Link with Unit Test Framework (exact library name depends on compiler
- you are using, but most probably it will be libboost_prg_exec_monitor.lib). </LI>
- <LI>Include <boost/test/included/prg_exec_monitor.hpp>, in which case
- you need not link with precompiled component but it may incur probably
- some compile time overhead.</LI>
- </UL>
- <P class="first-line-indented">If your code were using the original version
- of test_main and test tools facilitates of Boost.Test library, to migrate
- to use of latest one you have following choices:</P>
- <UL>
- <LI>Without changing of the code that were using Boost.Test facilities link
- with Test Execution Monitor (exact library name depends on compiler you
- are using, but most probably it will be libtest_exec_monitor.lib).</LI>
- <LI>Include <boost/test/included/test_exec_monitor.hpp>, in which case
- you need not link with precompiled component but it may incur probably
- some compile time overhead. Definition of BOOST_INCLUDE_MAIN could be deleted
- either.</LI>
- <LI>Include <boost/test/minimal.hpp>, in which case you need not link
- with precompiled component and it most probably does not incur a compile
- time overhead, but you will be limited to the set of features defined in
- the original test library. Definition of BOOST_INCLUDE_MAIN could be deleted
- either. Would you decide in a future to use any of newer Boost.Test features
- you will be enforced to snitch to one the two chaises above. </LI>
- </UL>
-</DIV>
-<DIV class="footer">
- <DIV class="footer-body">
- <P> © <A name="Copyright">Copyright</A> <A href="mailto:boost-test%20at%20emailaccount%20dot%20com%20%28please%20unobscure%29">Gennadiy
- Rozental</A> 2001-2006. <BR>
- Distributed under the Boost Software License, Version 1.0.
- (See accompanying file LICENSE_1_0.txt or
- copy at www.boost.org/LICENSE_1_0.txt)</P>
- <P>Revised:
- <!-- #BeginDate format:Sw1 -->8 March, 2006<!-- #EndDate -->
- </P>
- </DIV>
-</DIV>
-</BODY>
-</HTML>
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