R – import twice when run test

djangoimporttesting

i have this code in my tests.py:

from models import *

and in the models.py I have a signal handler and register it with

post_save.connect( post_save_note, sender=Note )

and when i run test with ./manage.py test main

I found the signal handler was registered twice and executed twice,
and I found it's because the models was imported twice.

can't i put from models import * in the test code?
what should i do?

Best Answer

You need to make sure your models are always imported the same way.

So for example, if you have in example1/tests.py:

from models import *

and in another package example2/views.py:

from example1.models import ModelA

then you'll have the problem you are experiencing. The solution is to be consistent and use only one or the other.

Related Solutions

How to call a custom Django manage.py command directly from a test driver

The best way to test such things - extract needed functionality from command itself to standalone function or class. It helps to abstract from "command execution stuff" and write test without additional requirements.

But if you by some reason cannot decouple logic form command you can call it from any code using call_command method like this:

from django.core.management import call_command

call_command('my_command', 'foo', bar='baz')

Python – django – circular import problem when executing a command

Is there any particular reason you need to store SITE_DOMAIN and SITE_NAME in globals.py? These are already available directly from the sites framework.

According to the docs, the site object is cached the first time you access it, so importing it and using it there directly doesn't hurt.

Best Answer

Related Solutions

How to call a custom Django manage.py command directly from a test driver

Python – django – circular import problem when executing a command

Related Topic