m
Ec @ s d Z d k Z d k Z e d j o$ e e i i e i d d n d e f d YZ d Z d Z
d Z e d j o e n d S(
s] Test Five-traversable classes
$Id: test_traversable.py 68752 2006-06-19 15:02:21Z regebro $
Nt __main__i s framework.pyt SimpleClassc B s t Z d Z RS( s Class with no __bobo_traverse__.( t __name__t
__module__t __doc__( ( ( tK /data/zmath/zope/lib/python/Products/Five/browser/tests/test_traversable.pyR s c C s d S( s
Test the behaviour of Five-traversable classes.
>>> import Products.Five
>>> from Products.Five import zcml
>>> zcml.load_config("configure.zcml", Products.Five)
``SimpleContent`` is a traversable class by default. Its fallback
traverser should raise NotFound when traversal fails. (Note: If
we return None in __fallback_traverse__, this test passes but for
the wrong reason: None doesn't have a docstring so BaseRequest
raises NotFoundError.)
>>> from Products.Five.tests.testing.simplecontent import manage_addSimpleContent
>>> manage_addSimpleContent(self.folder, 'testoid', 'Testoid')
>>> print http(r'''
... GET /test_folder_1_/testoid/doesntexist HTTP/1.1
... ''')
HTTP/1.1 404 Not Found
...
Now let's take class which already has a __bobo_traverse__ method.
Five should correctly use that as a fallback.
>>> configure_zcml = '''
...
...
...
...
...
...
...
...
...
...
... '''
>>> zcml.load_string(configure_zcml)
>>> from Products.Five.tests.testing.fancycontent import manage_addFancyContent
>>> info = manage_addFancyContent(self.folder, 'fancy', '')
In the following test we let the original __bobo_traverse__ method
kick in:
>>> print http(r'''
... GET /test_folder_1_/fancy/something-else HTTP/1.1
... ''')
HTTP/1.1 200 OK
...
something-else
Once we have a custom __bobo_traverse__ method, though, it always
takes over. Therefore, unless it raises AttributeError or
KeyError, it will be the only way traversal is done.
>>> print http(r'''
... GET /test_folder_1_/fancy/fancyview HTTP/1.1
... ''')
HTTP/1.1 200 OK
...
fancyview
As said, if the original __bobo_traverse__ method *does* raise
AttributeError or KeyError, we can get normal view look-up. Other
exceptions are passed through just fine:
>>> print http(r'''
... GET /test_folder_1_/fancy/raise-attributeerror HTTP/1.1
... ''')
HTTP/1.1 200 OK
...
Fancy, fancy
>>> print http(r'''
... GET /test_folder_1_/fancy/raise-keyerror HTTP/1.1
... ''')
HTTP/1.1 200 OK
...
Fancy, fancy
>>> print http(r'''
... GET /test_folder_1_/fancy/raise-valueerror HTTP/1.1
... ''', handle_errors=False)
Traceback (most recent call last):
...
ValueError: ...
Five's traversable monkeypatches the __bobo_traverse__ method to do view
lookup and then delegates back to the original __bobo_traverse__ or direct
attribute/item lookup to do normal lookup. In the Zope 2 ZPublisher, an
object with a __bobo_traverse__ will not do attribute lookup unless the
__bobo_traverse__ method itself does it (i.e. the __bobo_traverse__ is the
only element used for traversal lookup). Let's demonstrate:
>>> from Products.Five.tests.testing.fancycontent import manage_addNonTraversableFancyContent
>>> info = manage_addNonTraversableFancyContent(self.folder, 'fancy_zope2', '')
>>> self.folder.fancy_zope2.an_attribute = 'This is an attribute'
>>> print http(r'''
... GET /test_folder_1_/fancy_zope2/an_attribute HTTP/1.1
... ''')
HTTP/1.1 200 OK
...
an_attribute
Without a __bobo_traverse__ method this would have returned the attribute
value 'This is an attribute'. Let's make sure the same thing happens for
an object that has been marked traversable by Five:
>>> self.folder.fancy.an_attribute = 'This is an attribute'
>>> print http(r'''
... GET /test_folder_1_/fancy/an_attribute HTTP/1.1
... ''')
HTTP/1.1 200 OK
...
an_attribute
Clean up:
>>> from zope.app.testing.placelesssetup import tearDown
>>> tearDown()
Verify that after cleanup, there's no cruft left from five:traversable::
>>> from Products.Five.browser.tests.test_traversable import SimpleClass
>>> hasattr(SimpleClass, '__bobo_traverse__')
False
>>> hasattr(SimpleClass, '__fallback_traverse__')
False
>>> from Products.Five.tests.testing.fancycontent import FancyContent
>>> hasattr(FancyContent, '__bobo_traverse__')
True
>>> hasattr(FancyContent.__bobo_traverse__, '__five_method__')
False
>>> hasattr(FancyContent, '__fallback_traverse__')
False
N( ( ( ( R t test_traversable s c C s d S( s~
Test that views don't shadow attributes, e.g. items in a folder.
Let's first define a browser page for object managers called
``eagle``:
>>> configure_zcml = '''
...
...
...
...
...
... '''
>>> import Products.Five
>>> from Products.Five import zcml
>>> zcml.load_config("configure.zcml", Products.Five)
>>> zcml.load_string(configure_zcml)
Then we create a traversable folder...
>>> from Products.Five.tests.testing.folder import manage_addFiveTraversableFolder
>>> manage_addFiveTraversableFolder(self.folder, 'ftf')
and add an object called ``eagle`` to it:
>>> from Products.Five.tests.testing.simplecontent import manage_addIndexSimpleContent
>>> manage_addIndexSimpleContent(self.folder.ftf, 'eagle', 'Eagle')
When we publish the ``ftf/eagle`` now, we expect the attribute to
take precedence over the view during traversal:
>>> print http(r'''
... GET /test_folder_1_/ftf/eagle HTTP/1.1
... ''')
HTTP/1.1 200 OK
...
Default index_html called
Of course, unless we explicitly want to lookup the view using @@:
>>> print http(r'''
... GET /test_folder_1_/ftf/@@eagle HTTP/1.1
... ''')
HTTP/1.1 200 OK
...
The eagle has landed
Some weird implementations of __bobo_traverse__, like the one
found in OFS.Application, raise NotFound. Five still knows how to
deal with this, hence views work there too:
>>> print http(r'''
... GET /eagle HTTP/1.1
...
... ''')
HTTP/1.1 200 OK
...
The eagle has landed
>>> print http(r'''
... GET /@@eagle HTTP/1.1
...
... ''')
HTTP/1.1 200 OK
...
The eagle has landed
However, acquired attributes *should* be shadowed. See discussion on
http://codespeak.net/pipermail/z3-five/2006q2/001474.html
>>> manage_addIndexSimpleContent(self.folder, 'mouse', 'Mouse')
>>> print http(r'''
... GET /test_folder_1_/ftf/mouse HTTP/1.1
... ''')
HTTP/1.1 200 OK
...
The mouse has been eaten by the eagle
Clean up:
>>> from zope.app.testing.placelesssetup import tearDown
>>> tearDown()
N( ( ( ( R t! test_view_doesnt_shadow_attribute s cc C s d k l } | S( N( s FunctionalDocTestSuite( t Testing.ZopeTestCaset FunctionalDocTestSuite( R ( ( R t
test_suite! s
(
R t ost sysR t execfilet patht joint objectR R R R
t framework( R R R R
R R ( ( R t ? s
$ e