#33184: Allow a way to create a new test database AND keep it for the next test
run
------------------------------------+--------------------------------------
Reporter: Valentijn Scholten | Owner: nobody
Type: New feature | Status: closed
Component: Testing framework | Version: 3.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
> I am running multiple test suites serially. ...
Assuming I've understood correctly, I think Mateusz's is right.
* Use `--keepdb` for all runs, which should create the DB on the first
pass.
* Run `dropdb` (Postgres) or `rm` (Sqlite) or equivalent, after the last
run.
For the `dropdb` step, I don't think that replicating existing tools
inside `django-admin` is going to be worth it.
--
Ticket URL: <https://code.djangoproject.com/ticket/33184#comment:2>
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/075.689e2003eeabd0b93cb5f62c267edb40%40djangoproject.com.
