AttributeError: 'module' object has no attribute 'tests'

Question

I'm running this command:

python manage.py test project.apps.app1.tests

and it causes this error:

AttributeError: 'module' object has no attribute 'tests'

Below is my directory structure. I've also added app1 to my installed apps config.

Traceback (most recent call last):
    File "manage.py", line 10, in <module> execute_from_command_line(sys.argv)
    File "/home/username/local/dev/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 385, in execute_from_command_line
    utility.execute()
    File "/home/username/local/dev/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 377, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
    File "/home/username/local/dev/local/lib/python2.7/site-packages/django/core/management/commands/test.py", line 50, in run_from_argv
    super(Command, self).run_from_argv(argv)
    File "/home/username/local/dev/local/lib/python2.7/site-packages/django/core/management/base.py", line 288, in run_from_argv
    self.execute(*args, **options.__dict__)
    File "/home/username/local/dev/local/lib/python2.7/site-packages/django/core/management/commands/test.py", line 71, in execute
    super(Command, self).execute(*args, **options)
    File "/home/username/local/dev/local/lib/python2.7/site-packages/django/core/management/base.py", line 338, in execute
    output = self.handle(*args, **options)
    File "/home/username/local/dev/local/lib/python2.7/site-packages/django/core/management/commands/test.py", line 88, in handle
    failures = test_runner.run_tests(test_labels)
    File "/home/username/local/dev/local/lib/python2.7/site-packages/django/test/runner.py", line 146, in run_tests
    suite = self.build_suite(test_labels, extra_tests)
    File "/home/username/local/dev/local/lib/python2.7/site-packages/django/test/runner.py", line 66, in build_suite
    tests = self.test_loader.loadTestsFromName(label)
    File "/usr/lib/python2.7/unittest/loader.py", line 100, in loadTestsFromName
    parent, obj = obj, getattr(obj, part)
    AttributeError: 'module' object has no attribute 'tests'

Directory structure:

enter image description here

Eric Leschinski · Accepted Answer · 2015-09-07 02:24:41Z

198

I finally figured it out working on another problem. The problem was that my test couldn't find an import.

It looks like you get the above error if your test fails to import. This makes sense because the test suite can't import a broken test. At least I think this is what is going on because I fixed the import within my test file and sure enough it started working.

To validate your test case just try import the test case file in python console.

Example:

from project.apps.app1.tests import *

edited Sep 7, 2015 at 2:24

Eric Leschinski

155k96 gold badges423 silver badges337 bronze badges

answered Aug 29, 2014 at 20:22

Chris

5,0939 gold badges40 silver badges58 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

AdamC Over a year ago

Bad assumption in that message.

Hakan B. Over a year ago

This can also be done from the command line, eliminating the need to open a Python shell: python -c "from project.apps.app1.tests import *"

Peter M. - stands for Monica Over a year ago

+1 saved me from confusing error message. The only problem with your suggestion is that you imported death star . OK in console for experiments, but in code, always import just the names needed.

MikeyE Over a year ago

Instead of fearing use of the "death star" can't you juse use the __all__ variable in each file? And specify a list of class names, functions, and variables to export when using from package_name.module import *? I've had good luck with this pattern. I understand it takes a bit more time to write up the __all__ bit at the top of each file. But importing using "death star" seems to work nicely.

rfportilla Over a year ago

I just had this issue and was really confused. Thanks for the answer. Python is not doing the right thing here. It needs a clearer message. That being said, I assume your "...import *" is just to check the tests, not meant to be part of the test runner... I think the latter would be inappropriate.

|

Steve Bradshaw · Accepted Answer · 2015-03-30 13:34:40Z

39

Use:

./manage.py shell

followed by

import myapp.tests

to find the nature of the import error.

answered Mar 30, 2015 at 13:34

Steve Bradshaw

8177 silver badges11 bronze badges

1 Comment

MikeyE Over a year ago

I appreciate the effort, and it seems like this worked for many people. But, when I opened a python interactive shell using ./manage.py shell then did either import myapp.tests or from myapp.tests import * both worked without error. But, I still get the error described by the OP.

tmin · Accepted Answer · 2016-05-03 19:07:55Z

24

For my case, I need to create an empty __init__.py in my app/tests folder

answered May 3, 2016 at 19:07

tmin

1,32313 silver badges15 bronze badges

Comments

lukeaus · Accepted Answer · 2015-05-10 06:30:23Z

6

Steve Bradshaw's example above works for import errors (thanks Steve).

Other type of errors (e.g. ValueError) may also cause

AttributeError: 'module' object has no attribute 'tests'

to see what these errors are

./manage.py shell
from myapp.tests import SomeTestCase
t = SomeTestCase()

edited May 10, 2015 at 6:30

answered Apr 25, 2015 at 2:17

lukeaus

12.3k8 gold badges54 silver badges61 bronze badges

Comments

Doug Murphy · Accepted Answer · 2014-09-25 19:26:07Z

5

I had the same error as Chris. I had deleted an old model, then run tests.py, but another file (views.py) was still trying to import the deleted model.

When I took out the now-obsolete import statement, problem solved.

answered Sep 25, 2014 at 19:26

Doug Murphy

4831 gold badge5 silver badges9 bronze badges

Comments

Lukasz Dynowski · Accepted Answer · 2017-01-09 10:03:41Z

3

Make sure that all modules that you are using in your script are not broken. By this I mean check spelling in your import statements.

# invalid import
from app.model.notification import Notification
# valid import
from app.models.notification import Notification

You can test yours modules by executing imports statements in djano's interactive console.

$root@13faefes8: python manage.py shell
Type "help", "copyright", "credits" or "license" for more information (InteractiveConsole)
>>> from app.model.notification import Notification
Traceback (most recent call last): 
   File "<console>", line 1, in <module>
ImportError: No module named model.notification

answered Jan 9, 2017 at 10:03

Lukasz Dynowski

14k14 gold badges99 silver badges149 bronze badges

Comments

rudyt · Accepted Answer · 2018-09-29 00:22:26Z

2

I resolved the error "AttributeError: module 'utils' has no attribute 'name_of_my_function' " by fixing a circular import reference. My files manage.py and utils.py each had an import statement pointing at each other.

answered Sep 29, 2018 at 0:22

rudyt

213 bronze badges

Comments

Davide Andrea · Accepted Answer · 2019-02-28 19:01:06Z

2

I had the same error. It turned out to be because I named my module common.py, yet there already was some other common.py module. All I had to do was to rename my module.

answered Feb 28, 2019 at 19:01

Davide Andrea

1,4252 gold badges19 silver badges44 bronze badges

Comments

Kasravnd · Accepted Answer · 2014-08-29 19:56:09Z

1

According to django document When you run your tests, the default behavior of the test utility is to find all the test cases (that is, subclasses of unittest.TestCase) in any file whose name begins with test, automatically build a test suite out of those test cases, and run that suite.

so try this : python manage.py test tests.py

edited Aug 29, 2014 at 19:56

answered Aug 29, 2014 at 19:49

Kasravnd

108k19 gold badges167 silver badges195 bronze badges

Comments

Petter Friberg · Accepted Answer · 2016-10-03 08:09:49Z

1

Got the same error, but checked all the reasons list here, did not fix my problem.

Finally figure it out that, the reason is that the name of one method that imported but not used yet is not correct. Though it is a stupid error, it happens.

edited Oct 3, 2016 at 8:09

Petter Friberg

21.8k10 gold badges67 silver badges116 bronze badges

answered Oct 3, 2016 at 8:07

zhihong

1,9662 gold badges25 silver badges35 bronze badges

Comments

dpsahoo · Accepted Answer · 2019-11-09 07:54:49Z

0

I had a similar error while writing a unittest.TestCase. When I re-typed the same method definition as-is, it seemed to work !

The only change I noticed on PyCharm was the 'override' icon pop-up the 2nd time, as the setup(self) method needs to override the original method defined in TestCase.

answered Nov 9, 2019 at 7:54

dpsahoo

277 bronze badges

Comments

bobdilan · Accepted Answer · 2021-11-04 07:54:38Z

0

My solution was just renaming my module.

answered Nov 4, 2021 at 7:54

bobdilan

216 bronze badges

2 Comments

Community Over a year ago

As it’s currently written, your answer is unclear. Please edit to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center.

Eric Aya Over a year ago

You mean like in this answer?

Collectives™ on Stack Overflow

AttributeError: 'module' object has no attribute 'tests'

12 Answers 12

7 Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

12 Answers 12

7 Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related