#25251: Inconsistent availability of data migrations in TransactionTestCase when
using --keepdb
-------------------------------------+-------------------------------------
     Reporter:  David Szotten        |                    Owner:  Romain
                                     |  Garrigues
         Type:  Bug                  |                   Status:  assigned
    Component:  Testing framework    |                  Version:  1.8
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Romain Garrigues):

 * owner:  nobody => Romain Garrigues
 * status:  new => assigned


Comment:

 I updated the MR according to my discussion with @aaugustin.
 It impacted the `DiscoverRunner` explicit test ordering. I didn't want to
 update the current tests to ensure backward-compatibility, I created new
 ones for `TransactionTestCase` tests ordering.

--
Ticket URL: <https://code.djangoproject.com/ticket/25251#comment:25>
Django <https://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 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/070.948edf412dceb2084a5a641003dd9c79%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to