#12087: Django "TransactionTestCase" isn't
----------------------------------------+-----------------------------------
Reporter: brandon | Owner: nobody
Status: closed | Milestone: 1.2
Component: Testing framework | Version: 1.1
Resolution: wontfix | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Changes (by jacob):
* status: new => closed
* resolution: => wontfix
Comment:
To my eyes, `TransactionTestCase` does exactly what
[http://docs.djangoproject.com/en/1.1/topics/testing/#django.test.TransactionTestCase
the documentation] says it does: force you to handle transactions
yourself. This means that you need to do the commit/rollback handling
yourself.
Remember you can always easily writing your own `TestCase` (or
`TransactionTestCase` subclass to handle this stuff however your app
wants. Django provides two common options; less common ones can -- and
should -- be confined to your own projects.
[Yes, `TransactionTestCase` could have been named better. Water under the
bridge now, though.]
--
Ticket URL: <http://code.djangoproject.com/ticket/12087#comment:4>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
