documentation updated

1 files changed, 20 insertions, 24 deletions

diff --git a/docs/tests.rst b/docs/tests.rst
index dbd03e3..063a812 100644
--- a/docs/tests.rst
+++ b/docs/tests.rst
@@ -15,16 +15,23 @@ the benefits of software testing, some prophets will do it better than me.
 * http://en.wikipedia.org/wiki/Software_testing
 * https://docs.djangoproject.com/en/dev/topics/testing/
 
-Of course Gstudio is tested using the `unittest`_  approach.
-All the tests belong in the directory :file:`gstudio/tests/`.
+Of course gnowsys-studio has a testing framework. However, we were
+impatient and developed several hasty features, without writing
+unit-tests. You have been warned.  Please contribute if you have a
+zeal to write test cases to match the software requirements and use
+cases.
+
+ All the tests belong in the directory :file:`gstudio/tests/` and
+ `objectapp/tests`.
 
 .. _lauching-test-suite:
 
 Launching the test suite
 ========================
 
-If you have :ref:`run the buildout script<running-the-buildout>` bundled in
-Gstudio, the tests are run under `nose`_ by launching this command: ::
+If you have :ref:`run the buildout script<running-the-buildout>`
+bundled in gnowsys-studio, the tests are run under `nose`_ by
+launching this command: ::
 
   $ ./bin/test
 
@@ -32,13 +39,16 @@ But the tests can also be launched within a Django project with the default
 test runner: ::
 
   $ django-admin.py test gstudio --settings=gstudio.testsettings
+  $ django-admin.py test objectapp --settings=gstudio.testsettings
 
-Using the ``./bin/test`` script is usefull when you develop because the tests
-are calibrated to run fast, but testing Gstudio within a Django project even
-if it's slow, can prevent some integration issues.
+Using the ``./bin/test`` script is usefull when you develop because
+the tests are calibrated to run fast, but testing gnowsys-studio
+within a Django project even if it's slow, can prevent some
+integration issues.
 
-If you want to make some speed optimizations or compare with your tests
-results, you can check the actual execution time of the tests at this URL:
+If you want to make some speed optimizations or compare with your
+tests results, you can check the actual execution time of the tests at
+this URL:
 
 http://django-blog-gstudio.com/documentation/xunit/
 
@@ -47,22 +57,8 @@ http://django-blog-gstudio.com/documentation/xunit/
 Coverage
 ========
 
-Despite my best efforts, some functionnalities are not yet tested, that's why
-I need your help !
-
-As I write these lines the **121** tests in Gstudio cover **96%** of the code
-bundled in Gstudio. A real effort has been made to obtain this percentage,
-for ensuring the quality of the code.
-
-I know that a coverage percent does not represent the quality of the tests,
-but maintaining or increasing this percentage ensures the quality of
-Gstudio and his future evolutions.
-
-You can check the actual coverage percent at this URL:
-
-http://django-blog-gstudio.com/documentation/coverage/
+We need help here. Any body there?
 
-I hope that you will write some tests and find some bugs. :)
 
 .. _`unittest`: http://docs.python.org/library/unittest.html
 .. _`nose`: http://somethingaboutorange.com/mrl/projects/nose/