Testing manual transactions inside Django unittests

Question

How do you test code that disables autocommit and uses savepoints, inside a Django unittest?

The default Django unittest class wraps all tests inside an @atomic decorator, which is usually exactly what you want, to ensure the sqlite database gets reset between tests. However, any code that touches transaction.set_autocommit() from a test throws the error:

TransactionManagementError: This is forbidden when an 'atomic' block is active.

even if it works fine outside the unittest.

How do you temporarily disable the transaction autocommit in a unittest, so you can test manual commits?

I am not entirely sure this works in tests, but try adding a @transaction.commit_on_success decorator to the test function — Simas Joneliunas
– Simas Joneliunas, Commented Jul 4, 2018 at 1:37
@SimasJoneliunas That decorator was removed several versions ago and is not available to me. — Cerin
– Cerin, Commented Jul 4, 2018 at 1:46

Kevin Christopher Henry · Accepted Answer · 2018-07-04 04:09:15Z

1

Use TransactionTestCase:

TransactionTestCase and TestCase are identical except for the manner in which the database is reset to a known state and the ability for test code to test the effects of commit and rollback: A TransactionTestCase resets the database after the test runs by truncating all tables. A TransactionTestCase may call commit and rollback and observe the effects of these calls on the database.

answered Jul 4, 2018 at 4:09

Kevin Christopher Henry

49.7k8 gold badges125 silver badges111 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Testing manual transactions inside Django unittests

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related