Nose没有找到Django测试

时间:2022-10-23 20:27:21

I am trying to use Django-nose in my current project, but I can't figure out how to get nose to run my tests. So I started a simple Django 1.4.1 project to get to know nose. But not even on this simple test project I could get it running.

我正在尝试在我现在的项目中使用Django-nose,但是我不知道如何让nose运行我的测试。因此,我启动了一个简单的Django 1.4.1项目来了解nose。但即使在这个简单的测试项目上,我也无法让它运行。

Before I go on: I know there are a ton of similar questions on *, like for instance this one:

在我继续之前:我知道关于*有很多类似的问题,比如这个:

How do I tell Django-nose where my tests are?

我如何告诉Django-nose我的测试在哪里?

But after Googling around, reading blog posts and * answers I still couldn't get it running.

但在谷歌上搜索、阅读博客文章和堆叠答案之后,我仍然无法让它运行。

How I set up my test project

  1. Create virtual environment.
  2. 创建虚拟环境。
  3. pip install django django-nose nose.
  4. 安装django django-nose。
  5. Create project with django-admin.py startproject djangonosetest.
  6. 用django-admin创建项目。py startproject djangonosetest。
  7. Create an app manage.py startapp testapp
  8. 创建一个应用程序管理。py startapp testapp
  9. Edit settings.py:

    编辑settings.py:

    • Set ENGINE to django.db.backends.sqlite3
    • 设置引擎django.db.backends.sqlite3
    • Added django_nose, testapp to INSTALLED_APPS
    • 添加django_nose, testapp到INSTALLED_APPS。
    • Added TEST_RUNNER = 'django_nose.NoseTestSuiteRunner'.
    • 添加TEST_RUNNER =“django_nose.NoseTestSuiteRunner”。
  10. Run manage.py test

    运行管理。py测试

But all I got was this output:

但我得到的是这个输出:

nosetests --verbosity 1
Creating test database for alias 'default'...

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
Destroying test database for alias 'default'...

But at least the default test case should have been run.

但是至少应该运行默认的测试用例。

When I run python manage.py test djangonosetest.testapp.tests:SimpleTest it'll run the test. But that seems a bit overkill if I had to do it for every test file I have. But it proves that the tests can be run.

当我运行python管理时。py djangonosetest.testapp测试。测试:SimpleTest将运行测试。但是如果我必须对我拥有的每个测试文件都这样做的话,这似乎有点过分了。但它证明了测试可以运行。

When I ran manage.py test -v 3 (high verbosity level) this showed up:

当我运行管理。py测试- v3(高冗余度级)显示:

nose.selector: INFO: /Users/Jens/Projects/Django/djangonosetest/djangonosetest/settings.py is executable; skipped
nose.selector: INFO: /Users/Jens/Projects/Django/djangonosetest/djangonosetest/settings.pyc is executable; skipped
nose.selector: INFO: /Users/Jens/Projects/Django/djangonosetest/djangonosetest/urls.py is executable; skipped
nose.selector: INFO: /Users/Jens/Projects/Django/djangonosetest/djangonosetest/wsgi.py is executable; skipped
nose.selector: INFO: /Users/Jens/Projects/Django/djangonosetest/djangonosetest/testapp/models.py is executable; skipped
nose.selector: INFO: /Users/Jens/Projects/Django/djangonosetest/djangonosetest/testapp/models.pyc is executable; skipped
nose.selector: INFO: /Users/Jens/Projects/Django/djangonosetest/djangonosetest/testapp/views.py is executable; skipped
nose.selector: INFO: /Users/Jens/Projects/Django/djangonosetest/djangonosetest/testapp/tests.py is executable; skipped
nose.selector: INFO: /Users/Jens/Projects/Django/djangonosetest/djangonosetest/testapp/tests.pyc is executable; skipped
nose.selector: INFO: /Users/Jens/Projects/Django/djangonosetest/manage.py is executable; skipped

The nose does definitely find my tests.py but is skipping it for some reason.

我的鼻子确实找到了我的测试。但是因为某种原因,他跳过了。

Folder structure

djangonosetest/
    djangonosetest/
        __init__.py
        settings.py
        testapp/
            __init__.py
            models.py
            tests.py
            views.py
        urls.py
        wsgi.py
    manage.py

settings.py

DEBUG = True
TEMPLATE_DEBUG = DEBUG

ADMINS = (
    # ('Your Name', 'your_email@example.com'),
)

MANAGERS = ADMINS

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.sqlite3', # Add 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'.
        'NAME': '',                      # Or path to database file if using sqlite3.
        'USER': '',                      # Not used with sqlite3.
        'PASSWORD': '',                  # Not used with sqlite3.
        'HOST': '',                      # Set to empty string for localhost. Not used with sqlite3.
        'PORT': '',                      # Set to empty string for default. Not used with sqlite3.
    }
}

# Local time zone for this installation. Choices can be found here:
# http://en.wikipedia.org/wiki/List_of_tz_zones_by_name
# although not all choices may be available on all operating systems.
# In a Windows environment this must be set to your system time zone.
TIME_ZONE = 'America/Chicago'

# Language code for this installation. All choices can be found here:
# http://www.i18nguy.com/unicode/language-identifiers.html
LANGUAGE_CODE = 'en-us'

SITE_ID = 1

# If you set this to False, Django will make some optimizations so as not
# to load the internationalization machinery.
USE_I18N = True

# If you set this to False, Django will not format dates, numbers and
# calendars according to the current locale.
USE_L10N = True

# If you set this to False, Django will not use timezone-aware datetimes.
USE_TZ = True

# Absolute filesystem path to the directory that will hold user-uploaded files.
# Example: "/home/media/media.lawrence.com/media/"
MEDIA_ROOT = ''

# URL that handles the media served from MEDIA_ROOT. Make sure to use a
# trailing slash.
# Examples: "http://media.lawrence.com/media/", "http://example.com/media/"
MEDIA_URL = ''

# Absolute path to the directory static files should be collected too.
# Don't put anything in this directory yourself; store your static files
# in apps' "static/" subdirectories and in STATICFILES_DIRS.
# Example: "/home/media/media.lawrence.com/static/"
STATIC_ROOT = ''

# URL prefix for static files.
# Example: "http://media.lawrence.com/static/"
STATIC_URL = '/static/'

# Additional locations of static files
STATICFILES_DIRS = (
    # Put strings here, like "/home/html/static" or "C:/www/django/static".
    # Always use forward slashes, even on Windows.
    # Don't forget to use absolute paths, not relative paths.
)

# List of finder classes that know how to find static files in
# various locations.
STATICFILES_FINDERS = (
    'django.contrib.staticfiles.finders.FileSystemFinder',
    'django.contrib.staticfiles.finders.AppDirectoriesFinder',
#    'django.contrib.staticfiles.finders.DefaultStorageFinder',
)

# Make this unique and don't share it with anybody.
SECRET_KEY = 'ikh^t)49eincyww4@nq(o)go_129zdr87*im00m^+h@_n!w4ec'

# List of callables that know how to import templates from various sources.
TEMPLATE_LOADERS = (
    'django.template.loaders.filesystem.Loader',
    'django.template.loaders.app_directories.Loader',
#     'django.template.loaders.eggs.Loader',
)

MIDDLEWARE_CLASSES = (
    'django.middleware.common.CommonMiddleware',
    'django.contrib.sessions.middleware.SessionMiddleware',
    'django.middleware.csrf.CsrfViewMiddleware',
    'django.contrib.auth.middleware.AuthenticationMiddleware',
    'django.contrib.messages.middleware.MessageMiddleware',
    # Uncomment the next line for simple clickjacking protection:
    # 'django.middleware.clickjacking.XFrameOptionsMiddleware',
)

ROOT_URLCONF = 'djangonosetest.urls'

# Python dotted path to the WSGI application used by Django's runserver.
WSGI_APPLICATION = 'djangonosetest.wsgi.application'

TEMPLATE_DIRS = (
    # Put strings here, like "/home/html/django_templates" or "C:/www/django/templates".
    # Always use forward slashes, even on Windows.
    # Don't forget to use absolute paths, not relative paths.
)

INSTALLED_APPS = (
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    'django.contrib.sites',
    'django.contrib.messages',
    'django.contrib.staticfiles',
    # Uncomment the next line to enable the admin:
    # 'django.contrib.admin',
    # Uncomment the next line to enable admin documentation:
    # 'django.contrib.admindocs',
    'django_nose',
    'djangonosetest.testapp',
)

# A sample logging configuration. The only tangible logging
# performed by this configuration is to send an email to
# the site admins on every HTTP 500 error when DEBUG=False.
# See http://docs.djangoproject.com/en/dev/topics/logging for
# more details on how to customize your logging configuration.
LOGGING = {
    'version': 1,
    'disable_existing_loggers': False,
    'filters': {
        'require_debug_false': {
            '()': 'django.utils.log.RequireDebugFalse'
        }
    },
    'handlers': {
        'mail_admins': {
            'level': 'ERROR',
            'filters': ['require_debug_false'],
            'class': 'django.utils.log.AdminEmailHandler'
        }
    },
    'loggers': {
        'django.request': {
            'handlers': ['mail_admins'],
            'level': 'ERROR',
            'propagate': True,
        },
    }
}

TEST_RUNNER = 'django_nose.NoseTestSuiteRunner'

The test code

The test code is the default TestCase Django creates.

测试代码是Django创建的默认TestCase。

"""
This file demonstrates writing tests using the unit test module. These will pass
when you run "manage.py test".

Replace this with more appropriate tests for your application.
"""

from Django.test import TestCase


class SimpleTest(TestCase):
    def test_basic_addition(self):
        """
        Tests that 1 + 1 always equals 2.
        """
        self.assertEqual(1 + 1, 2)

So how do I tell Django-nose/nose where my tests are?

那么我该如何告诉Django-nose/nose我的测试呢?

UPDATE

If found an interesting Google Groups post and * answer on the subject:

如果发现了一个有趣的谷歌组post和*答案:

Both boil down to the fact that nose will skip executable files. That's why I get tests.py is executable; skipped. Problem is that the file is not executable:

两者都归结为鼻子会跳过可执行文件的事实。这就是为什么我要参加考试。py是可执行;跳过。问题是该文件不可执行:

----------+ 1 Jens  staff  383 13 Okt 00:01 tests.py

I also tried it with u-x, g-x and o-x but nose skipped anyway. I get the feeling that this is a bug. The file is found in the nose, is not executable but still skipped.

我也尝试了u-x, g-x和o-x,但还是跳过了鼻子。我觉得这是一个bug。在鼻子中找到的文件,不是可执行的,但仍然被跳过。

A workaround is to use the --exe switch. Running manage.py test --exe runs the test. While it's better than the other workarounds I am not completely happy with that solution.

一个变通方法是使用-exe开关。运行管理。py测试——exe运行测试。虽然它比其他解决方案要好,但我对这个解决方案并不完全满意。

2 个解决方案

#1


2  

I had the same issue today and I fixed it.

我今天也有同样的问题,我解决了。

Try:

试一试:

chmod a-x djangonosetest/djangonosetest/testapp/*.py

#2


1  

I think it might be that in Django 1.4 you need to specify the project in installed apps if you don't specify a project root. Instead of just 'testapp', try 'djangonosetest.testapp'

我认为在Django 1.4中,如果不指定项目根,您可能需要在已安装的应用程序中指定项目。不只是'testapp',试试'djangonosetest.testapp'

https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-INSTALLED_APPS see their example.

https://docs.djangoproject.com/en/dev/ref/settings/ std:setting-INSTALLED_APPS看到他们的例子。

#1


2  

I had the same issue today and I fixed it.

我今天也有同样的问题,我解决了。

Try:

试一试:

chmod a-x djangonosetest/djangonosetest/testapp/*.py

#2


1  

I think it might be that in Django 1.4 you need to specify the project in installed apps if you don't specify a project root. Instead of just 'testapp', try 'djangonosetest.testapp'

我认为在Django 1.4中,如果不指定项目根,您可能需要在已安装的应用程序中指定项目。不只是'testapp',试试'djangonosetest.testapp'

https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-INSTALLED_APPS see their example.

https://docs.djangoproject.com/en/dev/ref/settings/ std:setting-INSTALLED_APPS看到他们的例子。