south / docs / unittests.rst

Unit Test Integration

By default, South's syncdb command will also apply migrations if it's run in non-interactive mode, which includes when you're running tests - it will run every migration every time you run your tests.

If you want the test runner to use syncdb instead of migrate - for example, if your migrations are taking way too long to apply - simply set SOUTH_TESTS_MIGRATE = False in

South's own unit tests

South has its own set of unit tests; these will also be run when you run ./ 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 to stop South's tests running, should they be causing issues.

Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.