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.
We write a test class for the model class Page and another test class
for the initialize_sql function.
To do so, we'll retain the tutorial.tests.ViewTests class provided as a
result of the pyramid_routesalchemy project generator. We'll add two
test classes: one for the Page model named PageModelTests, one for the
initialize_sql function named InitializeSqlTests.
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,
and add four other test classes: ViewWikiTests, ViewPageTests,
AddPageTests, and EditPageTests. These test the view_wiki,
view_page, add_page, and edit_page views respectively.
We 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.
Once we're done with the tests.py module, it will look a lot like the
below:
.. literalinclude:: src/tests/tutorial/tests.py :linenos: :language: python
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.
.. literalinclude:: src/tests/setup.py :linenos: :language: python :lines: 10-19
After we've added a dependency on WebTest in setup.py, assuming our
shell's current working directory is the "tutorial" distribution directory:
On UNIX:
$ ../bin/python setup.py test -q
On Windows:
c:\pyramidtut\tutorial> ..\Scripts\python setup.py test -q
The expected result looks something like:
......................
----------------------------------------------------------------------
Ran 22 tests in 2.700s
OK