Website : rimsha.abasa.com
backdoor
Home
Console
Upload
information
Create File
Create Folder
About
Tools
:
/
proc
/
self
/
root
/
lib
/
python3
/
dist-packages
/
zope
/
component
/
__pycache__
/
Filename :
testlayer.cpython-310.pyc
back
Copy
o ,�WX � @ s� d dl Z d dlmZmZ zd dlmZ W n ey! dd� ZY nw d dlmZ d dl m Z d dl m Z m Z G d d � d e�ZG d d � d e�ZG d d� de�ZdS )� N)� xmlconfig�config��cleanUpc C � d S �N� r r r �:/usr/lib/python3/dist-packages/zope/component/testlayer.pyr � r )�provideHandler)�setHooks)�events� clearEventsc @ s> e Zd ZdZdZddd�Zdd� Zdd � Zd d � Zd d � Z dS )� LayerBasea� Sane layer base class. zope.testing implements an advanced mechanism so that layer setUp, tearDown, testSetUp and testTearDown code gets called in the right order. These methods are supposed to be @classmethods and should not use super() as the test runner is supposed to take care of that. In practice, this mechanism turns out not to be useful and overcomplicated. It becomes difficult to pass information into layers (such as a ZCML file to load), because the only way to pass in information is to subclass, and subclassing these layers leads to a range of interactions that is hard to reason about. We'd rather just use Python and the super mechanism, as we know how to reason about that. This base class is a hack to make this possible. The hack requires us to set __bases__, __module__ and __name__. This fools zope.testing into thinking that this layer instance is a class it can work with. It'd be better if zope.testing just called a minimal API and didn't try to be fancy. Fancy layer inheritance mechanisms can then be implemented elsewhere if people want to. But unfortunately it does implement a fancy mechanism and we need to fool it. r Nc C s( |d u r| j j}|| _|j| _|| _d S r )� __class__�__name__� __module__�package)�selfr �namer r r �__init__; s zLayerBase.__init__c C r r r �r r r r �setUpB r zLayerBase.setUpc C r r r r r r r �tearDownE r zLayerBase.tearDownc C r r r r r r r � testSetUpH r zLayerBase.testSetUpc C r r r r r r r � testTearDownK r zLayerBase.testTearDownr ) r r � __qualname__�__doc__� __bases__r r r r r r r r r r s r c sB e Zd ZdZd � fdd� Zdd� Zdd� Zd d � Zd d � Z� Z S )� ZCMLLayerBasez%Base class to load up some ZCML. Nc s t t| ��||� |p g | _d S r )�superr r �features)r r r r! �r r r r Q s zZCMLLayerBase.__init__c C sJ t � t�� }t�|� | jD ]}|�|� q| �|�| _t t j d� d S )Nr ) r r �ConfigurationMachiner �registerCommonDirectivesr! �provideFeature� _load_zcml�contextr r �append)r r' �featurer r r r U s zZCMLLayerBase.setUpc C � t � d S r )r r r r r r ^ � zZCMLLayerBase.testTearDownc C r* r r r r r r r a r+ zZCMLLayerBase.tearDownc C s t �r )�NotImplementedError�r r' r r r r& d r zZCMLLayerBase._load_zcml)NN) r r r r r r r r r& � __classcell__r r r" r r N s r c s. e Zd ZdZ d� fdd� Zdd� Z� ZS ) � ZCMLFileLayera8 This layer can be used to run tests with a ZCML file loaded. The ZCML file is assumed to include sufficient (meta)configuration so that it can be interpreted itself. I.e. to create a ZCMLLayer based on another ZCMLLayer's ZCML, just use a ZCML include statement in your own ZCML to load it. � ftesting.zcmlNc s2 t t| ��|||� tj�tj�|j�|�| _d S r ) r r/ r �os�path�join�dirname�__file__� zcml_file)r r r6 r r! r" r r r o s �zZCMLFileLayer.__init__c C s t j| j| j|dd�S )NT)r r' �execute)r �filer6 r r- r r r r& u s �zZCMLFileLayer._load_zcml)r0 NN)r r r r r r& r. r r r" r r/ g s �r/ )r1 �zope.configurationr r �zope.testing.cleanupr � ImportError�zope.componentr �zope.component.hooksr �zope.component.eventtestingr r �objectr r r/ r r r r �<module> s � 1