Re: Disabling migrations when running tests

> > BTW: Would you consider bringing back patch > https://github.com/django/django/commit/157d7f1f1de4705daddebb77f21bd7097a74513d > > ? This patch is what I've asking for months. > > Marcin > Yes -- that patch didn't work properly as noted on the ticket. We'll certainly include a working

Re: Disabling migrations when running tests

Please ignore this! My apologies - I read "fixtures" instead of "migrations". On Sunday, 17 July 2016 15:13:05 UTC+2, Derek wrote: > > I use a small "hack" which Works For Me :) > > I use a shell script to run the tests (call it, for example, `tester.sh`) > :- > > mv myapp/fixtures

Re: Disabling migrations when running tests

I use a small "hack" which Works For Me :) I use a shell script to run the tests (call it, for example, `tester.sh`) :- mv myapp/fixtures myapp/_fixtures python manage.py test --traverse-namespace tests --settings=test_settings mv myapp/_fixtures myapp/fixtures So; basically rename the fixtures

Re: Disabling migrations when running tests

On Sunday, July 17, 2016 at 3:08:49 AM UTC+2, Tim Graham wrote: > > You can use MIGRATION_MODULES for this: > https://docs.djangoproject.com/en/1.9/ref/settings/#migration-modules > > Also, there's a ticket to simplify disabling of migrations during tests > further:

Re: Disabling migrations when running tests

You can use MIGRATION_MODULES for this: https://docs.djangoproject.com/en/1.9/ref/settings/#migration-modules Also, there's a ticket to simplify disabling of migrations during tests further: https://code.djangoproject.com/ticket/25388 On Saturday, July 16, 2016 at 6:44:26 PM UTC-4,

Re: Disabling migrations when running tests

On Sunday, July 17, 2016 at 12:20:30 AM UTC+2, James Schneider wrote: > > > > > I don't need automatically created test databases nor migrations > applied. Can I disable this? > > > > I don't know of a way to do so. You're probably better off using a > separate test suite than relying on

Re: Disabling migrations when running tests

try this library: https://github.com/henriquebastos/django-test-without-migrations/ On Sat, Jul 16, 2016 at 7:20 PM, James Schneider wrote: > >> > >> Could you explain what you mean by running tests? > > > > > > Yes. I'm talking about "manage.py test". > > > > The

Re: Disabling migrations when running tests

>> >> Could you explain what you mean by running tests? > > > Yes. I'm talking about "manage.py test". > > The docs says: > "New in Django 1.8 [...] If the database does not exist, it will first be created. Any migrations will also be applied in order to keep it up to date." > > Source:

Re: Disabling migrations when running tests

On Saturday, July 16, 2016 at 11:57:18 PM UTC+2, Ryan Castner wrote: > > Could you explain what you mean by running tests? > Yes. I'm talking about "manage.py test". The docs says: "New in Django 1.8 [...] If the database does not exist, it will first be created. *Any migrations will also be

Re: Disabling migrations when running tests

Could you explain what you mean by running tests? Migrations are executed when you run `./manage.py migrate`, if you are running `./manage.py test ...` it shouldn't be running your migrations, probably just gives a log warning that you have unapplied migrations. Here are the django docs on

Disabling migrations when running tests

Hi all. Is possible to disable migrations execution when running tests? Thanks, Marcin -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to