django/test/simple.py Imports django.db even when your app dosn't use a db

[Damian Zaremba]

Even if your app requires no database interaction the testing module still imports django.db. To get around this you have to do stupid things like create an sqllite db in memory. This shouldn't be required as if your app doesn't need a db you shouldn't have to configure one and the testing framework shouldn't test it (or there should be a way to ignore it).

[Russell Keith-Magee]

It's not just the import that is a problem. The simple test runner constructs and destroys a test database.

If you don't want to use a database at all, you can define a custom test runner; in 1.2, this looks something like:

from django.test.simple import DjangoTestSuiteRunner

class MyRunner(DjangoTestSuiteRunner):
    def setup_databases(self, **kwargs):
        pass
    def teardown_databases(self, old_config, **kwargs):
        pass

Then, put TEST_RUNNER = 'path.to.runner.MyRunner' in your settings.py.

There is an analogous approach in 1.1, but it involves copying django.test.simple.run_tests() and removing the database setup lines.