And the answer turned out to be... we were/are using a multidb setup, which
silently prevents the test suite from creating a test db. Setting
DATABASE_ROUTERS
= [] re-enabled the test db creation. Sigh. It's always the little things.
--
You received this message because you are subscribed to t
My bad...missed the version in original question.
You are right.
On Tue, Aug 30, 2016 at 4:59 PM, Andromeda Yelton <
andromeda.yel...@gmail.com> wrote:
> What are do the relevant parts of your settings file say? In particular,
> https://docs.djangoproject.com/en/1.7/topics/testing/overview/#the-
What are do the relevant parts of your settings file say? In particular,
https://docs.djangoproject.com/en/1.7/topics/testing/overview/#the-test-database
says "If you want to use a different database name, specify NAME in the
TEST dictionary for any given database in DATABASES." - I would check the
Try this:
python manage.py test --keepdb
On Mon, Aug 29, 2016 at 3:26 PM, Adam Hirsch
wrote:
> I've been handed a fairly large and built-up django 1.7.9 installation
> with several dozen pre-existing in-house modules and a lot of history.
>
> For some reason, any attempt to * manage.py test *
I've been handed a fairly large and built-up django 1.7.9 installation with
several dozen pre-existing in-house modules and a lot of history.
For some reason, any attempt to * manage.py test * any of the existing
modules runs tests against the live database specified in *DATABASES['default']
*
5 matches
Mail list logo