| Server IP : 209.38.156.173 / Your IP : 216.73.216.122 [ Web Server : Apache/2.4.52 (Ubuntu) System : Linux lakekumayuhotel 5.15.0-136-generic #147-Ubuntu SMP Sat Mar 15 15:53:30 UTC 2025 x86_64 User : root ( 0) PHP Version : 8.1.2-1ubuntu2.22 Disable Function : NONE Domains : 2 Domains MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /usr/lib/python3/dist-packages/twisted/trial/test/__pycache__/ |
Upload File : |
o
�b\� � @ s� d Z ddlZddlZddlZddlZddlmZ ddlm Z m
Z
ddl m Z ddl
mZ ddlmZmZmZmZ ddlmZmZmZ dd lmZ dd
lmZ G d d � d �ZG d
d� d�Z G dd� de ej �Z G dd� de ej �Z G dd� de�Z!G dd� de!ej �Z"G dd� de!ej �Z#G dd� de�Z$G dd � d e$ej �Z%G d d � d e$ej �Z&G d d � d e�Z'G d!d"� d"e'ej �Z(G d#d$� d$e'ej �Z)G d%d&� d&e�Z*G d'd(� d(e*ej �Z+G d)d*� d*e*ej �Z,G d+d,� d,e�Z-G d-d.� d.e-ej �Z.G d/d0� d0e-ej �Z/G d1d2� d2ej �Z0G d3d4� d4�Z1G d5d6� d6e1ej �Z2G d7d8� d8e1ej �Z3G d9d:� d:eej �Z4G d;d<� d<�Z5G d=d>� d>e5ej �Z6G d?d@� d@e5ej �Z7G dAdB� dBej �Z8G dCdD� dD�Z9G dEdF� dFe9ej �Z:G dGdH� dHe9ej �Z;G dIdJ� dJ�Z<G dKdL� dLe<ej �Z=G dMdN� dNe<ej �Z>G dOdP� dP�Z?G dQdR� dRe?ej �Z@G dSdT� dTe?ej �ZAG dUdV� dV�ZBG dWdX� dXeBej �ZCG dYdZ� dZeBej �ZDG d[d\� d\�ZEG d]d^� d^eEej �ZFG d_d`� d`eEej �ZGG dadb� dbej �ZHdS )ca�
Tests for the behaviour of unit tests.
Many tests in this module follow a simple pattern. A mixin is defined which
includes test methods for a certain feature. The mixin is inherited from twice,
once by a class also inheriting from SynchronousTestCase and once from a class
inheriting from TestCase. These two subclasses are named like
I{SynchronousFooTests} and I{AsynchronousFooTests}, where I{Foo} is related to
the name of the mixin. Sometimes the mixin is defined in another module, along
with the synchronous subclass. The mixin is imported into this module to define
the asynchronous subclass.
This pattern allows the same tests to be applied to the two base test case
classes trial provides, ensuring their behavior is the same.
Most new tests should be added in this pattern. Tests for functionality which
is intentionally only provided by TestCase, not SynchronousTestCase, is excepted
of course.
� N)�StringIO)�defer�reactor)�_PYPY)�namedAny)�reporter�runner�unittest�util)� _clearSuite� _ForceGarbageCollectionDecorator�
_iterateTests)� erroneous)�SuppressionMixinc @ �( e Zd ZdZdd� Zdd� Zdd� ZdS ) �ResultsTestMixinzG
Provide useful APIs for test cases that are about test cases.
c C s& t �� | _| j�|�| _t�� | _dS )zt
Load tests from the given test case class and create a new reporter to
use for running it.
N)�pyunit�
TestLoader�loader�loadTestsFromTestCase�suiter �
TestResult��selfr � r �?/usr/lib/python3/dist-packages/twisted/trial/test/test_tests.py� loadSuite1 s
zResultsTestMixin.loadSuitec C sD | � | j�� � | �| jjg � | �| jjg � | �| jjg � dS )z
test the setup
N)�
assertTruer �
wasSuccessful� assertEqual�errors�failures�skips�r r r r �
test_setUp: s zResultsTestMixin.test_setUpc C s2 | � | j�� |� | �| j� | � | jj|� dS )z:
Asserts that the test count is plausible
N)r r �countTestCasesr �testsRun)r �numTestsr r r � assertCountC s z ResultsTestMixin.assertCountN)�__name__�
__module__� __qualname__�__doc__r r$ r( r r r r r , s
r c @ �@ e Zd ZdZdd� Zdd� Zdd� Zdd � Zd
d � Zd d
� Z dS )� SuccessMixinz\
Tests for the reporting of successful tests in L{twisted.trial.unittest.TestCase}.
c C s t �� | _dS ��%
Setup our test case
N)r r �resultr# r r r �setUpQ � zSuccessMixin.setUpc C s dS )z9
A successful test, used by other tests.
Nr r# r r r �test_successfulW s z SuccessMixin.test_successfulc C sX | � |jd� | � |jg � | � |jg � | � |jg � | � |jg � | � |jg � dS )zd
Utility function -- assert there is one success and the state is
plausible
� N)r � successesr! r �expectedFailures�unexpectedSuccessesr" �r �testr1 r r r �assertSuccessful\ s z SuccessMixin.assertSuccessfulc C s( | � d�}|�| j� | �|| j� dS )z�
Test that when a successful test is run, it is reported as a success,
and not as any other kind of result.
r4 N�� __class__�runr1 r; �r r: r r r �test_successfulIsReportedh s
z&SuccessMixin.test_successfulIsReportedc C s& | � � }|�| j� | �|| j� dS )zz
The test case type can be instantiated with no arguments, run, and
reported as being successful.
Nr< r? r r r �test_defaultIsSuccessfulq s z%SuccessMixin.test_defaultIsSuccessfulc C sJ | � d�}t�|�}|�| j� | �|| j� ~t�� | �|� d� dS )zF
Test that no reference is kept on a successful test.
r4 N) r= �weakref�refr> r1 r; �gc�collect�assertIdentical)r r: rC r r r �test_noReferencez s
z SuccessMixin.test_noReferenceN)
r) r* r+ r, r2 r4 r; r@ rA rG r r r r r. L s r. c @ � e Zd ZdZdS )�SynchronousSuccessTests�N
Tests for the reporting of successful tests in the synchronous case.
N�r) r* r+ r, r r r r rI � � rI c @ rH )�AsynchronousSuccessTestsrJ NrK r r r r rM � rL rM c @ r- )�SkipMethodsMixinzZ
Tests for the reporting of skipping tests in L{twisted.trial.unittest.TestCase}.
c C � | � | j� dS r/ )r �Skippingr# r r r r2 � � zSkipMethodsMixin.setUpc C � | � d� dS )z4
Assert that there are three tests.
� N�r( r# r r r �
test_counting� r3 z SkipMethodsMixin.test_countingc C �d | � | j� | �| j�� � | �| jjg � | �| jjg � | �t| jj�d� | �| jj d� dS )z�
Running a suite in which all methods are individually set to skip
produces a successful result with no recorded errors or failures, all
the skipped methods recorded as skips, and no methods recorded as
successes.
rS r N�
r r r r r r r! �lenr" r6 r# r r r � test_results� � z SkipMethodsMixin.test_resultsc C sp | � | j� | �| j� | �| j�� � | �| jjg � | �| jjg � | �t | jj
�d� | �| jj d� dS )a
Running a suite in which all methods are skipped by C{setUp} raising
L{SkipTest} produces a successful result with no recorded errors or
failures, all skipped methods recorded as skips, and no methods recorded
as successes.
� r N) r �
SkippingSetUpr r r r r r r! rX r" r6 r# r r r r$ � s zSkipMethodsMixin.test_setUpc C sF | � | j� d}| jjD ]\}}| �|�� t|�d� t|�� q dS )z(
Test that reasons work
�test_N)r r r" r �shortDescriptionrX �str)r �prefixr: �reasonr r r � test_reasons� s
"�z SkipMethodsMixin.test_reasonsc C sd | � | j� | �| j� | �| jjg�}| �dt|�� | �t|d d � | �d|d d � dS )zo
If a test method raises L{SkipTest} with no reason, a deprecation
warning is emitted.
r5 r �categoryzSDo not raise unittest.SkipTest with no arguments! Give a reason for skipping tests!�messageN) r �DeprecatedReasonlessSkipr r �
flushWarnings�test_1r rX �DeprecationWarning)r �warningsr r r � test_deprecatedSkipWithoutReason� s
�z1SkipMethodsMixin.test_deprecatedSkipWithoutReasonN)
r) r* r+ r, r2 rU rY r$ rb rj r r r r rN � s
rN c @ �( e Zd ZdZed�Zed�Zed�ZdS )�SynchronousSkipMethodTestsz�
Tests for the reporting of skipping tests in the synchronous case.
See: L{twisted.trial.test.test_tests.SkipMethodsMixin}
z/twisted.trial.test.skipping.SynchronousSkippingz4twisted.trial.test.skipping.SynchronousSkippingSetUpz?twisted.trial.test.skipping.SynchronousDeprecatedReasonlessSkipN�r) r* r+ r, r rP r\ re r r r r rl � � �rl c @ rk )�AsynchronousSkipMethodTestsz�
Tests for the reporting of skipping tests in the asynchronous case.
See: L{twisted.trial.test.test_tests.SkipMethodsMixin}
z0twisted.trial.test.skipping.AsynchronousSkippingz5twisted.trial.test.skipping.AsynchronousSkippingSetUpz@twisted.trial.test.skipping.AsynchronousDeprecatedReasonlessSkipNrm r r r r ro � rn ro c @ �8 e Zd ZdZdd� Zdd� Zdd� Zdd � Zd
d � Zd S )
�SkipClassesMixinzQ
Test the class skipping features of L{twisted.trial.unittest.TestCase}.
c C s | � | j� d| j_dS )r0 FN)r � SkippedClass� _setUpRanr# r r r r2 � s zSkipClassesMixin.setUpc C rR )zP
Skipped test methods still contribute to the total test count.
� NrT r# r r r rU r3 z SkipClassesMixin.test_countingc C s | � | j� | �| jj� dS )zP
The C{setUp} method is not called if the class is set to skip.
N)r r � assertFalserr rs r# r r r �
test_setUpRan
s z SkipClassesMixin.test_setUpRanc C rV )a
Skipped test methods don't cause C{wasSuccessful} to return C{False},
nor do they contribute to the C{errors} or C{failures} of the reporter,
or to the count of successes. They do, however, add elements to the
reporter's C{skips} list.
rt r NrW r# r r r rY rZ z SkipClassesMixin.test_resultsc C �6 | � | j� g d�}dd� | jjD �}| �||� dS )z�
Test methods which raise L{unittest.SkipTest} or have their C{skip}
attribute set to something are skipped.
)�class�skip2rx rx c S s g | ]\}}|�qS r r )�.0r: ra r r r �
<listcomp>' s z1SkipClassesMixin.test_reasons.<locals>.<listcomp>N)r r r" r �r �expectedReasons� reasonsGivenr r r rb s z SkipClassesMixin.test_reasonsN) r) r* r+ r, r2 rU rv rY rb r r r r rq � s rq c @ � e Zd ZdZed�ZdS )�SynchronousSkipClassTestsz
Test the class skipping features in the synchronous case.
See: L{twisted.trial.test.test_tests.SkipClassesMixin}
z3twisted.trial.test.skipping.SynchronousSkippedClassN�r) r* r+ r, r rr r r r r r� + � r� c @ r )�AsynchronousSkipClassTestsz�
Test the class skipping features in the asynchronous case.
See: L{twisted.trial.test.test_tests.SkipClassesMixin}
z4twisted.trial.test.skipping.AsynchronousSkippedClassNr� r r r r r� 5 r� r� c @ sH e Zd ZdZdd� Zdd� Zdd� Zdd � Zd
d � Zd d
� Z dd� Z
dS )� TodoMixinzv
Tests for the individual test method I{expected failure} features of
L{twisted.trial.unittest.TestCase}.
c C rO r/ )r �Todor# r r r r2 E rQ zTodoMixin.setUpc C rR )z9
Ensure that we've got three test cases.
rS NrT r# r r r rU K r3 zTodoMixin.test_countingc C s� | � | j� | �| j�� � | �| jjg � | �| jjg � | �| jjg � | �t| jj �d� | �t| jj
�d� | �| jj d� dS )a�
Running a suite in which all methods are individually marked as expected
to fail produces a successful result with no recorded errors, failures,
or skips, all methods which fail and were expected to fail recorded as
C{expectedFailures}, and all methods which pass but which were expected
to fail recorded as C{unexpectedSuccesses}. Additionally, no tests are
recorded as successes.
r[ r5 r N� r r r r r r r! r" rX r7 r8 r6 r# r r r rY Q � zTodoMixin.test_resultsc C �6 | � | j� ddg}dd� | jjD �}| �||� dS )�E
Ensure that expected failures are handled properly.
�todo1�todo2c S � g | ]\}}}|j �qS r �ra �rz �t�e�rr r r r{ i � z3TodoMixin.test_expectedFailures.<locals>.<listcomp>N�r r r7 r r| r r r �test_expectedFailuresc � z TodoMixin.test_expectedFailuresc C s4 | � | j� dg}dd� | jjD �}| �||� dS )�>
Ensure that unexpected successes are caught.
�todo3c S � g | ]\}}|j �qS r r� �rz r� r� r r r r{ r � z6TodoMixin.test_unexpectedSuccesses.<locals>.<listcomp>N�r r r8 r r| r r r �test_unexpectedSuccessesl s z"TodoMixin.test_unexpectedSuccessesc C s� | � | j� | �| j� | �| j�� � | �t| jj�d� | �| jj g � | �| jj
g � | �t| jj �d� | �t| jj �d� | �| jj
d� dS )z|
C{setUp} is excluded from the failure expectation defined by a C{todo}
attribute on a test method.
r5 r N)r � SetUpTodor r ru r r rX r r! r" r7 r8 r6 r# r r r �test_expectedSetUpFailureu s z#TodoMixin.test_expectedSetUpFailurec C s� | � | j� | �| j� | �| j�� � | �t| jj�d� | �| jj g � | �| jj
g � | �t| jj �d� | �t| jj �d� | �| jj
d� dS )z
C{tearDown} is excluded from the failure expectation defined by a C{todo}
attribute on a test method.
r5 r N)r � TearDownTodor r ru r r rX r r! r" r7 r8 r6 r# r r r � test_expectedTearDownFailure� s z&TodoMixin.test_expectedTearDownFailureN) r) r* r+ r, r2 rU rY r� r� r� r� r r r r r� ? s r� c @ rk )�SynchronousTodoTestszx
Test the class skipping features in the synchronous case.
See: L{twisted.trial.test.test_tests.TodoMixin}
z+twisted.trial.test.skipping.SynchronousTodoz0twisted.trial.test.skipping.SynchronousSetUpTodoz3twisted.trial.test.skipping.SynchronousTearDownTodoN�r) r* r+ r, r r� r� r� r r r r r� � �
r� c @ rk )�AsynchronousTodoTestszy
Test the class skipping features in the asynchronous case.
See: L{twisted.trial.test.test_tests.TodoMixin}
z,twisted.trial.test.skipping.AsynchronousTodoz1twisted.trial.test.skipping.AsynchronousSetUpTodoz4twisted.trial.test.skipping.AsynchronousTearDownTodoNr� r r r r r� � r� r� c @ rp )
�ClassTodoMixinzj
Tests for the class-wide I{expected failure} features of
L{twisted.trial.unittest.TestCase}.
c C rO r/ )r � TodoClassr# r r r r2 � rQ zClassTodoMixin.setUpc C rR )z8
Ensure that we've got four test cases.
rt NrT r# r r r rU � r3 z ClassTodoMixin.test_countingc C s� | � | j� | �| j�� � | �| jjg � | �| jjg � | �| jjg � | �t| jj �d� | �t| jj
�d� | �| jj d� dS )a�
Running a suite in which an entire class is marked as expected to fail
produces a successful result with no recorded errors, failures, or
skips, all methods which fail and were expected to fail recorded as
C{expectedFailures}, and all methods which pass but which were expected
to fail recorded as C{unexpectedSuccesses}. Additionally, no tests are
recorded as successes.
r[ r Nr� r# r r r rY � r� zClassTodoMixin.test_resultsc C r� )r� �methodrx c S r� r r� r� r r r r{ � r� z8ClassTodoMixin.test_expectedFailures.<locals>.<listcomp>Nr� r| r r r r� � r� z$ClassTodoMixin.test_expectedFailuresc C r� )r� r� rx c S r� r r� r� r r r r{ � r� z;ClassTodoMixin.test_unexpectedSuccesses.<locals>.<listcomp>Nr� r| r r r r� � r� z'ClassTodoMixin.test_unexpectedSuccessesN� r) r* r+ r, r2 rU rY r� r� r r r r r� � s r� c @ r )�SynchronousClassTodoTestsz�
Tests for the class-wide I{expected failure} features in the synchronous case.
See: L{twisted.trial.test.test_tests.ClassTodoMixin}
z0twisted.trial.test.skipping.SynchronousTodoClassN�r) r* r+ r, r r� r r r r r� � r� r� c @ r )�AsynchronousClassTodoTestsz�
Tests for the class-wide I{expected failure} features in the asynchronous case.
See: L{twisted.trial.test.test_tests.ClassTodoMixin}
z1twisted.trial.test.skipping.AsynchronousTodoClassNr� r r r r r� � r� r� c @ rp )
�StrictTodoMixinz�
Tests for the I{expected failure} features of
L{twisted.trial.unittest.TestCase} in which the exact failure which is
expected is indicated.
c C rO r/ )r �
StrictTodor# r r r r2 rQ zStrictTodoMixin.setUpc C rR )z3
Assert there are seven test cases
� NrT r# r r r rU r3 z StrictTodoMixin.test_countingc C s� | � | j� | �| j�� � | �t| jj�d� | �t| jj�d� | �t| jj�d� | �t| jj �d� | �| jj
d� | �| jj g � dS )z�
A test method which is marked as expected to fail with a particular
exception is only counted as an expected failure if it does fail with
that exception, not if it fails with some other exception.
r[ r5 rS r N) r r ru r r rX r r! r7 r8 r6 r" r# r r r rY
s z StrictTodoMixin.test_resultsc C rw )r� )r� r� �todo5c S r� r r� r� r r r r{ " r� z9StrictTodoMixin.test_expectedFailures.<locals>.<listcomp>Nr� �r r} �
reasonsGottenr r r r� r� z%StrictTodoMixin.test_expectedFailuresc C s: | � | j� tgdfg}dd� | jjD �}| �||� dS )r� �todo7c S s g | ]
\}}|j |jf�qS r )r ra r� r r r r{ + s �z<StrictTodoMixin.test_unexpectedSuccesses.<locals>.<listcomp>N)r r � RuntimeErrorr8 r r� r r r r� % s �z(StrictTodoMixin.test_unexpectedSuccessesNr� r r r r r� � s r� c @ r )�SynchronousStrictTodoTestsz�
Tests for the expected failure case when the exact failure that is expected
is indicated in the synchronous case
See: L{twisted.trial.test.test_tests.StrictTodoMixin}
z1twisted.trial.test.skipping.SynchronousStrictTodoN�r) r* r+ r, r r� r r r r r� 1 � r� c @ r )�AsynchronousStrictTodoTestsz�
Tests for the expected failure case when the exact failure that is expected
is indicated in the asynchronous case
See: L{twisted.trial.test.test_tests.StrictTodoMixin}
z2twisted.trial.test.skipping.AsynchronousStrictTodoNr� r r r r r� < r� r� c @ r ) �ReactorCleanupTestszc
Tests for cleanup and reporting of reactor event sources left behind by test
methods.
c C s t �t� �| _t�� | _dS r/ )r �Reporterr r1 r r r r# r r r r2 M s zReactorCleanupTests.setUpc C s^ | j �d�}|�| j� | �| j�� � | �| jjd� | jjd d }| � |�
t j �� dS )zm
Trial reports a L{util.DirtyReactorAggregateError} if a test leaves
sockets behind.
z@twisted.trial.test.erroneous.SocketOpenTest.test_socketsLeftOpenr5 r N)
r �
loadByNamer> r1 ru r r r6 r r �checkr
�DirtyReactorAggregateError�r r �failurer r r �test_leftoverSocketsT s � z(ReactorCleanupTests.test_leftoverSocketsc C s\ t �d�}|�| j� | �| j�� � | jjd d }| �| jjd� | � |�
t j �� dS )z�
Trial reports a L{util.DirtyReactorAggregateError} and fails the test
if a test leaves a L{DelayedCall} hanging.
�test_leftoverPendingCallsr r5 N)
r r� r> r1 ru r r r r6 r r� r
r� r� r r r r� e s
z-ReactorCleanupTests.test_leftoverPendingCallsN)r) r* r+ r, r2 r� r� r r r r r� G s
r� c @ �0 e Zd ZdZdd� Zdd� Zdd� Zdd � Zd
S ) � FixtureMixinzB
Tests for fixture helper methods (e.g. setUp, tearDown).
c C s t �� | _ t�� | _dS r/ )r r� r r r r# r r r r2 w s
zFixtureMixin.setUpc C s` | j �| j�}|�| j� | �t| jj�dk� | �| jjd d j t
j � | � d| jj
� dS )zO
When setUp fails, the error is recorded in the result object.
r r5 N)r r �TestFailureInSetUpr> r r rX r �assertIsInstance�valuer � FoolishErrorr r6 r r r r �test_brokenSetUp~ s
z FixtureMixin.test_brokenSetUpc C s` | j �| j�}|�| j� | jj}| �t|�dk� | �|d d j t
j � | � d| jj
� dS )zR
When tearDown fails, the error is recorded in the result object.
r r5 N)r r �TestFailureInTearDownr> r r r rX r� r� r r� r r6 )r r r r r r �test_brokenTearDown� s z FixtureMixin.test_brokenTearDownc C s� | j �| j�}t|�d }| �|j� |�| j� | jj}| � t
|�dk� | � |d d j t
j� | �d| jj� | � |j� dS )zP
L{SynchronousTestCase.tearDown} runs when a test method fails.
r r5 N)r r �TestFailureButTearDownRuns�listru �tornDownr> r r r rX r� r� r r� r r6 )r r �caser r r r � test_tearDownRunsOnTestFailure� s z+FixtureMixin.test_tearDownRunsOnTestFailureN)r) r* r+ r, r2 r� r� r� r r r r r� r s
r� c @ rk )�SynchronousFixtureTestsz�
Tests for broken fixture helper methods in the synchronous case
See: L{twisted.trial.test.test_tests.FixtureMixin}
z:twisted.trial.test.erroneous.SynchronousTestFailureInSetUpz=twisted.trial.test.erroneous.SynchronousTestFailureInTearDownzBtwisted.trial.test.erroneous.SynchronousTestFailureButTearDownRunsN�r) r* r+ r, r r� r� r� r r r r r� � � ���r� c @ rk )�AsynchronousFixtureTestsz�
Tests for broken fixture helper methods in the asynchronous case
See: L{twisted.trial.test.test_tests.FixtureMixin}
z;twisted.trial.test.erroneous.AsynchronousTestFailureInSetUpz>twisted.trial.test.erroneous.AsynchronousTestFailureInTearDownzCtwisted.trial.test.erroneous.AsynchronousTestFailureButTearDownRunsNr� r r r r r� � r� r� c @ s0 e Zd ZdZed�Zed�Zed�Zed�ZdS )� AsynchronousSuppressionTestsz�
Tests for the warning suppression features of
L{twisted.trial.unittest.TestCase}
See L{twisted.trial.test.test_suppression.SuppressionMixin}
z?twisted.trial.test.suppression.AsynchronousTestSetUpSuppressionzBtwisted.trial.test.suppression.AsynchronousTestTearDownSuppressionz:twisted.trial.test.suppression.AsynchronousTestSuppressionz;twisted.trial.test.suppression.AsynchronousTestSuppression2N) r) r* r+ r, r �TestSetUpSuppression�TestTearDownSuppression�TestSuppression�TestSuppression2r r r r r� � s ����r� c @ sB e Zd ZdZG dd� dej�Zdd� Zdd� Zdd � Z d
d � Z
d S )
�GCMixinz�
I provide a few mock tests that log setUp, tearDown, test execution and
garbage collection. I'm used to test whether gc.collect gets called.
c @ r ) zGCMixin.BasicTestz#
Mock test to run.
c C rR )z$
Mock setUp
r2 N��_logr# r r r r2 � r3 zGCMixin.BasicTest.setUpc C rR )z(
Mock test case
r: Nr� r# r r r �test_foo� r3 zGCMixin.BasicTest.test_fooc C rR )z,
Mock tear tearDown
�tearDownNr� r# r r r r� � r3 zGCMixin.BasicTest.tearDownN)r) r* r+ r, r2 r� r� r r r r � BasicTest� s
r� c C s | j �|� dS )z
Log function
N)�_collectCalled�append)r �msgr r r r� � rQ z GCMixin._logc C rR )zFake gc.collectrE Nr� r# r r r rE s zGCMixin.collectc C s$ g | _ | j| j_tj| _| jt_dS r/ )r� r� r� rD rE � _oldCollectr# r r r r2 s
z
GCMixin.setUpc C s | j t_dS �z$
Tear down the test
N)r� rD rE r# r r r r� s zGCMixin.tearDownN) r) r* r+ r, r �SynchronousTestCaser� r� rE r2 r� r r r r r� � s r� c @ � e Zd ZdZdd� ZdS )� GarbageCollectionDefaultTestsz@
By default, tests should not force garbage collection.
c C s2 | � d�}t�� }|�|� | �| jg d�� dS )zH
By default, tests should not force garbage collection.
r� )r2 r: r� N)r� r r r> r r� r9 r r r �test_collectNotDefault s
z4GarbageCollectionDefaultTests.test_collectNotDefaultN)r) r* r+ r, r� r r r r r� � r� c @ r� )�GarbageCollectionTestsz-
Test that, when force GC, it works.
c C s: t �d�}t|�}t�� }|�|� | �| jg d�� dS )zG
test gc.collect is called before and after each test.
r� )rE r2 r: r� rE N)r� r� r r r r> r r� r9 r r r �test_collectCalled* s
�z)GarbageCollectionTests.test_collectCalledN)r) r* r+ r, r� r r r r r� % r� r� c @ s< e Zd ZdZdd� Zdd� Ze�ed�dd� �Z d d
� Z
d S ) �UnhandledDeferredTestsz\
Test what happens when we have an unhandled deferred left around after
a test.
c C s( ddl m} t�� t|�d��| _dS )r0 r )�weird�test_unhandledDeferredN)�twisted.trial.testr� rD �disabler � TestBleeding�test1)r r� r r r r2 = s
�z UnhandledDeferredTests.setUpc C s* t �� }| �|� | �t|j�dd� dS )zo
Forcing garbage collection should cause unhandled Deferreds to be
reported as errors.
r5 z(Unhandled deferred passed without noticeN)r r r� r rX r )r r1 r r r �test_isReportedI s
�z&UnhandledDeferredTests.test_isReportedz GC works differently on PyPy.c C sP t �� }| �|� | �� ttj�}| �|dd� | �� }| �t|�dd� dS )z�
Forcing garbage collection in the test should mean that there are
no unreachable cycles immediately after the test completes.
r z unreachable cycle still existedz Errors logged after gc.collectN)r r r� �flushLoggedErrorsrX rD �garbager )r r1 �n�xr r r �test_doesntBleedT s
z'UnhandledDeferredTests.test_doesntBleedc C s t �� t �� | �� dS r� )rD rE �enabler� r# r r r r� e s z UnhandledDeferredTests.tearDownN) r) r* r+ r, r2 r� r �skipIfr r� r� r r r r r� 7 s
r� c sP e Zd ZdZ� fdd�Zdd� Zdd� Zdd � Zd
d � Zd d
� Z dd� Z
� Z S )�AddCleanupMixinz1
Test the addCleanup method of TestCase.
c s" t � �� t�� | _| �� | _dS r/ )�superr2 r r r1 �
AddCleanupr: r# �r= r r r2 s s
zAddCleanupMixin.setUpc C �D | j j| j _| j �| j jd� | j �| j� | �ddg| j j� dS )zQ
Callables added with C{addCleanup} are run even if setUp fails.
�foor2 N) r: � brokenSetUpr2 �
addCleanupr� r> r1 r �logr# r r r �!test_addCleanupCalledIfSetUpFails{ s z1AddCleanupMixin.test_addCleanupCalledIfSetUpFailsc C r� )z�
Callables added with C{addCleanup} are run even if setUp raises
L{SkipTest}. This allows test authors to reliably provide clean up
code using C{addCleanup}.
r� r2 N) r: �
skippingSetUpr2 r r� r> r1 r r r# r r r �!test_addCleanupCalledIfSetUpSkips� s z1AddCleanupMixin.test_addCleanupCalledIfSetUpSkipsc C sJ | j �| j jd� | j �| j jd� | j �| j� | �g d�| j j� dS )z~
Callables added with C{addCleanup} should be called before C{tearDown}
in reverse order of addition.
r� �bar�r2 �runTestr r� r� N�r: r r� r> r1 r r r# r r r �#test_addCleanupCalledInReverseOrder� s z3AddCleanupMixin.test_addCleanupCalledInReverseOrderc C st | j �| j jd� | j �| j� | �| j�� � | �dt| jj �� | jj \\}}| �|| j � | �|�
� d� dS )z�
Errors raised in cleanup functions should be treated like errors in
C{tearDown}. They should be added as errors and fail the test. Skips,
todos and failures are all treated as errors.
r� r5 N) r: r �failr> r1 ru r r rX r �getErrorMessage�r r: �errorr r r � test_errorInCleanupIsCaptured� s z-AddCleanupMixin.test_errorInCleanupIsCapturedc C s� | j �| j jd� | j �| j jd� | j �| j� | �g d�| j j� | �dt| jj �� | jj \\}}| �|| j � | �|�
� d� dS )zq
If a cleanup raises an error then that does not stop the other
cleanups from being run.
r� r )r2 r r� r� r5 N) r: r r� r
r> r1 r r rX r r r r r r �&test_cleanupsContinueRunningAfterError� s z6AddCleanupMixin.test_cleanupsContinueRunningAfterErrorc C s� | j �| j jd� | j �| j jd� | j �| j� | �g d�| j j� | �dt| jj�� | jj\\}}\}}| �|| j � | �|| j � | �|� � d� | �|� � d� dS )zm
If more than one cleanup fails, then the test should fail with more
than one error.
r� r )r2 r r� r[ N)
r: r r
r> r1 r r rX r r )r r� �error1�test2�error2r r r �test_multipleErrorsReported� s z+AddCleanupMixin.test_multipleErrorsReported) r) r* r+ r, r2 r r r r r r �
__classcell__r r r� r r� n s
r� c @ r )�SynchronousAddCleanupTestsz�
Test the addCleanup method of TestCase in the synchronous case
See: L{twisted.trial.test.test_tests.AddCleanupMixin}
z1twisted.trial.test.skipping.SynchronousAddCleanupN)r) r* r+ r, r r� r r r r r � r� r c @ s e Zd ZdZed�Zdd� ZdS )�AsynchronousAddCleanupTestsz�
Test the addCleanup method of TestCase in the asynchronous case
See: L{twisted.trial.test.test_tests.AddCleanupMixin}
z2twisted.trial.test.skipping.AsynchronousAddCleanupc sR � fdd�}� j �� j jd� � j �|d� � j �� j� � �g d�� j j� dS )z�
If an added callable returns a L{Deferred}, then the test should wait
until that L{Deferred} has fired before running the next cleanup
method.
c s& t �� }t�d|j| � |�� jj�S )Nr )r �Deferredr � callLater�callback� addCallbackr: r� )rd �dr# r r �cleanup� s zMAsynchronousAddCleanupTests.test_addCleanupWaitsForDeferreds.<locals>.cleanupr� r r Nr )r r r r# r � test_addCleanupWaitsForDeferreds� s
z<AsynchronousAddCleanupTests.test_addCleanupWaitsForDeferredsN)r) r* r+ r, r r� r r r r r r � s r c @ � e Zd ZdZdd� Zdd� ZdS )�SuiteClearingMixinzM
Tests for our extension that allows us to clear out a L{TestSuite}.
c C �B t �� }|�| �� � | �d|�� � t|� | �d|�� � dS )z_
Calling L{_clearSuite} on a populated L{TestSuite} removes
all tests.
r5 r N)r � TestSuite�addTest�TestCaser r% r r r r r �test_clearSuite� s
z"SuiteClearingMixin.test_clearSuitec C r )z�
Calling L{_clearSuite} on a populated standard library
L{TestSuite} removes all tests.
This test is important since C{_clearSuite} operates by mutating
internal variables.
r5 r N)r r! r" r# r r% r r r r r �test_clearPyunitSuite� s
z(SuiteClearingMixin.test_clearPyunitSuiteN)r) r* r+ r, r$ r% r r r r r � s r c @ � e Zd ZdZejZdS )� SynchronousSuiteClearingTestsz�
Tests for our extension that allows us to clear out a L{TestSuite} in the
synchronous case.
See L{twisted.trial.test.test_tests.SuiteClearingMixin}
N�r) r* r+ r, r r� r# r r r r r' �
r' c @ � e Zd ZdZejZdS )� AsynchronousSuiteClearingTestsz�
Tests for our extension that allows us to clear out a L{TestSuite} in the
asynchronous case.
See L{twisted.trial.test.test_tests.SuiteClearingMixin}
N�r) r* r+ r, r r# r r r r r+ r) r+ c @ sh e Zd ZdZdd� Zdd� Zdd� Zdd � Zd
d � Zd d
� Z dd� Z
dd� Z dd� Z dd� Z
dd� ZdS )�TestDecoratorMixinz1
Tests for our test decoration features.
c C sd | � |j|jd� t|dd�}t|dd�}| �||� || u r%du r0n dS | �||� dS dS )zB
Assert that the given decorated tests are equal.
�Different class�
_originalTestN)r r= �getattrrF )r �observed�expected�observedOriginal�expectedOriginalr r r �assertTestsEqual' s �z#TestDecoratorMixin.assertTestsEqualc C sr | � |j|jd� | � t|j�t|j�d� t|j|j�D ]\}}t|dd�dur0| �||� q | �||� q dS )zS
Assert that the given test suites with decorated tests are equal.
r. zDifferent number of tests.�_testsN)r r= rX r6 �zipr0 �assertSuitesEqualr5 )r r1 r2 � observedTest� expectedTestr r r r8 2 s ��z$TestDecoratorMixin.assertSuitesEqualc C s@ | � � }t�|�}ddlm} |� }|�|� | �|j|� dS )z�
For decorated tests, C{run} uses a result adapter that preserves the
test decoration for calls to C{addError}, C{startTest} and the like.
See L{reporter._AdaptedReporter}.
r ��LoggingReporterN)r# r �
TestDecorator� twisted.trial.test.test_reporterr< r> r5 r: �r r: �
decoratedTestr< r1 r r r � test_usesAdaptedReporterWithRun@ s
z2TestDecoratorMixin.test_usesAdaptedReporterWithRunc C s> | � � }t�|�}ddlm} |� }||� | �|j|� dS )z�
For decorated tests, C{__call__} uses a result adapter that preserves
the test decoration for calls to C{addError}, C{startTest} and the
like.
See L{reporter._AdaptedReporter}.
r r; N)r# r r= r> r< r5 r: r? r r r � test_usesAdaptedReporterWithCallP s
z3TestDecoratorMixin.test_usesAdaptedReporterWithCallc C s, | � � }t�|tj�}| �t�|�|� dS )z�
Calling L{decorate} on a single test case returns the test case
decorated with the provided decorator.
N�r# r �decorater= r5 )r r: r@ r r r �test_decorateSingleTesta s z*TestDecoratorMixin.test_decorateSingleTestc C s@ | � � }t�|g�}t�|tj�}| �|t�t�|�g�� dS )z�
Calling L{decorate} on a test suite will return a test suite with
each test decorated with the provided decorator.
N�r# r r! rD r= r8 �r r: r r@ r r r �test_decorateTestSuitej � �z)TestDecoratorMixin.test_decorateTestSuitec C sZ | � � }t�|g�}t�|tj�}| �|t�t�|�g�� | �|t�t�|�g�� dS )zU
Calling L{decorate} on a test suite will mutate the original suite.
NrF rG r r r �#test_decorateInPlaceMutatesOriginalv s ��z6TestDecoratorMixin.test_decorateInPlaceMutatesOriginalc C s` t tdd�}|du rt�d��| �� }t�|g�}||�}t�|tj� ||�}| �||� dS )ac
When decorating a test suite in-place, the number of references to the
test objects in that test suite should stay the same.
Previously, L{unittest.decorate} recreated a test suite, so the
original suite kept references to the test objects. This test is here
to ensure the problem doesn't reappear again.
� getrefcountNz*getrefcount not supported on this platform) r0 �sysr �SkipTestr# r! rD r= r )r rK r: r �count1�count2r r r � test_decorateTestSuiteReferences� s
z3TestDecoratorMixin.test_decorateTestSuiteReferencesc C sT | � � }t�t�|g�g�}t�|tj�}t�t�t�|�g�g�}| �||� dS )z�
Calling L{decorate} on a test suite with nested suites will return a
test suite that maintains the same structure, but with all tests
decorated.
NrF )r r: r r@ r2 r r r � test_decorateNestedTestSuite� s �z/TestDecoratorMixin.test_decorateNestedTestSuitec C s: | � � }t�|tj�}t�|tj�}| �|t�|�� dS )z�
Calling L{decorate} on a test suite with already-decorated tests
decorates all of the tests in the suite again.
NrC )r r: r@ �redecoratedTestr r r �test_decorateDecoratedSuite� s z.TestDecoratorMixin.test_decorateDecoratedSuitec C s@ | � � }t�|g�}t�|tj�}| �|t�t�|�g�� dS )z�
Tests can be in non-standard suites. L{decorate} preserves the
non-standard suites when it decorates the tests.
N)r# r �DestructiveTestSuiter rD r= r8 )r r: r � decoratedr r r �test_decoratePreservesSuite� rI z.TestDecoratorMixin.test_decoratePreservesSuiteN)r) r* r+ r, r5 r8 rA rB rE rH rJ rP rQ rS rV r r r r r- " s
r- c @ r& )� SynchronousTestDecoratorTestsz�
Tests for our test decoration features in the synchronous case.
See L{twisted.trial.test.test_tests.TestDecoratorMixin}
Nr( r r r r rW � �
rW c @ r* )� AsynchronousTestDecoratorTestsz�
Tests for our test decoration features in the asynchronous case.
See L{twisted.trial.test.test_tests.TestDecoratorMixin}
Nr, r r r r rY � rX rY c @ r- )�MonkeyPatchMixinzF
Tests for the patch() helper method in L{unittest.TestCase}.
c C s" d| _ d| _| j | _| �� | _dS )r0 �original�patchedN)�
originalValue� patchedValue�
objectToPatchr# r: r# r r r r2 � s zMonkeyPatchMixin.setUpc C s& | j �| d| j� | �| j| j� dS )zi
Calling C{patch()} on a test monkey patches the specified object and
attribute.
r_ N)r: �patchr^ r r_ r# r r r �
test_patch� s zMonkeyPatchMixin.test_patchc C s6 | j �| d| j� | j �t�� � | �| j| j� dS )zw
Any monkey patches introduced by a test using C{patch()} are reverted
after the test has run.
r_ N) r: r` r^ r> r r� r r_ r] r# r r r �test_patchRestoredAfterRun� s z+MonkeyPatchMixin.test_patchRestoredAfterRunc C s. | j �| d| j�}|�� | �| j| j� dS )z�
C{patch()} return a L{monkey.MonkeyPatcher} object that can be used to
restore the original values before the end of the test.
r_ N)r: r` r^ �restorer r_ r] �r r` r r r �test_revertDuringTest� s z&MonkeyPatchMixin.test_revertDuringTestc C s6 | j �| d| j�}|�� |�� | �| j| j� dS )zq
The returned L{monkey.MonkeyPatcher} object can re-apply the patch
during the test run.
r_ N)r: r` r^ rc r r_ rd r r r �test_revertAndRepatch� s z&MonkeyPatchMixin.test_revertAndRepatchc C sd | j �| d| j� | �| j| j� | j �| dd� | �| jd� | j �t�� � | �| j| j� dS )zW
Successive patches are applied and reverted just like a single patch.
r_ z second valueN) r: r` r^ r r_ r> r r� r] r# r r r �test_successivePatches s z'MonkeyPatchMixin.test_successivePatchesN)
r) r* r+ r, r2 ra rb re rf rg r r r r rZ � s
rZ c @ r& )�SynchronousMonkeyPatchTestsz�
Tests for the patch() helper method in the synchronous case.
See L{twisted.trial.test.test_tests.MonkeyPatchMixin}
Nr( r r r r rh rX rh c @ r* )� AsynchronousMonkeyPatchTestsz�
Tests for the patch() helper method in the asynchronous case.
See L{twisted.trial.test.test_tests.MonkeyPatchMixin}
Nr, r r r r ri rX ri c @ r� ) �IterateTestsMixinz]
L{_iterateTests} returns a list of all test cases in a test suite or test
case.
c C s" | � � }| �|gtt|��� dS )zj
L{_iterateTests} on a single test case returns a list containing that
test case.
N)r# r r� r
r? r r r �test_iterateTestCase) s z&IterateTestsMixin.test_iterateTestCasec C s. | � � }t�|g�}| �|gtt|��� dS )z�
L{_iterateTests} on a test suite that contains a single test case
returns a list containing that test case.
N�r# r r! r r� r
�r r: r r r r � test_iterateSingletonTestSuite1 s z0IterateTestsMixin.test_iterateSingletonTestSuitec C s6 | � � }t�t�|g�g�}| �|gtt|��� dS )zP
L{_iterateTests} returns tests that are in nested test suites.
Nrl rm r r r �test_iterateNestedTestSuite: s z-IterateTestsMixin.test_iterateNestedTestSuitec C s: | � � }t�t�|g�| g�}| �|| gtt|��� dS )zU
L{_iterateTests} returns tests in left-to-right, depth-first order.
Nrl rm r r r �#test_iterateIsLeftToRightDepthFirstB s z5IterateTestsMixin.test_iterateIsLeftToRightDepthFirstN)r) r* r+ r, rk rn ro rp r r r r rj # s rj c @ r& )� SynchronousIterateTestsTestsz�
Check that L{_iterateTests} returns a list of all test cases in a test suite
or test case for synchronous tests.
See L{twisted.trial.test.test_tests.IterateTestsMixin}
Nr( r r r r rq K r) rq c @ r* )� AsynchronousIterateTestsTestsz�
Check that L{_iterateTests} returns a list of all test cases in a test suite
or test case for asynchronous tests.
See L{twisted.trial.test.test_tests.IterateTestsMixin}
Nr, r r r r rr V r) rr c @ r )�TrialGeneratorFunctionTestsz=
Tests for generator function methods in test cases.
c C � G dd� dt j�}|d�}t�� }|�|� | �t|j�d� | �t|j�d� | � d|jd d j
j d � | � d|jd d j
j d � | � d|jd d j
j d � d S )
z�
In a TestCase, a test method which is a generator function is reported
as an error, as such a method will never run assertions.
c @ r� )zTTrialGeneratorFunctionTests.test_errorOnGeneratorFunction.<locals>.GeneratorTestCasez?
A fake TestCase for testing purposes.
c s � � | � d� dV dS �zt
A method which is also a generator function, for testing
purposes.
z this should never be reachedN�r
r# r r r �test_generatorq � �
zcTrialGeneratorFunctionTests.test_errorOnGeneratorFunction.<locals>.GeneratorTestCase.test_generatorN�r) r* r+ r, rx r r r r �GeneratorTestCasel r� r{ rx r r5 z GeneratorTestCase.test_generatorz+GeneratorTestCase testMethod=test_generator�4is a generator function and therefore will never runN) r r# r r r> r rX r! r �assertInr� �args)r r{ �testCaser1 r r r � test_errorOnGeneratorFunctionf s"
���z9TrialGeneratorFunctionTests.test_errorOnGeneratorFunctionc C rt )
z�
In a SynchronousTestCase, a test method which is a generator function
is reported as an error, as such a method will never run assertions.
c @ r� )zrTrialGeneratorFunctionTests.test_synchronousTestCaseErrorOnGeneratorFunction.<locals>.GeneratorSynchronousTestCasezJ
A fake SynchronousTestCase for testing purposes.
c s ru rv rw r# r r r rx � ry z�TrialGeneratorFunctionTests.test_synchronousTestCaseErrorOnGeneratorFunction.<locals>.GeneratorSynchronousTestCase.test_generatorNrz r r r r � GeneratorSynchronousTestCase� r� r� rx r r5 z+GeneratorSynchronousTestCase.test_generatorz6GeneratorSynchronousTestCase testMethod=test_generatorr| N) r r� r r r> r rX r! r r} r� r~ )r r� r r1 r r r �0test_synchronousTestCaseErrorOnGeneratorFunction� s$
���zLTrialGeneratorFunctionTests.test_synchronousTestCaseErrorOnGeneratorFunctionN)r) r* r+ r, r� r� r r r r rs a s $rs )Ir, rD rL r r rB �ior �twisted.internetr r �twisted.python.compatr �twisted.python.reflectr �
twisted.trialr r r
�twisted.trial._asyncrunnerr r r
r� r �#twisted.trial.test.test_suppressionr r r. r� rI r# rM rN rl ro rq r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r r r r' r+ r- rW rY rZ rh ri rj rq rr rs r r r r �<module> st ;I3
X 7
7 +377X
!
>
(