
我刚刚开始使用factory_boy django库来测试工厂,并且遇到了重复键约束违规的问题.
test_member_programme.py
from datetime import date,timedeltafrom django.test import TestCasefrom app.test.factorIEs import MemberFactory,ProgrammeFactoryfrom app.models.member_programme import MemberProgrammeclass MemberProgrammeTestCase(TestCase): def member_programme(self): yesterday = date.today() - timedelta(days=1) return MemberProgramme.objects.create( mem=MemberFactory(),prg=ProgrammeFactory(),date_registered=yesterday) def date_registered_should_be_defined_test(self): # This test passes memprg = self.member_programme() assert hasattr(memprg,'date_registered') def date_registered_should_be_in_past_test(self): # This test fails memprg = self.member_programme() assert memprg.date_registered < date.today()factorIEs.py
class CountryOfOriginFactory(factory.Factory): """ Factory class for app.models.CountryOfOrigin """ FACTORY_FOR = CountryOfOrigin code = 'UK' the_country = 'United Kingdom'class MemberFactory(factory.Factory): """ Factory class for app.models.Member """ FACTORY_FOR = Member first_name = 'Test' surname = 'User' sex = 'M' date_of_birth = datetime.date(1990,1,1) origin = factory.LazyAttribute(lambda a: CountryOfOriginFactory())运行第一个测试成功通过时,第二个测试失败并出现以下错误:
IntegrityError: duplicate key value violates unique constraint "country_of_origin_code_key"我的理解是每个TestCase都应该在一个事务中运行,但是在第二个测试运行之前,外键的创建似乎没有回滚.显然我做了一些根本错误的事情,但我有点难过!谢谢!
我已经找到了问题,但遗憾的是不知道如何解决它.问题是RolLBACK正在发生,但仅在一个数据库上(此应用程序有2个数据库).由于遗留原因,我们为django auth,flatpages等提供了一个单独的数据库,并为我们的应用程序提供了另一个数据库.
dba test_app 127.0.0.1 2012-09-04 21:51:50.806 UTC LOG: duration: 0.038 ms statement: BEGIN; SET TRANSACTION ISolATION LEVEL READ COMMITTEDdba test_app 127.0.0.1 2012-09-04 21:51:50.808 UTC LOG: duration: 0.903 ms statement: INSERT INTO "member_programme" ("mem_ID","prgm_ID","date_registered","date_completed","ordinality") VALUES (1,E'2012-09-04',NulL,1)dba test_app 127.0.0.1 2012-09-04 21:51:50.808 UTC LOG: duration: 0.150 ms statement: SELECT CURRVAL(pg_get_serial_sequence('"member_programme"','ID'))dba test_app 127.0.0.1 2012-09-04 21:51:50.810 UTC LOG: duration: 1.796 ms statement: COMMITdba test_app_django 127.0.0.1 2012-09-04 21:51:50.811 UTC LOG: duration: 0.056 ms statement: RolLBACK <---- RolLBACK ON DJANGO DB ONLYdba test_app_django 127.0.0.1 2012-09-04 21:51:50.814 UTC LOG: disconnection: session time: 0:00:21.005 user=dba database=test_app_django host=127.0.0.1 port=60355dba test_app 127.0.0.1 2012-09-04 21:51:50.818 UTC LOG: disconnection: session time: 0:00:04.751 user=dba database=test_app host=127.0.0.1 port=60357dba test_app 127.0.0.1 2012-09-04 21:54:00.796 UTC LOG: connection authorized: user=dba database=test_appdba test_app 127.0.0.1 2012-09-04 21:54:00.802 UTC LOG: duration: 0.243 ms statement: SET DATESTYLE TO 'ISO'dba test_app 127.0.0.1 2012-09-04 21:54:00.802 UTC LOG: duration: 0.156 ms statement: SHOW clIEnt_enCodingdba test_app 127.0.0.1 2012-09-04 21:54:00.803 UTC LOG: duration: 0.047 ms statement: SHOW default_transaction_isolationdba test_app 127.0.0.1 2012-09-04 21:54:00.803 UTC LOG: duration: 0.068 ms statement: BEGIN; SET TRANSACTION ISolATION LEVEL READ COMMITTEDdba test_app 127.0.0.1 2012-09-04 21:54:00.804 UTC LOG: duration: 0.410 ms statement: SET TIME ZONE E'Pacific/Auckland'dba test_app 127.0.0.1 2012-09-04 21:54:00.805 UTC ERROR: duplicate key value violates unique constraint "country_of_origin_code_key"有类似问题的人here.最佳答案自1.2以来,Django已经拥有support for testing against multiple databases!
将以下属性添加到我的TestCase解决了以下问题:
multi_db = True 总结 以上是内存溢出为你收集整理的python – TestCase中缺少ROLLBACK导致multi-db django应用程序中的唯一约束违规全部内容,希望文章能够帮你解决python – TestCase中缺少ROLLBACK导致multi-db django应用程序中的唯一约束违规所遇到的程序开发问题。
如果觉得内存溢出网站内容还不错,欢迎将内存溢出网站推荐给程序员好友。
欢迎分享,转载请注明来源:内存溢出
微信扫一扫
支付宝扫一扫
评论列表(0条)