As much as I like some Django concepts and as much as authors embrace testing in official documentation, I doubt that anyone really tried them in detail. Some basic testing techniques are impossible with Django and this library comes to fix them.
One of the great flaws is very simplistic testing system. By it’s nature it’s very slow (flushing database when not needed ), it does not allow some basic xUnit features and also do not allow testing via HTTP  and provides to extensibility model to fix the issues.
However, there is an excellent option available. Nose library is excellent test-dicovery framework, backward-compatible with PyUnit, that provides nice plugin interface to hook your own stuff. To make my life simpler, most of this library is made as a nose plugin.
And don’t be afraid, we have TEST_RUNNER too, so your ./manage.py test will still work.
Library supports following:
- Nose integration (load plugins and try noserun)
- Django integration (./manage.py test and boo ya)
- True unittests (no database interaction, no handling needed = SPEED)
- HTTP tests (has included wrapper for urlopen from urllib2)
- Transactional database tests (everything in one transaction, no database flush)
- Selenium RC integration (our pages needs to be tested with browser)
- CherryPy can be used instead of Django ‘s WSGI (when you need usable server )
Differences from standard Django test runner¶
If You are using older version than Django 1.3, you will be able to use unittest2 goodies.
Unlike Django’s test runner, django-sane-testing do not modify your DEBUG behavior. You are free to run with DEBUG = True, which might be handy under some circumstances.
|||At least transactional test cases are going to be implemented in Django 1.1, see #8138.|
|||Kinda buggy when we’re talking about HTTP framework. See #2879.|