Please sign in to comment.
Fixed #8138 -- Changed django.test.TestCase to rollback tests (when …
…the database supports it) instead of flushing and reloading the database. This can substantially reduce the time it takes to run large test suites. This change may be slightly backwards incompatible, if existing tests need to test transactional behavior, or if they rely on invalid assumptions or a specific test case ordering. For the first case, django.test.TransactionTestCase should be used. TransactionTestCase is also a quick fix to get around test case errors revealed by the new rollback approach, but a better long-term fix is to correct the test case. See the testing doc for full details. Many thanks to: * Marc Remolt for the initial proposal and implementation. * Luke Plant for initial testing and improving the implementation. * Ramiro Morales for feedback and help with tracking down a mysterious PostgreSQL issue. * Eric Holscher for feedback regarding the effect of the change on the Ellington testsuite. * Russell Keith-Magee for guidance and feedback from beginning to end. git-svn-id: http://code.djangoproject.com/svn/django/trunk@9756 bcc190cf-cafb-0310-a4f2-bffc1f526a37
- Loading branch information...
Showing with 251 additions and 51 deletions.
- +1 −0 AUTHORS
- +15 −2 django/db/backends/creation.py
- +1 −1 django/test/__init__.py
- +3 −0 django/test/client.py
- +40 −1 django/test/simple.py
- +77 −5 django/test/testcases.py
- +46 −0 docs/topics/testing.txt
- +16 −5 tests/regressiontests/comment_tests/tests/comment_view_tests.py
- +43 −34 tests/regressiontests/comment_tests/tests/moderation_view_tests.py
- +3 −0 tests/regressiontests/file_uploads/tests.py
- +6 −3 tests/regressiontests/generic_inline_admin/tests.py
Oops, something went wrong.