Ignore:
Timestamp:
18 May 2015, 05:07:59 (9 years ago)
Author:
Henrik Bettermann
Message:

Remove duplicate text passage.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • main/waeup.kofa/trunk/docs/source/userdocs/testing.rst

    r12952 r12964  
    11.. _testing:
    22
    3 Testing :sup:`in progress`
    4 **************************
     3Testing
     4*******
    55
    66Introduction
     
    1515given sets of conditions and, only comprehensive testing ensures
    1616that changing or customizing the code does not break existing
    17 functionality. Why *automated* testing? Simply because no developer
    18 likes to click around the user interface to check tons of
    19 functionality. In Kofa more than 1300 tests, with dozens of actions
    20 per test, are being executed each time when the testrunner is
    21 started. This job can't be done manually.
     17functionality.
    2218
    2319Why *automated* testing? Simply because no developer likes to click
    24 around the user interface to check tons of functionality. In Kofa more
    25 than 1100 tests, with dozens of actions per test, are being executed
    26 each time when the testrunner is started. This job can't be done
    27 manually.
     20around the user interface to check tons of functionality. In Kofa
     21more than 1300 tests, with dozens of actions per test, are being
     22executed each time when the testrunner is started. This job can't be
     23done manually.
    2824
    2925What we test: "Unit" and "Functional" Tests
     
    7773When starting the development of Kofa, we relied on writing a
    7874coherent documentation including doctests in restructured text
    79 format. During the software development process the focus shifted
     75format. During the software development process, the focus shifted
    8076from doctesting to pure Python testing with a lot of functional
    8177tests inside. It turned out that Python tests are easier to handle
     
    186182   :pyobject: test_suspended_officer
    187183
    188 The test makes sure that a suspended officers can't login but see a
     184This test makes sure that a suspended officers can't login but see a
    189185proper warning message when trying to login. Furthermore, suspended
    190186officer accounts are clearly marked and a warning message shows up
    191187if a manager accesses a suspended account, see :ref:`Officers
    192188<officers>`.
     189
     190Further tests will follow soon.
Note: See TracChangeset for help on using the changeset viewer.