#25251: Inconsistent availability of data migrations in TransactionTestCase when using --keepdb -----------------------------------+------------------------------------ Reporter: davidszotten | Owner: nobody Type: Bug | Status: new Component: Testing framework | Version: 1.8 Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -----------------------------------+------------------------------------
Comment (by timgraham): I think `keepdb` isn't an important part of testing this (it doesn't really have any tests). Instead you could use an approach similar to what's done in `tests/test_utils/test_transactiontestcase.py` where you invoke `TransactionTestCase`'s methods within a test and check the availability of the data. -- Ticket URL: <https://code.djangoproject.com/ticket/25251#comment:7> 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.8d1087955e4af7cc4a2fae06f81e0843%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.