summaryrefslogtreecommitdiff
path: root/docs/tutorials/wiki/tests.rst
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2011-11-11 12:25:59 -0500
committerChris McDonough <chrism@plope.com>2011-11-11 12:25:59 -0500
commitc8e2f8e35c99b4f35d53ed0bb73e737e97ef345c (patch)
tree117cd5f89699c22bbb112bcf1a1d71b26037de15 /docs/tutorials/wiki/tests.rst
parent9da33516637075b5a41b2e8bf500297a4cb71166 (diff)
parent41de98e3287b8ddd457c24ea952839261b3b462f (diff)
downloadpyramid-c8e2f8e35c99b4f35d53ed0bb73e737e97ef345c.tar.gz
pyramid-c8e2f8e35c99b4f35d53ed0bb73e737e97ef345c.tar.bz2
pyramid-c8e2f8e35c99b4f35d53ed0bb73e737e97ef345c.zip
Merge branch 'master' of github.com:Pylons/pyramid
Diffstat (limited to 'docs/tutorials/wiki/tests.rst')
-rw-r--r--docs/tutorials/wiki/tests.rst18
1 files changed, 9 insertions, 9 deletions
diff --git a/docs/tutorials/wiki/tests.rst b/docs/tutorials/wiki/tests.rst
index 841baa8d1..941302d67 100644
--- a/docs/tutorials/wiki/tests.rst
+++ b/docs/tutorials/wiki/tests.rst
@@ -6,8 +6,8 @@ We will now add tests for the models and the views and a few functional
tests in the ``tests.py``. Tests ensure that an application works, and
that it continues to work after some changes are made in the future.
-Testing the Models
-==================
+Test the Models
+===============
We write tests for the model
classes and the appmaker. Changing ``tests.py``, we'll write a separate test
@@ -15,13 +15,13 @@ class for each model class, and we'll write a test class for the
``appmaker``.
To do so, we'll retain the ``tutorial.tests.ViewTests`` class provided as a
-result of the ``pyramid_zodb`` project generator. We'll add three test
+result of the ``zodb`` project generator. We'll add three test
classes: one for the ``Page`` model named ``PageModelTests``, one for the
``Wiki`` model named ``WikiModelTests``, and one for the appmaker named
``AppmakerTests``.
-Testing the Views
-=================
+Test the Views
+==============
We'll modify our ``tests.py`` file, adding tests for each view function we
added above. As a result, we'll *delete* the ``ViewTests`` test in the file,
@@ -38,8 +38,8 @@ tested in the unit tests, like logging in, logging out, checking that
the ``viewer`` user cannot add or edit pages, but the ``editor`` user
can, and so on.
-Viewing the results of all our edits to ``tests.py``
-====================================================
+View the results of all our edits to ``tests.py``
+=================================================
Once we're done with the ``tests.py`` module, it will look a lot like the
below:
@@ -48,8 +48,8 @@ below:
:linenos:
:language: python
-Running the Tests
-=================
+Run the Tests
+=============
We can run these tests by using ``setup.py test`` in the same way we did in
:ref:`running_tests`. However, first we must edit our ``setup.py`` to