Make tests in the Wiki2 tutorial a separate chapter, as for Wiki1.

Also add functional tests to the Wiki2 tutorial, similar to Wiki1.

1 files changed, 0 insertions, 43 deletions

diff --git a/docs/tutorials/wiki2/definingviews.rst b/docs/tutorials/wiki2/definingviews.rst
index 8fd9a9399..cea376b77 100644
--- a/docs/tutorials/wiki2/definingviews.rst
+++ b/docs/tutorials/wiki2/definingviews.rst
@@ -341,46 +341,3 @@ Exception('Forced Exception')``).  Then visit the error-raising view
 in a browser.  You should see an interactive exception handler in the
 browser which allows you to examine values in a post-mortem mode.
 
-Adding Tests
-============
-
-Since we've added a good bit of imperative code here, it's useful to
-define tests for the views we've created.  We'll change our tests.py
-module to look like this:
-
-.. literalinclude:: src/views/tutorial/tests.py
-   :linenos:
-   :language: python
-
-We can then run the tests using something like:
-
-.. code-block:: text
-   :linenos:
-
-    $ python setup.py test -q
-
-The expected output is something like:
-
-.. code-block:: text
-   :linenos:
-
-   running test
-   running egg_info
-   writing requirements to tutorial.egg-info/requires.txt
-   writing tutorial.egg-info/PKG-INFO
-   writing top-level names to tutorial.egg-info/top_level.txt
-   writing dependency_links to tutorial.egg-info/dependency_links.txt
-   writing entry points to tutorial.egg-info/entry_points.txt
-   unrecognized .svn/entries format in
-   reading manifest file 'tutorial.egg-info/SOURCES.txt'
-   writing manifest file 'tutorial.egg-info/SOURCES.txt'
-   running build_ext
-   ......
-   ----------------------------------------------------------------------
-   Ran 6 tests in 0.181s
-
-   OK
-
-
-
-