This package is most useful when installed with:
- Django 1.2+
Upgrading from Django < 1.2
Django 1.2 switches to a class-based test runner. To use
with Django 1.2, change your
django_nose.run_tests will continue to work in Django 1.2, but will raise a
warning. In Django 1.3 it will stop working.
If you were using
django_nose.run_gis_tests, you should also switch to
django_nose.NoseTestSuiteRunner and use one of the spatial backends in
You can get django-nose from pypi with:
pip install django-nose
The development version can be installed with:
pip install -e git://github.com/jbalogh/django-nose.git#egg=django-nose
Since django-nose extends Django's built-in test command, you should add it to
INSTALLED_APPS = ( ... 'django_nose', ... )
TEST_RUNNER = 'django_nose.NoseTestSuiteRunner'
./manage.py help test for all the options nose provides, and look to
the nose docs for more help with nose.
Always Passing The Same Options
To always set the same command line options you can use a nose.cfg or setup.cfg (as usual) or you can specify them in settings.py like this:
NOSE_ARGS = ['--failed', '--stop']
Using Custom Plugins
If you need to make custom plugins, you can define each plugin class somewhere within your app and load them from settings.py like this:
NOSE_PLUGINS = [ 'yourapp.tests.plugins.SystematicDysfunctioner', # ... ]
Just like middleware or anything else, each string must be a dot separated, importable path to an actual class. Each plugin class will be instantiated and added to the Nose test runner.
South installs its own test command that turns off migrations during
testing. Make sure that
django_nose comes after
INSTALLED_APPS so that django_nose's test command is used.
Support for Django 1.1
If you want to use django-nose with Django 1.1, use https://github.com/jbalogh/django-nose/tree/django-1.1 or http://pypi.python.org/pypi/django-nose/0.0.3.