[Zope-CMF] Re: CachingPolicyManager improvements

yuppie y.2005- at wcm-solutions.de
Fri Sep 9 05:54:19 EDT 2005

Hi Stefan!

Stefan H. Holek wrote:
> PortalTestCase is actually only intended as a base class for  
> CMFTestCase/PloneTestCase/CPSTestCase/whatever, not for direct use.  It 
> provides some default behavior, because, for example, the  requirement 
> to refresh the skin cache is pretty hard to figure out.  The 
> ZopeTestCase philosophy is about convenience and "plumbing  included".
> I am committed to keeping things up-to-date. Please make me aware of  
> breakage, I am going to address everything that might come up.

That's great, but that doesn't resolve the problem:

If changes like the _refreshSkinData change in CMF 1.5 are made in CMF, 
tests are broken until there is a new Zope version with a new 
PortalTestCase that reflects these changes. CMF would depend on that new 
Zope version.

> On 5. Sep 2005, at 14:06, yuppie wrote:
>> PortalTestCase is in the wrong layer. It makes assumptions about  the 
>> way CMF works. Changes to the CMF might break PortalTestCase  and 
>> create a dependency on a new Zope release. (We saw that problem  
>> already with the _refreshSkinData changes in CMF 1.5)



More information about the Zope-CMF mailing list