#25251: Inconsistent availability of data from migrations in TestCases when
using
--keepdb
-------------------------------------+-------------------------------------
Reporter: David Szotten | Owner: Nathan
| Florea
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: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Nathan Florea):
* needs_docs: 1 => 0
* needs_tests: 1 => 0
* owner: David Sanders => Nathan Florea
Comment:
Sorry, I accidentally solved this in
[https://github.com/django/django/pull/19648 PR]. I don't modify
{{{TransactionTestCase}}}, though, so there's probably some other
interesting work to do there. And I didn't technically fix
{{{--keepdb}}}; I created a new flag, {{{--use-clones}}}, that only runs
tests against clones of the test database. But it does provide an
alternative to {{{--keepdb}}} that will always run tests against a fresh
copy of the test database, ensuring that no matter what happens during
testing or after, it will have no impact on subsequent test runs. We'll
see if it gets accepted.
--
Ticket URL: <https://code.djangoproject.com/ticket/25251#comment:47>
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070198176b94fb-b375a62e-b5f0-4a4a-8fc0-71f1136fdf5f-000000%40eu-central-1.amazonses.com.
