TransactionManagementError “You can’t execute queries until the end of the ‘atomic’ block” while using signals, but only during Unit Testing

by

I ran into this same problem myself. This is caused by a quirk in how transactions are handled in the newer versions of Django coupled with a unittest that intentionally triggers an exception.

I had a unittest that checked to make sure a unique column constraint was enforced by purposefully triggering an IntegrityError exception:

def test_constraint(self):
    try:
        # Duplicates should be prevented.
        models.Question.objects.create(domain=self.domain, slug='barks')
        self.fail('Duplicate question allowed.')
    except IntegrityError:
        pass

    do_more_model_stuff()

In Django 1.4, this works fine. However, in Django 1.5/1.6, each test is wrapped in a transaction, so if an exception occurs, it breaks the transaction until you explicitly roll it back. Therefore, any further ORM operations in that transaction, such as my do_more_model_stuff(), will fail with that django.db.transaction.TransactionManagementError exception.

Like caio mentioned in the comments, the solution is to capture your exception with transaction.atomic like:

from django.db import transaction
def test_constraint(self):
    try:
        # Duplicates should be prevented.
        with transaction.atomic():
            models.Question.objects.create(domain=self.domain, slug='barks')
        self.fail('Duplicate question allowed.')
    except IntegrityError:
        pass

That will prevent the purposefully-thrown exception from breaking the entire unittest’s transaction.

More Related Contents:

  1. Run / Debug a Django application’s UnitTests from the mouse right click context menu in PyCharm Community Edition?
  2. Django signals vs. overriding save method
  3. Django post_save() signal implementation
  4. How to run Django’s test database only in memory?
  5. How can I disable logging while running unit tests in Python Django?
  6. How do I prevent fixtures from conflicting with django post_save signal code?
  7. How to run django unit-tests on production database?
  8. Django post_save preventing recursion without overriding model save()
  9. Running a specific test case in Django when your app has a tests directory
  10. Identify the changed fields in django post_save signal
  11. How can I specify a database for Django Tests to use instead of having it build it every time?
  12. Django: How to create a model dynamically just for testing
  13. Django CSRF check failing with an Ajax POST request
  14. Having Django serve downloadable files
  15. How can I enable CORS on Django REST Framework
  16. Iterating through two lists in Django templates
  17. How do I extend the Django Group model?
  18. How can I create a ramdisk in Python?
  19. When to use Serializer’s create() and ModelViewset’s perform_create()
  20. What is choice_set in this Django app tutorial?
  21. Django values_list vs values
  22. Why doesn’t django’s model.save() call full_clean()?
  23. What’s the best solution for OpenID with Django? [closed]
  24. How can I get the current language in Django?
  25. QuerySet, Object has no attribute id – Django
  26. How to update manytomany field in Django?
  27. Install mysqlclient for Django Python on Mac OS X Sierra
  28. How to get more diagnostic output on a “no module named xyz” error?
  29. Django admin: How to display the field marked as “editable=False” in the model?
  30. How to solve “Page not found (404)” error in Django?

Leave a Comment