Re: [Django] #12087: Django "TransactionTestCase" isn't

[Django]

#12087: Django "TransactionTestCase" isn't
---+
 Reporter:  brandon|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Testing framework  |  Version:  1.1
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Thomas Hauk):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 The name `TransactionTestCase` was definitely a mistake and it should have
 been changed ages ago. Very confusing to have a class named after
 something which it ''definitely'' doesn't do! Maybe it should be renamed
 `DefinitelyNotInATransactionTestCase` as a breaking change in the next
 major release...

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.b8f56abaae5b15710baa3ab9e107375e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12087: Django "TransactionTestCase" isn't

[Django]

#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: 
Django 
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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12087: Django "TransactionTestCase" isn't

[Django]

#12087: Django "TransactionTestCase" isn't
+---
  Reporter:  brandon| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Testing framework  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  1 
Needs_better_patch:  0  |  
+---
Comment (by ericholscher):

 It would be useful to have a test case showing this behavior in action.
 The fix sounds simple enough.

-- 
Ticket URL: 
Django 
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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12087: Django "TransactionTestCase" isn't

[Django]

#12087: Django "TransactionTestCase" isn't
+---
  Reporter:  brandon| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Testing framework  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  1 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted
  * component:  Database layer (models, ORM) => Testing framework
  * needs_tests:  0 => 1
  * milestone:  => 1.2

-- 
Ticket URL: 
Django 
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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12087: Django "TransactionTestCase" isn't

[Django]

#12087: Django "TransactionTestCase" isn't
---+
  Reporter:  brandon   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jonathan):

 * cc: jonathan+dja...@harrycow.fr (added)
  * needs_better_patch:  => 0
  * component:  Testing framework => Database layer (models, ORM)
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 This ticket is related to: #10813, #12028.

 Need global fix ?

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---