mockpp-commits

[Ewald A. <ewa...@us...>]

Update of /cvsroot/mockpp/mockpp/mockpp/docs/en
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28468/mockpp/docs/en

Modified Files:
	appendix.docbook dev_embedded.docbook dev_intro.docbook 
	dev_test_framework.docbook 
Log Message:
select test framework

Index: appendix.docbook
===================================================================
RCS file: /cvsroot/mockpp/mockpp/mockpp/docs/en/appendix.docbook,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -d -r1.14 -r1.15
--- appendix.docbook	27 Dec 2005 18:01:44 -0000	1.14
+++ appendix.docbook	28 Dec 2005 09:23:30 -0000	1.15
@@ -17,12 +17,6 @@
 <sect1 id="requirements">
 <title>Requirements</title>
 
-<para>
-In order to fully benefit from &mockpp;, you need
-<ulink url="http://cppunit.sf.net">&cppunit;</ulink>, a framework for unit tests
-with C++. Any other framework should work for development as well but &cppunit;
-is used for the internal unittests.</para>
-
 </sect1>
 
 <sect1 id="compilation">

Index: dev_intro.docbook
===================================================================
RCS file: /cvsroot/mockpp/mockpp/mockpp/docs/en/dev_intro.docbook,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- dev_intro.docbook	27 Dec 2005 18:01:44 -0000	1.7
+++ dev_intro.docbook	28 Dec 2005 09:23:30 -0000	1.8
@@ -33,7 +33,7 @@
   </listitem>
 
   <listitem>&mockpp; has no testing framework of it's own so it is recommended
-     to use <ulink url="http://cppunit.sf.net">CppUnit</ulink> for that purpose.
+     to use <ulink url="http://cppunit.sf.net">&cppunit;</ulink> for that purpose.
      See the test and example files how to do it.
   </listitem>
 

Index: dev_test_framework.docbook
===================================================================
RCS file: /cvsroot/mockpp/mockpp/mockpp/docs/en/dev_test_framework.docbook,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- dev_test_framework.docbook	27 Dec 2005 18:01:44 -0000	1.3
+++ dev_test_framework.docbook	28 Dec 2005 09:23:30 -0000	1.4
@@ -14,7 +14,8 @@
 <sect2 id="framework-cppunit">
 <title>CppUnit</title>
 
-<para>Tests with &cppunit; are usually grouped in classes. A method contains one
+<para>Tests with <ulink url="http://cppunit.sf.net">&cppunit;</ulink>
+are usually grouped in classes. A method contains one
 single test. Each of the tests is typically registered automatically with a test
 runner by using some macros. This is internally done by instantiating a static
 variable.</para>
@@ -50,9 +51,11 @@
 <sect2 id="framework-cxxtest">
 <title>CxxTest</title>
 
-<para>The original working method of &cxxtest; is different to &cppunit;. A perl
+<para>The original working method of
+<ulink url="http://cxxtest.sf.net">&cxxtest;</ulink>
+is different to &cppunit;. A perl
 script searches the test sources and creates an additional source file which
-is then call compiled and run. All the library source files are directly included
+is then compiled and run. All the library source files are directly included
 into the main source file which means that you do not need to create a binary
 library for &cxxtest;.</para>
 

Index: dev_embedded.docbook
===================================================================
RCS file: /cvsroot/mockpp/mockpp/mockpp/docs/en/dev_embedded.docbook,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- dev_embedded.docbook	27 Dec 2005 18:01:44 -0000	1.9
+++ dev_embedded.docbook	28 Dec 2005 09:23:30 -0000	1.10
@@ -144,7 +144,9 @@
 to print a message to the screen and exit the application. Alternatively you may
 as well call the according collector of your unittest framework. E.g.
 <methodname>CPPUNIT_FAIL</methodname> for &cppunit; or
-<methodname>TS_FAIL</methodname> for &cxxtest;.
+<methodname>TS_FAIL</methodname> for &cxxtest;.</para>
+
+<para>The following listing shows a possible scenario without exceptions:
 
 <programlisting>
 
@@ -179,14 +181,16 @@
 
 ...
 
-  setAssertionFailedForwarder(printMalfunctionData&lt;mockpp::AssertionFailedError>);
+setAssertionFailedForwarder(printMalfunctionData&lt;mockpp::AssertionFailedError>);
 
 </programlisting>
 
 </para>
 
 <para>The test file <filename>tests/NoException_test.cpp</filename> shows a
-working solution.</para>
+working solution. This file is designed to work under all library settings by
+using special types. Using types like <token>int</token> or
+<token>std::string</token> might not work with the settings on your machine.</para>
 
 </sect2>