Commit 7ae951a4 authored by Julien Muchembled's avatar Julien Muchembled

Update TestPortalTypeClass.testBoundMethodCaching WRT r40640

Since r40640, portal type classes are reinitialized at the end of transaction,
but the test is still valid in multithreaded setups, where classes may be
ghostified at any moment by another thread.

testBoundMethodCaching and testClassHierarchyAfterReset somehow test the same
thing, but in different ways.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41204 20353a03-c40f-0410-a6d1-a30d3c3de9de
parent 5992ea61
...@@ -187,8 +187,7 @@ class TestPortalTypeClass(ERP5TypeTestCase): ...@@ -187,8 +187,7 @@ class TestPortalTypeClass(ERP5TypeTestCase):
Or do we need to reset the fewest classes as possible ? Or do we need to reset the fewest classes as possible ?
""" """
newDocument = self.portal.newContent(self.id(), 'Folder').newContent newDocument = self.portal.newContent(self.id(), 'Folder').newContent
self.portal.portal_types.newContent(portal_type='Base Type', self.portal.portal_types.resetDynamicDocuments()
type_class='Folder')
newDocument(portal_type='Folder') newDocument(portal_type='Folder')
def testPropertyGenerationOnTempPortalType(self): def testPropertyGenerationOnTempPortalType(self):
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment