Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Branch: 1.5-branch
Fetching contributors…

Cannot retrieve contributors at this time

104 lines (71 sloc) 3.022 kB

Adding Tests

We will now add tests for the models and the views and a few functional tests in tests.py. Tests ensure that an application works, and that it continues to work when changes are made in the future.

Test the models

We write tests for the model classes and the appmaker. Changing tests.py, we'll write a separate test 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 that was generated as part of the zodb scaffold. 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.

Test the views

We'll modify our tests.py file, adding tests for each view function we added previously. As a result, we'll delete the ViewTests class that the zodb scaffold provided, and add four other test classes: ViewWikiTests, ViewPageTests, AddPageTests, and EditPageTests. These test the view_wiki, view_page, add_page, and edit_page views.

Functional tests

We'll test the whole application, covering security aspects that are not 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.

View the results of all our edits to tests.py

Open the tutorial/tests.py module, and edit it such that it appears as follows:

Running 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 include a dependency on WebTest, which we've used in our tests.py. Change the requires list in setup.py to include WebTest.

After we've added a dependency on WebTest in setup.py, we need to run setup.py develop to get WebTest installed into our virtualenv. Assuming our shell's current working directory is the "tutorial" distribution directory:

On UNIX:

$ $VENV/bin/python setup.py develop

On Windows:

c:\pyramidtut\tutorial> %VENV%\Scripts\python setup.py develop

Once that command has completed successfully, we can run the tests themselves:

On UNIX:

$ $VENV/bin/python setup.py test -q

On Windows:

c:\pyramidtut\tutorial> %VENV%\Scripts\python setup.py test -q

The expected result should look like the following:

.........
----------------------------------------------------------------------
Ran 23 tests in 1.653s

OK
Jump to Line
Something went wrong with that request. Please try again.