wiki:UnitTestIntegration

Version 2 (modified by andrew, 5 years ago) (diff)

--

Unit Test Integration

By default, South's syncdb command will also apply migrations if it's run in non-interactive mode (e.g. as part of ./manage.py test).

This means South is already integrated in your unit test process; if you try testing, you'll see the migrations are all applied just after the non-migrated apps are synced.

Nice, eh?

South's own unit tests

South has its own set of unit tests; these will also be run when you run ./manage.py test. They do some fiddling with Django internals to set up a proper test environment; it's non-destructive, but if it's fouling up your own tests please submit a ticket about it.

You can also set SKIP_SOUTH_TESTS=True in settings.py to stop South's tests running.