When writing unittests make sure that any postorius.* imports are made -at the test method level and not at the module level. Here’s why:
-The Postorius documentation (the one you are reading right now) imports some -doctest modules from the test package using Sphinx’s autodoc extension. This is -a very nice feature, but in this scenario it has the nasty side effect of -breaking the build process if application code is imported as well (it will -fail to find an environment variable that Django needs to run). This can be -easily prevented by avoiding module level imports of postorius code in the test -modules.
-Good:
-from django.utils import unittest
-from mock import patch
-
-
-class SomeTest(unittest.TestCase):
-
- def test_some_method(self):
- from postorius.views import SomeViewClass
- foo = 'bar'
-Bad:
-from django.utils import unittest
-from mock import patch
-from postorius.views import SomeViewClass
-
-
-class SomeTest(unittest.TestCase):
-
- def test_some_method(self):
- foo = 'bar'
-To run the tests go to your project folder and run python manage.py test postorius from there.
postorius.tests.utils.create_mock_list creates a mock domain object:
+postorius.tests.utils.create_mock_domain creates a mock domain object:
>>> properties = dict(contact_address='postmaster@example.org',
... description='Example dot Org',
... mail_host='example.org',
@@ -192,7 +160,7 @@