File: //opt/alt/python37/lib/python3.7/site-packages/asynctest/__pycache__/case.cpython-37.pyc
B
�P�e�D � @ s� d Z ddlZddlZddlZddlZddlZddlZddlT ddlZ ddl
Z G dd� dej �Z G dd� dej
�Z
G dd � d e
ej�ZG d
d � d e
�Zdd d
�ZdS )a�
Module ``case``
---------------
Enhance :class:`unittest.TestCase`:
* a new loop is issued and set as the default loop before each test, and
closed and disposed after,
* if the loop uses a selector, it will be wrapped with
:class:`asynctest.TestSelector`,
* a test method in a TestCase identified as a coroutine function or returning
a coroutine will run on the loop,
* :meth:`~TestCase.setUp()` and :meth:`~TestCase.tearDown()` methods can be
coroutine functions,
* cleanup functions registered with :meth:`~TestCase.addCleanup()` can be
coroutine functions,
* a test fails if the loop did not run during the test.
class-level set-up
~~~~~~~~~~~~~~~~~~
Since each test runs in its own loop, it is not possible to run
:meth:`~TestCase.setUpClass()` and :meth:`~TestCase.tearDownClass()` as
coroutines.
If one needs to perform set-up actions at the class level (meaning
once for all tests in the class), it should be done using a loop created for
this sole purpose and that is not shared with the tests. Ideally, the loop
shall be closed in the method which creates it.
If one really needs to share a loop between tests,
:attr:`TestCase.use_default_loop` can be set to ``True`` (as a class
attribute). The test case will use the loop returned by
:meth:`asyncio.get_event_loop()` instead of creating a new loop for each test.
This way, the event loop or event loop policy can be set during class-level
set-up and tear down.
� N)�*c @ sL e Zd Zdd� Zdd� Zdd� Zdd� Zd d
� Zd d � Zd
d� Z dd� Z
dS )�_Policyc C s || _ || _|| _d | _d S )N)�original_policy�forbid_get_event_loop�loop�watcher)�selfr r r � r �?/opt/alt/python37/lib/python3.7/site-packages/asynctest/case.py�__init__; s z_Policy.__init__c C s* | j rtd��n| jr | jS | j�� S d S )NzSTestCase.forbid_get_event_loop is True, asyncio.get_event_loop() must not be called)r �AssertionErrorr r �get_event_loop)r r r r
r
E s
z_Policy.get_event_loopc C s
| j �� S )N)r �new_event_loop)r r r r
r N s z_Policy.new_event_loopc C s | j �|�}|| _|S )N)r �set_event_loopr )r r �resultr r r
r Q s z_Policy.set_event_loopc C s t td�st�d S )N�SafeChildWatcher)�hasattr�asyncio�NotImplementedError)r r r r
� _check_unixV s
z_Policy._check_unixc C sD | � � | jr6| jd kr0t�� | _| j�| j� | jS | j�� S d S )N)r r r r r � attach_loopr �get_child_watcher)r r r r
r Z s
z_Policy.get_child_watcherc C s4 | � � | jr$| j�|�}|| _|S | j�|�S d S )N)r r r �set_child_watcherr )r r r r r r
r e s z_Policy.set_child_watcherc C s | j r | j �� | j�d � d S )N)r �closer r )r r r r
�
reset_watchern s
z_Policy.reset_watcherN) �__name__�
__module__� __qualname__r r
r r r r r r r r r r
r : s
r c s� e Zd ZdZdZdZdZdd� Zdd� Zdd � Z d
d � Z
d d
� Z d dd�Z dd� Z
dd� Zejdd� �Z� fdd�Zejdd� �Zejdd� �Zejd d � �Zejd d � �Z� ZS )!�TestCaseaJ
A test which is a coroutine function or which returns a coroutine will run
on the loop.
Once the test returned, one or more assertions are checked. For instance,
a test fails if the loop didn't run. These checks can be enabled or
disabled using the :func:`~asynctest.fail_on` decorator.
By default, a new loop is created and is set as the default loop before
each test. Test authors can retrieve this loop with
:attr:`~asynctest.TestCase.loop`.
If :attr:`~asynctest.TestCase.use_default_loop` is set to ``True``, the
current default event loop is used instead. In this case, it is up to the
test author to deal with the state of the loop in each test: the loop might
be closed, callbacks and tasks may be scheduled by previous tests. It is
also up to the test author to close the loop and dispose the related
resources.
If :attr:`~asynctest.TestCase.forbid_get_event_loop` is set to ``True``,
a call to :func:`asyncio.get_event_loop()` will raise an
:exc:`AssertionError`. Since Python 3.6, calling
:func:`asyncio.get_event_loop()` from a callback or a coroutine will return
the running loop (instead of raising an exception).
These behaviors should be configured when defining the test case class::
class With_Reusable_Loop_TestCase(asynctest.TestCase):
use_default_loop = True
forbid_get_event_loop = False
def test_something(self):
pass
If :meth:`setUp()` and :meth:`tearDown()` are coroutine functions, they
will run on the loop. Note that :meth:`setUpClass()` and
:meth:`tearDownClass()` can not be coroutines.
.. versionadded:: 0.5
attribute :attr:`~asynctest.TestCase.use_default_loop`.
.. versionadded:: 0.7
attribute :attr:`~asynctest.TestCase.forbid_get_event_loop`.
In any case, the default loop is now reset to its original state
outside a test function.
.. versionadded:: 0.8
``ignore_loop`` has been deprecated in favor of the extensible
:func:`~asynctest.fail_on` decorator.
FNc C sR | j rt�� | _d }nt�� }| _tt�� || j�}t�|� | � | j�| _d S )N)
�use_default_loopr r
r r r �get_event_loop_policyr �set_event_loop_policy� _patch_loop)r r �policyr r r
�
_init_loop� s
zTestCase._init_loopc C sR t �� }| js<tjdkr*| j�| j�� � | j�� |� � t �
|j � d | _d S )N)� � ) r r r �sys� version_infor �run_until_complete�shutdown_asyncgensr r r! r )r r# r r r
� _unset_loop� s
zTestCase._unset_loopc sf t � d�r� S d� _� fdd�}x"dD ]}t� ||t� |��� q&W t� tjj�rbtj �
� j �� _ � S )N�_asynctest_ranFc s$ t �� ��� fdd��}t�|��S )Nc s z
�||�S d� _ X d S )NT)r, )r �args�kwargs)r �methodr r
�wrapper� s
z4TestCase._patch_loop.<locals>.wraps.<locals>.wrapper)� functools�wraps�types�
MethodType)r/ r0 )r )r/ r
r2 � s z#TestCase._patch_loop.<locals>.wraps)� run_foreverr) ) r r, �setattr�getattr�
isinstancer �selector_events�BaseSelectorEventLoop� asynctest�selectorZ TestSelector� _selector)r r r2 r/ r )r r
r" � s
zTestCase._patch_loopc C sr | � � t| | j�}t|tjjd �}|p0tj�� | _| j�| � t� | j
�r^| j � | �
� � n| �
� d| j _
d S )NF)r$ r7 �_testMethodNamer; �_fail_onZ
_FAIL_ON_ATTR�_checkerZ before_testr �iscoroutinefunctionZsetUpr r) r, )r �test�checkerr r r
�_setUp� s zTestCase._setUpc C s6 t �| j�r | j�| �� � n| �� | j�| � d S )N)r rA ZtearDownr r) r@ Z
check_test)r r r r
� _tearDown� s zTestCase._tearDownc
C s |}|d kr.| � � }t|dd �}|d k r.|� |�| � t| | j�}t| jdd�s^t|dd�r�z,t| jdd�pxt|dd�}| �|| |� W d |�| � X d S t|dd�}tj� |�}�z|| _
|� | �� | � � W d Q R X |j
�r2||_|j | dd�� | �|� W d Q R X d|_|� | �� | �� W d Q R X | j�| �� � | �� x"|jD ]\}} | �||| � �qRW | �||j� |j
�r�|�r�|j�r�| �||j� n
| �|� n
|�| � |S |�| � |d k�r�t|d d �}
|
d k �r�|
� |j� � d |_d | _
X d S )
N� startTestRunZ__unittest_skip__FZ__unittest_skip_why__� Z __unittest_expecting_failure__T)ZisTest� stopTestRun) ZdefaultTestResultr7 Z startTestr> � __class__Z_addSkipZstopTest�unittest�case�_Outcome�_outcome�testPartExecutorrD �success�expecting_failure�_run_test_methodrE r r) �
doCleanupsr+ ZskippedZ_feedErrorsToResult�errorsZexpectedFailureZ_addExpectedFailureZ_addUnexpectedSuccessZ
addSuccess�clear) r r Z orig_resultrF Z
testMethodZskip_whyrP �outcomerB �reasonrH r r r
�run sd
z TestCase.runc C s� | � � z�yd| �t| | j�� | �� xD| jrj| j�d�\}}}t�|�r^| j �
|||�� q(|||� q(W W n t k
r� � Y nX W d | � � X d S )N���)
rD rQ r7 r> rE � _cleanups�popr rA r r) � Exceptionr+ )r �functionr- r. r r r
�debugL s
zTestCase.debugc C s |� }t �|�r | j�|� d S )N)r � iscoroutiner r) )r r/ r r r r
rQ ] s
zTestCase._run_test_methodc c sn | j ptj�� }xV| jrf| j�� \}}}|�| ��, t�|�rP|||�E dH n
|||� W dQ R X qW |j S )zX
Execute all cleanup functions. Normally called for you after tearDown.
N)
rM rJ ZmockrL rY rZ rN r rA rO )r rU r\ r- r. r r r
rR d s
zTestCase.doCleanupsc s t � j|f|�|�S )z�
Add a function, with arguments, to be called when the test is
completed. If function is a coroutine function, it will run on the loop
before it's cleaned.
)�super�
addCleanup)r r\ r- r. )rI r r
r` t s zTestCase.addCleanupc c s | � |�� |E dH S Q R X dS )z�
Test that an exception of type ``exception`` is raised when an
exception is raised when awaiting ``awaitable``, a future or coroutine.
:see: :meth:`unittest.TestCase.assertRaises()`
N)� assertRaises)r � exception� awaitabler r r
�assertAsyncRaises| s zTestCase.assertAsyncRaisesc c s" | � ||�� |E dH S Q R X dS )z�
Like :meth:`assertAsyncRaises()` but also tests that ``regex`` matches
on the string representation of the raised exception.
:see: :meth:`unittest.TestCase.assertRaisesRegex()`
N)�assertRaisesRegex)r rb �regexrc r r r
�assertAsyncRaisesRegex� s z TestCase.assertAsyncRaisesRegexc c s | � |�� |E dH S Q R X dS )z�
Test that a warning is triggered when awaiting ``awaitable``, a future
or a coroutine.
:see: :meth:`unittest.TestCase.assertWarns()`
N)Z assertWarns)r �warningrc r r r
�assertAsyncWarns� s zTestCase.assertAsyncWarnsc c s" | � ||�� |E dH S Q R X dS )z�
Like :meth:`assertAsyncWarns()` but also tests that ``regex`` matches
on the message of the triggered warning.
:see: :meth:`unittest.TestCase.assertWarnsRegex()`
N)ZassertWarnsRegex)r rh rf rc r r r
�assertAsyncWarnsRegex� s z TestCase.assertAsyncWarnsRegex)N)r r r �__doc__r r r r$ r+ r" rD rE rW r] rQ r � coroutinerR r` rd rg ri rj �
__classcell__r r )rI r
r w s$ 6
C r c @ s e Zd ZdZdS )�FunctionTestCasezv
Enables the same features as :class:`~asynctest.TestCase`, but for
:class:`~asynctest.FunctionTestCase`.
N)r r r rk r r r r
rn � s rn c sD e Zd ZdZ� fdd�Zejdd� �Zdd� Zejdd � �Z � Z
S )
�ClockedTestCasez�
Subclass of :class:`~asynctest.TestCase` with a controlled loop clock,
useful for testing timer based behaviour without slowing test run time.
The clock will only advance when :meth:`advance()` is called.
c s2 t � �� t�� jj�� fdd��� j_d� _d S )Nc s � j S )N)�_timer )r r r
�<lambda>� � z,ClockedTestCase._init_loop.<locals>.<lambda>r )r_ r$ r1 r2 r �timerp )r )rI )r r
r$ � s
zClockedTestCase._init_loopc c sz |dk rt d�|���| �� E dH | j| }x2| �� }|dksH||krJP || _| �� E dH q0W || _| �� E dH dS )a
Fast forward time by a number of ``seconds``.
Callbacks scheduled to run up to the destination clock time will be
executed on time:
>>> self.loop.call_later(1, print_time)
>>> self.loop.call_later(2, self.loop.call_later, 1, print_time)
>>> await self.advance(3)
1
3
In this example, the third callback is scheduled at ``t = 2`` to be
executed at ``t + 1``. Hence, it will run at ``t = 3``. The callback as
been called on time.
r z#Cannot go back in time ({} seconds)N)�
ValueError�format� _drain_looprp �_next_scheduled)r �secondsZ target_time� next_timer r r
�advance� s
zClockedTestCase.advancec C s( y| j jd jS tk
r" d S X d S )Nr )r �
_scheduled�_when�
IndexError)r r r r
rw � s z ClockedTestCase._next_scheduledc c sF x@| � � }| jjs&|d ks$|| jkr&P t�d�E d H d| j_qW d S )Nr T)rw r �_readyrp r �sleepZ_TestCase_asynctest_ran)r ry r r r
rv � s
zClockedTestCase._drain_loop) r r r rk r$ r rl rz rw rv rm r r )rI r
ro � s
$ro c C s0 t �dt� tj�ddi�}| dkr(|S || �S )zK
Ignore the error case where the loop did not run during the test.
zBignore_loop() is deprecated in favor of fail_on(unused_loop=False)Z unused_loopFN)�warnings�warn�DeprecationWarningr; r? )�funcrC r r r
� ignore_loop� s r� )N)rk r r1 r3 rJ r' r� Z
unittest.caseZasynctest.selectorr; Zasynctest._fail_on�AbstractEventLoopPolicyr r rn ro r� r r r r
�<module>+ s = 4B