Index: main/waeup.kofa/trunk/docs/source/userdocs/testing.rst
===================================================================
--- main/waeup.kofa/trunk/docs/source/userdocs/testing.rst	(revision 12927)
+++ main/waeup.kofa/trunk/docs/source/userdocs/testing.rst	(revision 12928)
@@ -21,4 +21,13 @@
 started. This job can't be done manually.
 
+Why *automated* testing? Simply because no developer likes to click
+around the user interface to check tons of functionality. In Kofa more
+than 1100 tests, with dozens of actions per test, are being executed
+each time when the testrunner is started. This job can't be done
+manually.
+
+What we test: "unit" and "functional" Tests
+-------------------------------------------
+
 There are two different ways to test the code of a web application
 automatically: *unit tests* and *functional tests*. The goal of unit
@@ -31,5 +40,9 @@
 functional testing has to make use of a test browser. A test browser
 does the same job as normal web browser does, except for visualizing
-the rendered html code.
+the rendered HTML code.
+
+
+How we test: "Python" and "Doctest" Tests
+-----------------------------------------
 
 There are also two different ways to integrate tests, either
