skip to navigation
skip to content

Not Logged In

django-attest 0.7.1

Provides Django specific testing helpers to Attest

Latest Version: 0.10.0


Django testing for Attest. Requires Django >=1.2.


Use pip:

pip install django-attest


Create a test collection and optionally include one of django-attest's test contexts. The result is that a client argument is passed to each test within the collection. client is a django.test.TestClient object and allows you to make HTTP requests to your project.

from attest import Tests
from django_attest import TestContext

tests = Tests()

def can_add(client):
    client.get('/some-url/')  # same as self.client.get() if you were using
                              # the standard django.test.TestCase approach

See the TestCase.client documentation for more details.

When using a django.test.TestCase subclass, you're able to specify various options that affect the environment in which your tests are executed. django-attest provides the same functionality via keyword arguments to the TestContext. The following keyword arguments are supported:

For example if you want to specify fixtures, urls, a client_class, or multi_db, simply pass in these options when creating the django_tables.TestContext object:

from attest import Tests
from django_attest import TestContext

tests = Tests()
tests.context(TestContext(fixtures=['testdata.json'], urls='myapp.urls'))

Transaction management in tests

If you need to test transaction management within your tests, use TransactionTestContext rather than TestContext, e.g.:

from attest import Tests
from django_attest import TransactionTestContext

tests = Tests()

def some_test(client):
    # test something

Testing a reusable Django app

A flexible approach is to create a tests Django project. This shouldn't be the fully-fledged output of startproject, but instead the minimum required to keep Django happy.


from attest import assert_hook, Tests
import os
os.environ['DJANGO_SETTINGS_MODULE'] = 'tests.settings'
from django_attest import auto_loader

loader = autor_loader.test_loader
suite = Tests()

def example():
    assert len("abc") == 3

Django's built-in test runner performs various environment initialisation and cleanup tasks. It's important that tests are run using one of the loaders from django-attest.


    'default': {
        'ENGINE': 'django.db.backends.sqlite3',
        'NAME': ':memory:',


SECRET_KEY = 'abcdefghiljklmnopqrstuvwxyz'

ROOT_URLCONF = 'tests.urls'


from django.conf.urls import patterns
urlpatterns = patterns('')

from setuptools import setup
    tests_require=['Django >=1.2', 'Attest >=0.4', 'django-attest'],

Running the tests

python test

Testing non-reusable apps in a Django project

To test non-reusable apps in a Django project, the app must contain either a tests or models module with either a suite function that returns a unittest.TestCase, or simply contains TestCase classes. (see Django's documentation for details).

As of Attest 0.6 you should use test cases:

# myapp/
from attest import Tests

template = Tests()

def filter():
    # ...

template = template.test_case()

This allows Django to find your tests, and allows you to run individual tests, e.g.:

python test myapp.template.test_filter


When a unittest.TestCase is created from a test collection, the function names are prefixed with test_.

Prior to Attest 0.6, you must use the test suite option, which unfortunately doesn't support running individual tests:

from attest import Tests

template = Tests()

def filter():
    # ...

suite = template.test_suite

assert hook

Prior to Attest 0.5, the assert hook was enabled on first import of attest. As of Attest 0.6, this is no longer the case – instead it occurs when you use the attest command line program to execute tests.

Since Django uses as its entry point, django-attest enables the assert hook automatically when it's first imported.

This means that you need to do the following:

  1. Make sure django_attest is imported as soon as possible.
  2. Add from attest import assert_hook to the top of each test module.

Django assertions

For details on each of these, see django_attest/


Assert that a response redirects to some resource:

from django_attest import redirects

response = client.get('/')
redirects(response, path="/foo/")


Assert an expected set of queries took place:

from django_attest import queries

with queries() as qs:
assert len(qs) == 5

# The same could be rewritten as
with queries(count=5):

Context managers

django-attest has some context managers to simplify common tasks:


Change global settings within a block, same functionality as Django 1.4's TestCase.settings:

from django_attest import settings

with settings(MEDIA_ROOT="/tmp"):
    # ...

Code that's sensitive to settings changes should use the django_attest.signals.setting_changed signal to overcome any assumptions of settings remaining constant.


On Django >=1.4, django_attest.signals.setting_changed is an alias of django.test.signals.setting_changed.


Takes a list of URL patterns and promotes them up as the root URLconf. This avoids the need to have a dedicated test project and for simple cases:

def foo(client):
    def view(request):
        return HttpResponse('success')

    urls = patterns('', (r'view/', view))
    with urlconf(urls):
        assert client.get(reverse(view)).content == 'success'

If you want to provide a dotted path to a, use settings(ROOT_URLCONF=...) instead, it takes care to clear URL resolver caches.


  • django_attest.RequestFactory (from Django 1.4)
  • django_attest.settings (override_settings inspired from Django 1.4)
File Type Py Version Uploaded on Size
django-attest-0.7.1.tar.gz (md5) Source 2012-09-21 8KB
  • Downloads (All Versions):
  • 60 downloads in the last day
  • 456 downloads in the last week
  • 1789 downloads in the last month