Changes between Version 1 and Version 2 of Boost Test

Timestamp:

Sep 29, 2006, 2:17:48 PM (18 years ago)

Author:

staffan

Comment:

typo+minor edits

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 happends, 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 digging around some (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.
+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.
 This data is few to bitten by the `<report>` recipe command (RecipeCommands). We just have to make sure it receives it in a format that it understands.
 
@@ -16 +16 @@
 }}}
 
-The detailed report level is needed for the XSL transform provided in the next section. Furthermore, you have to somehow store this in a file, `test_results.xml` - there are several to do this, which I leave up to you to figure out (hint: redirect stderr/cerr or read the boost docs).
+The detailed report level is needed for the XSL transform provided in the next section. Furthermore, you have to somehow store this in a file, ''test_results.xml'' below. There are several to do this, which I leave up to you to figure out (hint: redirect stderr/cerr or read the boost docs).
 
 == Making it bitten-friendly ==
@@ -48 +48 @@
 }}}
 
-Use the `<x:transform>` recipe command to do this. I'll give an example below.
+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 ==