#31612: Running tests with --keepdb messy to flush.
-----------------------------------+--------------------------------------
Reporter: Jarek Glowacki | Owner: nobody
Type: New feature | Status: closed
Component: Testing framework | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: test keepdb | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Comment (by tinodb):
I must say I run into the same cases Jarek above runs into, which are
mainly around migrations. Either when creating them, or when switching
branches. I'm not so sure that is a very weird workflow for a larger team
working on a Django project?
I would say a `--createdb` (or `--recreatedb`) flag (which would drop the
db(s) upfront, without asking for input) would be very complementary to
`--keepdb` and I miss it quite often. (I usually check new Django release
to see if it has been added by chance :).
pytest-django has this as well: https://pytest-
django.readthedocs.io/en/latest/database.html#create-db-force-re-creation-
of-the-test-database.
--
Ticket URL: <https://code.djangoproject.com/ticket/31612#comment:3>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070190158ec2b2-b8022d3a-21bf-4550-9fe4-29e17cb35fd7-000000%40eu-central-1.amazonses.com.
