#31612: Running tests with --keepdb messy to flush.
-----------------------------------+--------------------------------------
Reporter: Jarek Glowacki | Owner: nobody
Type: New feature | Status: closed
Component: Testing framework | Version: master
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
-----------------------------------+--------------------------------------
Changes (by felixxm):
* status: new => closed
* type: Uncategorized => New feature
* version: 3.0 => master
* resolution: => wontfix
Comment:
I don't agree that `--keepdb` is clunky it works as intended.
> If there are changes that require dropping the test database.
I think that's something unusual. Everything will work without an extra
roundtrip if you'll control these changes with migrations and without
dropping the test database. So I would say that an issue is in your
workflow rather than in Django itself. Running tests wasn't designed to
drop a test database when something terrible happens. You use mix of
`--keepdb` on/off calls to do this, but it's not a "supported" flow.
> Finally, changing behaviour on --keepdb so that it somehow _knows_ when
to prompt to start from scratch when it feels there is something not
lining up in the migrations could be another way to go. Solution would be
very magic, and maybe not great at guessing when to prompt, but would save
the user from having to learn any of the other proposed options.
I think you've already answered that it's not feasible by using words like
`it somehow _knows_ ` and `very magic`.
--
Ticket URL: <https://code.djangoproject.com/ticket/31612#comment:1>
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/065.1af7aaf2ab3cf2ebe0dd7c30a6d277dd%40djangoproject.com.
