B `@sVddlmZddlmZddlmZmZmZddlm Z ddl m Z GdddZ dS) ) Interface) action_method)IRendererFactoryISecurityPolicy ITraverser)RendererHelper)split_path_infoc@s>eZdZd ddZddZeZed ddZd d d ZeZ dS)TestingConfiguratorMixinNTcCs.ddlm}||||||}|j|t|S)a0Unit/integration testing helper. Registers a faux :term:`security policy`. This function is most useful when testing code that uses the security APIs, such as :meth:`pyramid.request.Request.identity`, :attr:`pyramid.request.Request.authenticated_userid`, or :meth:`pyramid.request.Request.has_permission`, The behavior of the registered :term:`security policy` depends on the arguments passed to this method. :param userid: If provided, the policy's ``authenticated_userid`` method will return this value. As a result, :attr:`pyramid.request.Request.authenticated_userid` will have this value as well. :type userid: str :param identity: If provided, the policy's ``identity`` method will return this value. As a result, :attr:`pyramid.request.Request.identity`` will have this value. :type identity: object :param permissive: If true, the policy will allow access to any user for any permission. If false, the policy will deny all access. :type permissive: bool :param remember_result: If provided, the policy's ``remember`` method will return this value. Otherwise, ``remember`` will return an empty list. :type remember_result: list :param forget_result: If provided, the policy's ``forget`` method will return this value. Otherwise, ``forget`` will return an empty list. :type forget_result: list .. versionadded:: 1.4 The ``remember_result`` argument. .. versionadded:: 1.4 The ``forget_result`` argument. .. versionchanged:: 2.0 Removed ``groupids`` argument and add `identity` argument. r)DummySecurityPolicy)pyramid.testingr registryregisterUtilityr)selfZuserididentityZ permissiveZremember_resultZ forget_resultr policyr^/home/kop/projects/devel/pgwui/test_venv/lib/python3.7/site-packages/pyramid/config/testing.pytesting_securitypolicy s 2 z/TestingConfiguratorMixin.testing_securitypolicycs(Gfddd}|j|tftS)aUnit/integration testing helper: registers a dictionary of :term:`resource` objects that can be resolved via the :func:`pyramid.traversal.find_resource` API. The :func:`pyramid.traversal.find_resource` API is called with a path as one of its arguments. If the dictionary you register when calling this method contains that path as a string key (e.g. ``/foo/bar`` or ``foo/bar``), the corresponding value will be returned to ``find_resource`` (and thus to your code) when :func:`pyramid.traversal.find_resource` is called with an equivalent path string or tuple. cs eZdZddZfddZdS)zITestingConfiguratorMixin.testing_resources..DummyTraverserFactorycSs ||_dS)N)context)rrrrr__init__UszRTestingConfiguratorMixin.testing_resources..DummyTraverserFactory.__init__cs*|j}|}t|}|dd||d|dS)Nr)rZ view_namesubpath traversedZ virtual_rootZvirtual_root_pathroot)Z path_infor)rrequestpathobr) resourcesrr__call__XszRTestingConfiguratorMixin.testing_resources..DummyTraverserFactory.__call__N)__name__ __module__ __qualname__rrr)rrrDummyTraverserFactoryTsr")r ZregisterAdapterrr)rrr"r)rrtesting_resourcesEs z*TestingConfiguratorMixin.testing_resourcescs*||}gfdd}|||S)aUnit/integration testing helper: Registers a :term:`subscriber` which listens for events of the type ``event_iface``. This method returns a list object which is appended to by the subscriber whenever an event is captured. When an event is dispatched that matches the value implied by the ``event_iface`` argument, that event will be appended to the list. You can then compare the values in the list to expected event notifications. This method is useful when testing code that wants to call :meth:`pyramid.registry.Registry.notify`, or :func:`zope.component.event.dispatch`. The default value of ``event_iface`` (``None``) implies a subscriber registered for *any* kind of event. cs|dS)N)extend)event)Lrr subscriberszCTestingConfiguratorMixin.testing_add_subscriber..subscriber)Z maybe_dottedZadd_subscriber)rZ event_ifacer'r)r&rtesting_add_subscriberms    z/TestingConfiguratorMixin.testing_add_subscribercCsddlm}t||jd}|jjt|jd}t||sV||j|}|jj|t|jdddlm }|dkrp|}| |||S)aUnit/integration testing helper: register a renderer at ``path`` (usually a relative filename ala ``templates/foo.pt`` or an asset specification) and return the renderer object. If the ``renderer`` argument is None, a 'dummy' renderer will be used. This function is useful when testing code that calls the :func:`pyramid.renderers.render` function or :func:`pyramid.renderers.render_to_response` function or any other ``render_*`` or ``get_*`` API of the :mod:`pyramid.renderers` module. Note that calling this method for with a ``path`` argument representing a renderer factory type (e.g. for ``foo.pt`` usually implies the ``chameleon_zpt`` renderer factory) clobbers any existing renderer factory registered for that type. .. note:: This method is also available under the alias ``testing_add_template`` (an older name for it). r)DummyRendererFactory)namer )r*)DummyTemplateRendererN) r r)rr Z queryUtilityrtype isinstancer r+add)rrZrendererr)helperfactoryr+rrrtesting_add_renderers      z-TestingConfiguratorMixin.testing_add_renderer)NNTNN)N)N) rr r!rr#Ztesting_modelsrr(r1Ztesting_add_templaterrrrr s 4&  (r N) Zzope.interfacerZpyramid.config.actionsrZpyramid.interfacesrrrZpyramid.renderersrZpyramid.traversalrr rrrrs