创建测试数据库时，Django测试失败

[英]Django test fails when creating test database

本文翻译自 Lacrymology 查看原文 2012/04/07 1033 python/ django-testing/ django/ postgresql

It fails with a number of related_name-related issues. Of course when running the actual dev server (with ./manage.py runserver) this doesn't happen, I'm guessing maybe the models are being generated twice? I'm running psycopg2 2.4.1, and here's my test output:

它失败了许多与related_name相关的问题。当然,当运行实际的开发服务器(使用./manage.py运行服务器)时,这不会发生,我猜可能模型正在生成两次?我正在运行psycopg2 2.4.1,这是我的测试输出:

(venv)lacrymology@Roller:boilerplate$ ./manage.py test
Creating test database for alias 'default'...
Error: One or more models did not validate:
l10n.address: Accessor for field 'user_shipping' clashes with related field 'User.shipping_address'. Add a related_name argument to the definition for 'user_shipping'.
l10n.address: Reverse query name for field 'user_shipping' clashes with related field 'User.shipping_address'. Add a related_name argument to the definition for 'user_shipping'.
l10n.address: Accessor for field 'user_billing' clashes with related field 'User.billing_address'. Add a related_name argument to the definition for 'user_billing'.
l10n.address: Reverse query name for field 'user_billing' clashes with related field 'User.billing_address'. Add a related_name argument to the definition for 'user_billing'.
custom_registration.profile: Accessor for field 'user' clashes with related field 'User.profile'. Add a related_name argument to the definition for 'user'.
custom_registration.profile: Reverse query name for field 'user' clashes with related field 'User.profile'. Add a related_name argument to the definition for 'user'.
addressmodel.address: Accessor for field 'user_shipping' clashes with related field 'User.shipping_address'. Add a related_name argument to the definition for 'user_shipping'.
addressmodel.address: Reverse query name for field 'user_shipping' clashes with related field 'User.shipping_address'. Add a related_name argument to the definition for 'user_shipping'.
addressmodel.address: Accessor for field 'user_billing' clashes with related field 'User.billing_address'. Add a related_name argument to the definition for 'user_billing'.
addressmodel.address: Reverse query name for field 'user_billing' clashes with related field 'User.billing_address'. Add a related_name argument to the definition for 'user_billing'.
profiles.profile: Accessor for field 'user' clashes with related field 'User.profile'. Add a related_name argument to the definition for 'user'.
profiles.profile: Reverse query name for field 'user' clashes with related field 'User.profile'. Add a related_name argument to the definition for 'user'.

2 个解决方案

#1

It is highly possible that your test.py imports an app which is not inside INSTALLED_APP but has some model fields pointing to the collided model. Try to grep user_shipping inside apps which are imported in test.py but not inside INSTALLED_APPS, and replace it.

test.py很可能导入的应用程序不在INSTALLED_APP内,但有一些模型字段指向碰撞的模型。尝试grep user_shipping在test.py中导入但不在INSTALLED_APPS内的应用程序中,并替换它。

./manage.py validate, which will be called internally by ./manage.py runserver, only checks models loaded from apps inside INSTALLED_APP and thus there was no error when you ran devserver. However, imports inside test.py will cause extra models of non-installed apps, if there is any, to be loaded and then collision will happen.

./manage.py验证,将由./manage.py runserver在内部调用,仅检查从INSTALLED_APP内的应用程序加载的模型,因此运行devserver时没有错误。但是,test.py中的导入会导致额外的未安装应用程序模型(如果有的话)加载,然后发生冲突。

#2

This was an issue with django-shop tests, as described in this comment: Django test fails when creating test database

这是django-shop测试的问题,如本评论中所述:Django测试在创建测试数据库时失败

I could find no way around it without changing the app's code, so I ended up just testing my own apps (running ./manage.py test myapp instead of ./manage.py test

在没有更改应用程序代码的情况下我无法找到它,所以我最终只测试了自己的应用程序(运行./manage.py测试myapp而不是./manage.py测试

注意！

本站翻译的文章，版权归属于本站，未经许可禁止转摘，转摘请注明本文地址：http://www.silva-art.net/blog/2012/04/07/535f3d13e8b4f9ec8dd6f1ce9645d4aa.html。

Django没有正确创建测试数据库 - Django is not creating the test database correctly 如何避免在django中创建测试数据库进行测试？ - How to avoid creating test database for testing in django? Django:测试结束时如何保存测试数据库? - Django: How to keep the test database when the test is finished? django测试应用程序错误——创建测试数据库时出错:拒绝创建数据库。 - django test app error - Got an error creating the test database: permission denied to create database Django单元测试，每次运行时都不创建测试数据库 - Django unit test without creating test database every time I run 在数据库中创建测试数据 - Creating test data in a database Travis：“创建测试数据库时出错：创建数据库的权限被拒绝” - Travis: “Got an error creating the test database: permission denied to create database” 为什么django SimpleTestCase创建测试数据库 - why django SimpleTestCase create test database django测试数据库不是用utf8创建的 - django test database is not created with utf8 为什么django设置导入两次，并且在运行单元测试时测试数据库创建了两次？ - Why are the django settings imported twice, and test database created twice when running unit-tests?