Hi again,
On Monday 25 January 2016 18:33:15 charettes wrote:
> FWIW I've been working around this limitation by adding a suffix
> to my `DATABASES['alias']['TEST']['NAME']` setting if the project
> VCS branch is not the default one.
>
What Marc said. That's nice, but doesn't solve my problem.
Simon - that's great but still means ending up having to create a new test
DB every time you switch to a new branch, something you do a lot if you're
part of the QA process!
+100 to this feature, it would be super useful for me, especially when
working with long running feature branches with migra
FWIW I've been working around this limitation by adding a suffix
to my `DATABASES['alias']['TEST']['NAME']` setting if the project
VCS branch is not the default one.
e.g. for Git
import subprocess
branch = subprocess.check_output(['git', 'rev-parse', '--abbrev-ref',
'HEAD']).strip()
if branch
I've made similar mistakes (corrupting the test database) while working on
djangoproject.com. For that project, test database creation is quick enough
that I just drop "--keepdb" and start fresh. I think this will usually be
the simplest option for most users, but I don't see a reason not to sup
Hi,
While developing against a large project with many migrations, I found 1.8's
--keepdb option to the test command a life-saver, changing the time to run the
projects test from 7-8 minutes to under one (not even counting the tests
themselves). But it is still missing something.
If I develop
