Changes between Version 3 and Version 4 of Boost Test

Timestamp:

Mar 8, 2007, 2:55:07 PM (17 years ago)

Author:

anonymous

Comment:

--

Boost Test

@@ -1 +1 @@
 = Using Boost.Test =
 
-If you're developing with C++ [http://www.boost.org boost] is probably a familiar library. As it so happens, it's also a good match for being paired, quite easily, with bitten!
+If you're developing with C++, [http://www.boost.org boost] is probably a familiar library. As it so happens, it's also a good match for being paired, quite easily, with bitten!
 
 By roaming around the wiki (here: DataStorage) you can gather how bitten stores reports, and how ''test'' reports in particular are stored and used. For each test case a number of properties are stored, such as status and the fixture/test suite it belongs to.
@@ -8 +8 @@
 == Gathering the report ==
 
-Fortunately for us, Boost.Test outputs test reports in XML format, if instructed to do so. Thus, the amount of work we have to carry out is reduced to specifying and applying a simple XSL transform!
+Fortunately for us, Boost.Test outputs test reports in XML format, if instructed to do so. Thus, the amount of work we have to carry out is reduced to specifying and applying a simple XSL transform.
 
 But before we proceed to the needed transform we have to actually gather the XML data from boost. Suppose the program that runs your tests is called {{{run_tests}}}, then we can get an XML report by running that program as:
@@ -50 +50 @@
 Use the `<x:transform>` recipe command to do this. An example on how to use it is below. You will, of course, have to put this in your repository somewhere.
 
-== Cooking up your build recipe ==
+== Adjusting your recipe to make delicious Boost.Test soup ==
 
 Here's a template for how to put all of this together in your build recipe: