#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

Comment (by Jarek Glowacki):

 Sorry, I should've provided some examples for when dropping the test db
 might be necessary:
 - Doctoring an existing migration on a local branch. eg. I run tests on a
 local branch, applying a migration i've just added. I notice the migration
 is wrong and wish to change it before pushing it upstream. Running the
 tests again won't pick up my change. And to my knowledge I can't just
 unapply the migration like i can with the `migrate` mcommand.
 - Rebasing migrations. eg. I've got a stale PR with a migration on it. I
 rebase my work and rename the migration and its dependencies to sit at the
 end of the list. Local test db still thinks I've already applied said
 changes and falls over trying to apply them a second time. (Yes I could
 just add a merge migration here, but it's unnecessary clutter if the
 migration exists only on my PR. And i don't think faking migrations is
 possible here, like it is with `migrate`.)

 Are such workflows out of the ordinary?

 Anyway, if this still isn't sufficiently convincing, won't argue further.
 Will just add some custom code to do it in our own product I guess..

 Thanks for the quick triage!

Ticket URL: <https://code.djangoproject.com/ticket/31612#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to