【问题标题】:Duplicate key error running tests with django-nose but not with Django's DiscoverRunner使用 django-nose 但不是使用 Django 的 DiscoverRunner 运行测试时出现重复的关键错误
【发布时间】:2019-08-06 16:16:42
【问题描述】:

当我使用默认的 Django 测试运行程序 (django.test.runner.DiscoverRunner) 运行测试时,一切正常。当我使用nose(用于XML 输出)运行它们时,我从不属于我的测试中得到IntegrityErrors。

Override this method to return an instance of your custom user model ... ERROR

我不知道这是什么,也不知道为什么它只由 django-nose 测试运行程序运行。

这是错误的完整堆栈跟踪

======================================================================
ERROR: Override this method to return an instance of your custom user model
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "auth_user_username_key"
DETAIL:  Key (username)=(test@email.com) already exists.


The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/wagtail/tests/utils/wagtail_tests.py", line 24, in create_test_user
    return user_model.objects.create_superuser(**user_data)
  File "/usr/local/lib/python3.7/site-packages/django/contrib/auth/models.py", line 162, in create_superuser
    return self._create_user(username, email, password, **extra_fields)
  File "/usr/local/lib/python3.7/site-packages/django/contrib/auth/models.py", line 145, in _create_user
    user.save(using=self._db)
  File "/usr/local/lib/python3.7/site-packages/django/contrib/auth/base_user.py", line 66, in save
    super().save(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/django/db/models/base.py", line 741, in save
    force_update=force_update, update_fields=update_fields)
  File "/usr/local/lib/python3.7/site-packages/django/db/models/base.py", line 779, in save_base
    force_update, using, update_fields,
  File "/usr/local/lib/python3.7/site-packages/django/db/models/base.py", line 870, in _save_table
    result = self._do_insert(cls._base_manager, using, fields, update_pk, raw)
  File "/usr/local/lib/python3.7/site-packages/django/db/models/base.py", line 908, in _do_insert
    using=using, raw=raw)
  File "/usr/local/lib/python3.7/site-packages/django/db/models/manager.py", line 82, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 1186, in _insert
    return query.get_compiler(using=using).execute_sql(return_id)
  File "/usr/local/lib/python3.7/site-packages/django/db/models/sql/compiler.py", line 1335, in execute_sql
    cursor.execute(sql, params)
  File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 67, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 89, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.IntegrityError: duplicate key value violates unique constraint "auth_user_username_key"
DETAIL:  Key (username)=(test@email.com) already exists.

在我的测试中,我没有创建一个电子邮件地址为“test@email.com”的测试用户,而且我在这个堆栈跟踪中的任何地方都看不到我的任何代码,所以我不知道它来自哪里或为什么它只在我使用 django-nose 运行测试时出现。

【问题讨论】:

    标签: python wagtail nose django-nose


    【解决方案1】:

    我认为 django-nose 在查找测试方面非常激进。我的一个测试套件使用了WagtailPageTests,它有一个静态方法create_test_user。我认为 Nose 正在找到该方法并将其作为测试运行,因为它包含“测试”一词。

    我最终切换到unittest-xml-reporting 来获取 XUnit XML 报告,因为这是我使用 django-nose 的唯一原因,现在我的测试运行良好。

    【讨论】:

    • 如果您在测试中从WagtailPageTests 继承,那么它将继承call self.login on setup,然后calls create_test_user,这是设计使然。
    • 对,但是 django-nose 跑步者(显然)导致 create_test_user 被多次调用,导致 ValidationError 和 django-nose 将其解释为测试出错了。我怀疑从WagtailPageTests 继承的套件并非设计使然总是出错。而且由于django.test.runner.DiscoverRunner 或xmlrunner.extra.djangotestrunner.XMLTestRunner 都不会发生这种情况,我怀疑将django-nose(及其默认配置)与WagtailPageTests 结合使用会出现问题。
    猜你喜欢
    • 2015-06-28
    • 2012-11-11
    • 1970-01-01
    • 2012-08-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2011-12-12
    • 2018-04-20
    相关资源
    最近更新 更多