Changeset 12964

Timestamp:

18 May 2015, 05:07:59 (10 years ago)

Author:

Henrik Bettermann

Message:

Remove duplicate text passage.

File:

• main/waeup.kofa/trunk/docs/source/userdocs/testing.rst (modified) (4 diffs)

main/waeup.kofa/trunk/docs/source/userdocs/testing.rst

@@ -1 +1 @@
 .. _testing:
 
-Testing :sup:`in progress`
-**************************
+Testing
+*******
 
 Introduction
@@ -15 +15 @@
 given sets of conditions and, only comprehensive testing ensures
 that changing or customizing the code does not break existing
-functionality. Why *automated* testing? Simply because no developer
-likes to click around the user interface to check tons of
-functionality. In Kofa more than 1300 tests, with dozens of actions
-per test, are being executed each time when the testrunner is
-started. This job can't be done manually.
+functionality.
 
 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.
+around the user interface to check tons of functionality. In Kofa
+more than 1300 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
@@ -77 +73 @@
 When starting the development of Kofa, we relied on writing a
 coherent documentation including doctests in restructured text
-format. During the software development process the focus shifted
+format. During the software development process, the focus shifted
 from doctesting to pure Python testing with a lot of functional
 tests inside. It turned out that Python tests are easier to handle
@@ -186 +182 @@
    :pyobject: test_suspended_officer
 
-The test makes sure that a suspended officers can't login but see a
+This test makes sure that a suspended officers can't login but see a
 proper warning message when trying to login. Furthermore, suspended
 officer accounts are clearly marked and a warning message shows up
 if a manager accesses a suspended account, see :ref:`Officers
 <officers>`.
+
+Further tests will follow soon.