File: //usr/lib/python3/dist-packages/twisted/trial/test/__pycache__/test_assertions.cpython-38.pyc
U
W[&� � @ sj d Z ddlmZmZ ddlZddlZddlmZ ddl m
Z
m Z m Z ddl
mZ ddlmZmZ ddlmZ dd lmZ dd
lmZmZmZ G d d � d ee�ZG d
d� de�ZG dd� dej �Z G dd� dej �Z G dd� dej �Z G dd� dej �Z!G dd� dej �Z"G dd� dej �Z#G dd � d ej �Z$G d d � d ej �Z%ee%j&�d d � �Z'ee%j&d!d"�d#d$� �Z(dS )%a�
Tests for assertions provided by C{SynchronousTestCase} and C{TestCase},
provided by L{twisted.trial.unittest}.
L{TestFailureTests} demonstrates that L{SynchronousTestCase.fail} works, so that
is the only method on C{twisted.trial.unittest.SynchronousTestCase} that is
initially assumed to work. The test classes are arranged so that the methods
demonstrated to work earlier in the file are used by those later in the file
(even though the runner will probably not run the tests in this order).
� )�division�absolute_importN)� FancyEqMixin)�prefixedMethods�accumulateMethods�fullyQualifiedName��
deprecated)�Version�getVersionString)�Failure)�unittest)�Deferred�fail�succeedc @ s e Zd ZdZdd� Zdd� ZdS )� MockEquality��namec C s
|| _ d S �Nr )�selfr � r �D/usr/lib/python3/dist-packages/twisted/trial/test/test_assertions.py�__init__ s zMockEquality.__init__c C s d| j f S )NzMockEquality(%s)r �r r r r �__repr__$ s zMockEquality.__repr__N)�__name__�
__module__� __qualname__ZcompareAttributesr r r r r r r s r c @ s e Zd ZdZdd� Ze ZZdS )�ComparisonErrorzH
An object which raises exceptions from its comparison methods.
c C s t d��d S )NzComparison is broken)�
ValueError)r �otherr r r �_error, s zComparisonError._errorN)r r r �__doc__r! �__eq__�__ne__r r r r r ( s r c @ s: e Zd ZdZG dd� dej�Zdd� Zdd� Zdd � Z d
S ) �TestFailureTestsa�
Tests for the most basic functionality of L{SynchronousTestCase}, for
failing tests.
This class contains tests to demonstrate that L{SynchronousTestCase.fail}
can be used to fail a test, and that that failure is reflected in the test
result object. This should be sufficient functionality so that further
tests can be built on L{SynchronousTestCase} instead of
L{unittest.TestCase}. This depends on L{unittest.TestCase} working.
c @ s e Zd Zdd� ZdS )z TestFailureTests.FailingTestc C s | � d� d S )NzThis test fails.�r r r r r �
test_fails? s z'TestFailureTests.FailingTest.test_failsN)r r r r' r r r r � FailingTest> s r( c C sD t | jj | jj g}t�� | _| j�d�|��| _t | j�d | _
dS )zo
Load a suite of one test which can be used to exercise the failure
handling behavior.
�.r N) r � __class__r( �pyunitZ
TestLoader�loaderZloadTestsFromName�join�suite�list�test)r Z
componentsr r r �setUpC s �
zTestFailureTests.setUpc
C sV z| j �d� W n6 | j jk
rF } z| �dt|�� W 5 d}~X Y n X | �d� dS )z}
L{SynchronousTestCase.fail} raises
L{SynchronousTestCase.failureException} with the given argument.
ZfailedNzRSynchronousTestCase.fail method did not raise SynchronousTestCase.failureException)r0 r �failureException� assertEqual�str�r �resultr r r � test_failO s "�zTestFailureTests.test_failc C s^ t �� }| j�|� | �|�� � | �|jg � | �t|j �d� | �|j d d | j
� dS )z�
When a test method raises L{SynchronousTestCase.failureException}, the test is
marked as having failed on the L{TestResult}.
� r N) r+ Z
TestResultr. �run� assertFalseZ
wasSuccessfulr3 �errors�lenZfailuresr0 r5 r r r �test_failingExceptionFails^ s z+TestFailureTests.test_failingExceptionFailsN)
r r r r" r
�SynchronousTestCaser( r1 r7 r= r r r r r% 3 s
r% c @ s@ e Zd ZdZdd� Zdd� Zdd� Zdd � Zd
d � Zd d
� Z dS )�AssertFalseTestsa
Tests for L{SynchronousTestCase}'s C{assertFalse} and C{failIf} assertion
methods.
This is pretty paranoid. Still, a certain paranoia is healthy if you
are testing a unit testing framework.
@note: As of 11.2, C{assertFalse} is preferred over C{failIf}.
c C sB dddddg fD ],}||d|f �}||kr| � d|f � qdS )z�
Perform the positive case test for C{failIf} or C{assertFalse}.
@param method: The test method to test.
r � FNr � failed on %r�Did not return argument %rr& )r �method�notTruer6 r r r �_assertFalseFalsev s z"AssertFalseTests._assertFalseFalsec C s� dddddgdfD ]r}z||d|f � W nD | j k
rn } z$| �d|f t|�d||f � W 5 d}~X Y qX | �d |j|f � qdS )
z�
Perform the negative case test for C{failIf} or C{assertFalse}.
@param method: The test method to test.
r8 T�cat� �� � rA �$Raised incorrect exception on %r: %rN�Call to %s(%r) didn't fail�r2 �assertInr4 r r )r rC �true�er r r �_assertFalseTrue� s
� �z!AssertFalseTests._assertFalseTruec C s | � | j� dS )zt
L{SynchronousTestCase.failIf} returns its argument if its argument is
not considered true.
N)rE �failIfr r r r �test_failIfFalse� s z!AssertFalseTests.test_failIfFalsec C s | � | j� dS )zy
L{SynchronousTestCase.assertFalse} returns its argument if its argument
is not considered true.
N)rE r: r r r r �test_assertFalseFalse� s z&AssertFalseTests.test_assertFalseFalsec C s | � | j� dS )z�
L{SynchronousTestCase.failIf} raises
L{SynchronousTestCase.failureException} if its argument is considered
true.
N)rQ rR r r r r �test_failIfTrue� s z AssertFalseTests.test_failIfTruec C s | � | j� dS )z�
L{SynchronousTestCase.assertFalse} raises
L{SynchronousTestCase.failureException} if its argument is considered
true.
N)rQ r: r r r r �test_assertFalseTrue� s z%AssertFalseTests.test_assertFalseTrueN)
r r r r" rE rQ rS rT rU rV r r r r r? l s r? c @ s@ e Zd ZdZdd� Zdd� Zdd� Zdd � Zd
d � Zd d
� Z dS )�AssertTrueTestsa
Tests for L{SynchronousTestCase}'s C{assertTrue} and C{failUnless} assertion
methods.
This is pretty paranoid. Still, a certain paranoia is healthy if you
are testing a unit testing framework.
@note: As of 11.2, C{assertTrue} is preferred over C{failUnless}.
c C s� dddddg fD ]r}z||d|f � W nD | j k
rl } z$| �d|f t|�d||f � W 5 d}~X Y qX | �d|j|f � qdS ) z�
Perform the negative case test for C{assertTrue} and C{failUnless}.
@param method: The test method to test.
r r@ FNr rA rK rL rM )r rC rD rP r r r �_assertTrueFalse� s
� �z AssertTrueTests._assertTrueFalsec C sD dddddgdfD ],}||d|f �}||kr| � d|f � qdS ) z�
Perform the positive case test for C{assertTrue} and C{failUnless}.
@param method: The test method to test.
r8 TrF rG rH rA rB Nr& )r rC rO r6 r r r �_assertTrueTrue� s z AssertTrueTests._assertTrueTruec C s | � | j� dS )z�
L{SynchronousTestCase.assertTrue} raises
L{SynchronousTestCase.failureException} if its argument is not
considered true.
N)rX �
assertTruer r r r �test_assertTrueFalse� s z$AssertTrueTests.test_assertTrueFalsec C s | � | j� dS )z�
L{SynchronousTestCase.failUnless} raises
L{SynchronousTestCase.failureException} if its argument is not
considered true.
N)rX �
failUnlessr r r r �test_failUnlessFalse� s z$AssertTrueTests.test_failUnlessFalsec C s | � | j� dS )zt
L{SynchronousTestCase.assertTrue} returns its argument if its argument
is considered true.
N)rY rZ r r r r �test_assertTrueTrue� s z#AssertTrueTests.test_assertTrueTruec C s | � | j� dS )zt
L{SynchronousTestCase.failUnless} returns its argument if its argument
is considered true.
N)rY r\ r r r r �test_failUnlessTrue� s z#AssertTrueTests.test_failUnlessTrueN)
r r r r" rX rY r[ r] r^ r_ r r r r rW � s rW c @ sj e Zd ZdZdd� Zdd� Zdd� Zdd � Zd
d � Zd d
� Z dd� Z
dd� Z dd� Z dd� Z
dd� Zdd� Zdd� Zd d � Zd d � Zd d!� Zd"d#� Zd$d%� Zd&d'� Zd(d)� Zd*d+� Zd,d-� Zd.d/� Zd0d1� Zd2d3� Z d4d5� Z d6d7� Z d8d9� Z d:d;� Z d<d=� Z!d>d?� Z"d@dA� Z#dBdC� Z$dDdE� Z%dFdG� Z&dHdI� Z'dJdK� Z(dLdM� Z)dNdO� Z*dPdQ� Z+e,e-j.dRdS�dSk�rfdTe+_/dSS )U�SynchronousAssertionsTestsa�
Tests for L{SynchronousTestCase}'s assertion methods. That is, failUnless*,
failIf*, assert* (not covered by other more specific test classes).
Note: As of 11.2, assertEqual is preferred over the failUnlessEqual(s)
variants. Tests have been modified to reflect this preference.
This is pretty paranoid. Still, a certain paranoia is healthy if you are
testing a unit testing framework.
c C s" | � ||�}||kr | �d� d S )Nz)assertEqual should return first parameter)r3 r )r �first�second�xr r r �_testEqualPair s z)SynchronousAssertionsTests._testEqualPairc
C s� d}z| � ||� W n� | jk
r� } zrt�d�}z|� ||� W nR |jk
r� } z2d}t|�}t|�}||kr�| �d||f � W 5 d}~X Y nX W 5 d}~X Y nX |s�| �d||f � dS )z�
Assert that when called with unequal arguments, C{assertEqual} raises a
failure exception with the same message as the standard library
C{assertEqual} would have raised.
Fr1 TzExpected: %r; Got: %rNz'Call to assertEqual(%r, %r) didn't fail)r3 r2 r+ �TestCaser4 r ) r ra rb ZraisedZ
ourFailureZcaseZ theirFailureZgot�expectedr r r �_testUnequalPair s"
6
�z+SynchronousAssertionsTests._testUnequalPairc C s: | � dd� | �dd� | � dgdg� | �dgd� d S )NrF Zdogr8 �orange)rd rg r r r r �test_assertEqual_basic1 s z1SynchronousAssertionsTests.test_assertEqual_basicc C sL t d�}t d�}t d�}| �||� | �||� | �||� | �||� d S )Nra rb )r rd rg )r rc �y�zr r r �test_assertEqual_custom8 s z2SynchronousAssertionsTests.test_assertEqual_customc C s. d}| � | j| jdd|�}| �|t|�� dS )zi
When a message is passed to L{assertEqual} it is included in the error
message.
�message�foo�barN)� assertRaisesr2 r3 rN r4 )r rm � exceptionr r r �test_assertEqualMessageB s �z2SynchronousAssertionsTests.test_assertEqualMessagec C sB | � | j| jddd�}| � | j| jdd�}| �t|�t|�� dS )zz
If a message is specified as L{None}, it is not included in the error
message of L{assertEqual}.
rn ro N)rp r2 r3 r4 )r ZexceptionForNoneZexceptionWithoutr r r �test_assertEqualNoneMessageO s � �z6SynchronousAssertionsTests.test_assertEqualNoneMessagec C sf t � }dg}z| �||� W n2 | jk
r< | �d� Y n& tk
rN Y nX | �d||f � d S )Nrh z6Fail raised when ValueError ought to have been raised.z3Comparing %r and %r should have raised an exception)r r3 r2 r r )r Zapplerh r r r � test_assertEqual_incomparable] s �z8SynchronousAssertionsTests.test_assertEqual_incomparablec C s |�d S r r )r �errorr r r � _raiseErrorl s z&SynchronousAssertionsTests._raiseErrorc C s& | � t| jt�}| �t|t�d� d S )Nz?Expect failUnlessRaises to return instance of raised exception.)�failUnlessRaisesr rv rZ �
isinstance�r rc r r r � test_failUnlessRaises_expectedp s �z9SynchronousAssertionsTests.test_failUnlessRaises_expectedc C sV z| � t| jt� W n2 tk
r2 | �d� Y n | jk
rF Y n X | �d� d S )Nz9failUnlessRaises shouldn't re-raise unexpected exceptionsz4Expected exception wasn't raised. Should have failed)rw r rv � TypeErrorr r2 r r r r � test_failUnlessRaises_unexpectedv s z;SynchronousAssertionsTests.test_failUnlessRaises_unexpectedc
s` d� z| � t� fdd�� W n4 | jk
rP } z| �t|�d� W 5 d }~X Y n X | �d� d S )NrI c s � S r r r �Z returnValuer r �<lambda>� � zNSynchronousAssertionsTests.test_failUnlessRaises_noException.<locals>.<lambda>z"ValueError not raised (3 returned)z(Exception not raised. Should have failed)rw r r2 r3 r4 r �r rP r r} r �!test_failUnlessRaises_noException� s
�z<SynchronousAssertionsTests.test_failUnlessRaises_noExceptionc C sl | � | j| j| j�}| �t|| j�d| jf � z| � | j| jt�}W n | jk
r\ Y n X | �d� d S )Nz#Expected %r instance to be returnedz Should have raised exception)rw r2 rv rZ rx r r ry r r r �&test_failUnlessRaises_failureException� s ��� �zASynchronousAssertionsTests.test_failUnlessRaises_failureExceptionc C s4 t d�}| �t ��
}|�W 5 Q R X | �||j� dS )z�
If C{assertRaises} is used to create a context manager and an exception
is raised from the body of the C{with} statement then the context
manager's C{exception} attribute is set to the exception that was
raised.
�markerN)r rp �assertIsrq )r rq �contextr r r � test_assertRaisesContextExpected� s z;SynchronousAssertionsTests.test_assertRaisesContextExpectedc
C s� z"| � t�� td��W 5 Q R X W nT | jk
rv } z4t|�}djtt�d�}| �|�|�d�|�� W 5 d}~X Y n X | � d� dS )z�
If C{assertRaises} is used to create a context manager and the wrong
exception type is raised from the body of the C{with} statement then
the C{with} statement raises C{failureException} describing the
mismatch.
r� z/{type} raised instead of ValueError:
Traceback)�typez>Exception message did not begin with expected information: {0}N�:Mismatched exception type should have caused test failure.)
rp r r{ r2 r4 �formatr rZ �
startswithr )r rq rm rf r r r �"test_assertRaisesContextUnexpected� s$ �����z=SynchronousAssertionsTests.test_assertRaisesContextUnexpectedc
C sb z| � t�� W 5 Q R X W n8 | jk
rR } zt|�}| �|d� W 5 d}~X Y n X | �d� dS )z�
If C{assertRaises} is used to create a context manager and no exception
is raised from the body of the C{with} statement then the C{with}
statement raises C{failureException} describing the lack of exception.
z%ValueError not raised (None returned)Nz5Non-exception result should have caused test failure.)rp r r2 r4 r3 r )r rq rm r r r �#test_assertRaisesContextNoException� s z>SynchronousAssertionsTests.test_assertRaisesContextNoExceptionc
C s� z$| � ttf�� t� �W 5 Q R X W nx | jk
r� } zXt|�}d|k}d|k}g }|rb|�d� |rp|�d� |r�| �d�|�d� |�� W 5 d}~X Y n X | �d� dS ) z�
If the exception type passed to C{assertRaises} does not have a
C{__name__} then the context manager still manages to construct a
descriptive string for it.
r r{ z(expected ValueError in exception messagez'expected TypeError in exception messagez; z
message = {0}Nr� )
rp r r{ �AttributeErrorr2 r4 �appendr r- r� )r rq rm Z
valueErrorZ typeErrorr; r r r �test_brokenName� s"
*�z*SynchronousAssertionsTests.test_brokenNamec C s\ dgdgdg }}}| � ||�}| �||d� | �| j| j ||� | �| j| j ||� d S )Nr8 rG �)failIfEqual should return first parameter)� failIfEqualr3 rw r2 �r rc rj rk �retr r r �test_failIfEqual_basic� s � � �z1SynchronousAssertionsTests.test_failIfEqual_basicc C sX t d�}t d�}t d�}| �||�}| �||d� | �| j| j||� | �||d� d S )Nra rb Zfecundr� z"__ne__ should make these not equal)r r� r3 rw r2 r� r r r �test_failIfEqual_customEq� s � �z4SynchronousAssertionsTests.test_failIfEqual_customEqc C s( t � }t � }| �||�}| �||� dS )z�
C{failIfIdentical} returns its first argument if its first and second
arguments are not the same object.
N)�object�failIfIdenticalr3 )r rc rj r6 r r r � test_failIfIdenticalPositive s z7SynchronousAssertionsTests.test_failIfIdenticalPositivec C s t � }| �| j| j||� dS )z~
C{failIfIdentical} raises C{failureException} if its first and second
arguments are the same object.
N)r� rw r2 r� ry r r r � test_failIfIdenticalNegative s �z7SynchronousAssertionsTests.test_failIfIdenticalNegativec C s\ dgdgdg }}}| � ||�}| �||d� | �| j| j ||� | �| j| j ||� d S )Nr8 rG z1failUnlessIdentical should return first parameter)ZfailUnlessIdenticalr3 rw r2 r� r r r �test_failUnlessIdentical s � � �z3SynchronousAssertionsTests.test_failUnlessIdenticalc C sd d\}}}| � ||d� | � ||d�}| �||d� | �| j| j ||d� | �| j| j ||d� d S )N)g �?g�������?g333333�?g�������?z4failUnlessApproximates should return first parameterg�������?)ZfailUnlessApproximatesr3 rw r2 r� r r r �test_failUnlessApproximates) s
� �z6SynchronousAssertionsTests.test_failUnlessApproximatesc C s\ d}d}d}d}| � |||� | � |||�}| �||d||f � | �| j| j |||� d S )N� �A�! @�X�O @��C @z<failUnlessAlmostEqual should return first parameter (%r, %r))ZfailUnlessAlmostEqualr3 rw r2 �r Z precisionrc rj rk r� r r r �test_failUnlessAlmostEqual5 s
� �z5SynchronousAssertionsTests.test_failUnlessAlmostEqualc C sd d}d}d}d}| � |||�}| �||d||f � | �| j| j |||� | �| j| j |||� d S )Nr� r� r� r� z8failIfAlmostEqual should return first parameter (%r, %r))ZfailIfAlmostEqualr3 rw r2 r� r r r �test_failIfAlmostEqualB s(
� � �z1SynchronousAssertionsTests.test_failIfAlmostEqualc C s^ d}d}d}| � ||� | � ||�}| �||d� | �| j| j ||� | �| j| j ||� d S �NrF z the dog satz the cat satz should return first parameter)ZfailUnlessSubstringr3 rw r2 r� r r r �test_failUnlessSubstringP s � �z3SynchronousAssertionsTests.test_failUnlessSubstringc C s^ d}d}d}| � ||� | � ||�}| �||d� | �| j| j ||� | �| j| j ||� d S r� )ZfailIfSubstringr3 rw r2 r� r r r �test_failIfSubstring] s � �z/SynchronousAssertionsTests.test_failIfSubstringc C s t d�}| �||� dS )zB
L{assertIs} passes if two objects are identical.
ra N)r r� �r �ar r r �
test_assertIsj s z(SynchronousAssertionsTests.test_assertIsc C s6 t d�t d� }}| �||� | �| j| j||� dS )zE
L{assertIs} fails if two objects are not identical.
ra N)r r3 rp r2 r� �r r� �br r r �test_assertIsErrorr s z-SynchronousAssertionsTests.test_assertIsErrorc C s. t d�t d� }}| �||� | �||� dS )zI
L{assertIsNot} passes if two objects are not identical.
ra N)r r3 � assertIsNotr� r r r �test_assertIsNot{ s z+SynchronousAssertionsTests.test_assertIsNotc C s t d�}| �| j| j||� dS )zD
L{assertIsNot} fails if two objects are identical.
ra N)r rp r2 r� r� r r r �test_assertIsNotError� s z0SynchronousAssertionsTests.test_assertIsNotErrorc C s$ t dtfi �}|� }| �||� dS )z<
Test a true condition of assertIsInstance.
�AN�r� r� �assertIsInstance)r r� r� r r r �test_assertIsInstance� s z0SynchronousAssertionsTests.test_assertIsInstancec C s6 t dtfi �}t dtfi �}|� }| �|||f� dS )zR
Test a true condition of assertIsInstance with multiple classes.
r� �BNr� �r r� r� r� r r r �$test_assertIsInstanceMultipleClasses� s z?SynchronousAssertionsTests.test_assertIsInstanceMultipleClassesc C s: t dtfi �}t dtfi �}|� }| �| j| j||� dS )z6
Test an error with assertIsInstance.
r� r� N�r� r� rp r2 r� r� r r r �test_assertIsInstanceError� s z5SynchronousAssertionsTests.test_assertIsInstanceErrorc C sL t dtfi �}t dtfi �}t dtfi �}|� }| �| j| j|||f� dS )zK
Test an error with assertIsInstance and multiple classes.
r� r� �CNr� �r r� r� r� r� r r r �)test_assertIsInstanceErrorMultipleClasses� s
zDSynchronousAssertionsTests.test_assertIsInstanceErrorMultipleClassesc C s* | � | j| jdtd�}| �dt|�� dS )z�
If L{TestCase.assertIsInstance} is passed a custom message as its 3rd
argument, the message is included in the failure exception raised when
the assertion fails.
rI zSilly assertionN)rp r2 r� r4 rN )r �excr r r �"test_assertIsInstanceCustomMessage� s �z=SynchronousAssertionsTests.test_assertIsInstanceCustomMessagec C s2 t dtfi �}t dtfi �}|� }| �||� dS )z?
Test a true condition of assertNotIsInstance.
r� r� N�r� r� �assertNotIsInstancer� r r r �test_assertNotIsInstance� s z3SynchronousAssertionsTests.test_assertNotIsInstancec C sD t dtfi �}t dtfi �}t dtfi �}|� }| �|||f� dS )zT
Test a true condition of assertNotIsInstance and multiple classes.
r� r� r� Nr� r� r r r �'test_assertNotIsInstanceMultipleClasses� s
zBSynchronousAssertionsTests.test_assertNotIsInstanceMultipleClassesc C sD t dtfi �}|� }| �| j| j||�}| �t|�d||f � dS )z9
Test an error with assertNotIsInstance.
r� z%r is an instance of %sN)r� r� rp r2 r� r3 r4 )r r� r� ru r r r � test_assertNotIsInstanceError� s �z8SynchronousAssertionsTests.test_assertNotIsInstanceErrorc C s> t dtfi �}t dtfi �}|� }| �| j| j|||f� dS )zN
Test an error with assertNotIsInstance and multiple classes.
r� r� N)r� r� rp r2 r� r� r r r �,test_assertNotIsInstanceErrorMultipleClasses� s zGSynchronousAssertionsTests.test_assertNotIsInstanceErrorMultipleClassesc C s | � ddiddi� dS )z�
L{twisted.trial.unittest.TestCase} supports the C{assertDictEqual}
method inherited from the standard library in Python 2.7.
r� r8 N)�assertDictEqualr r r r �test_assertDictEqual� s z/SynchronousAssertionsTests.test_assertDictEqualr� Nz:assertDictEqual is not available on this version of Python)0r r r r" rd rg ri rl rr rs rt rv rz 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� r� r� r� r� �getattrr
r> �skipr r r r r` sX
�r` c @ st e Zd Zdd� Zdd� Zdd� Zdd� Zd d
� Zd d � Zd
d� Z dd� Z
dd� Z dd� Z dd� Z
dd� Zdd� ZdS ) �WarningAssertionTestsc C s* dd� }| � tdt|d�}| �|d� dS )z0
Test basic assertWarns report.
c S s t jdtd� | S �N�Woo deprecated��category��warnings�warn�DeprecationWarning�r� r r r r � s z:WarningAssertionTests.test_assertWarns.<locals>.deprecatedr� �{ N�� assertWarnsr� �__file__r3 �r r �rr r r �test_assertWarns� s
�z&WarningAssertionTests.test_assertWarnsc C sH dd� }| � tdt|d�}| �|d� | � tdt|d�}| �|d� dS )z}
Test that assertWarns cleans the warning registry, so the warning is
not swallowed the second time.
c S s t jdtd� | S r� r� r� r r r r s zGWarningAssertionTests.test_assertWarnsRegistryClean.<locals>.deprecatedr� r� �A Nr� )r r Zr1Zr2r r r � test_assertWarnsRegistryClean s
�
�z3WarningAssertionTests.test_assertWarnsRegistryCleanc C s& dd� }| � | j| jtdt|d� dS )zH
Test assertWarns failure when no warning is generated.
c S s | S r r r� r r r �normal s z;WarningAssertionTests.test_assertWarnsError.<locals>.normalr� r� N�rp r2 r� r� r� )r r� r r r �test_assertWarnsError s �z+WarningAssertionTests.test_assertWarnsErrorc C s& dd� }| � | j| jtdt|d� dS )zF
Test assertWarns failure when the category is wrong.
c S s t jdtd� | S �N�Foo deprecatedr� r� r� r r r r # s zGWarningAssertionTests.test_assertWarnsWrongCategory.<locals>.deprecatedr� r� N)rp r2 r� � UserWarningr� �r r r r r � test_assertWarnsWrongCategory s �z3WarningAssertionTests.test_assertWarnsWrongCategoryc C s& dd� }| � | j| jtdt|d� dS )zE
Test assertWarns failure when the message is wrong.
c S s t jdtd� | S r� r� r� r r r r / s zFWarningAssertionTests.test_assertWarnsWrongMessage.<locals>.deprecated�Bar deprecatedr� Nr� r� r r r � test_assertWarnsWrongMessage+ s �z2WarningAssertionTests.test_assertWarnsWrongMessagec C s& dd� }| � | j| jtdt|d� dS )z�
If the warning emitted by a function refers to a different file than is
passed to C{assertWarns}, C{failureException} is raised.
c S s t jdtdd� d S )Nr� rG )r� �
stacklevelr� r� r r r r < s
�zCWarningAssertionTests.test_assertWarnsWrongFile.<locals>.deprecatedr� r� Nr� r� r r r �test_assertWarnsWrongFile7 s �z/WarningAssertionTests.test_assertWarnsWrongFilec C sR G dd� d�}| � tdt|�}| �t||�� | � tdt|�}| �t||�� dS )zH
Test assertWarns works when creating a class instance.
c @ s e Zd Zdd� ZdS )z;WarningAssertionTests.test_assertWarnsOnClass.<locals>.Warnc S s t jdtd� d S )N�Do not call mer� )r� r� �RuntimeWarningr r r r r U s zDWarningAssertionTests.test_assertWarnsOnClass.<locals>.Warn.__init__N)r r r r r r r r �WarnT s r� r� N)r� r� r� rZ rx )r r� r� r r r �test_assertWarnsOnClassP s
�
�z-WarningAssertionTests.test_assertWarnsOnClassc C sX G dd� d�}|� }| � tdt|jd�}| �|d� | � tdt|jd�}| �|d� dS )zI
Test assertWarns works when used on an instance method.
c @ s e Zd Zdd� ZdS )z<WarningAssertionTests.test_assertWarnsOnMethod.<locals>.Warnc S s t jdtd� |S )Nr� r� r� r� r r r r d s zGWarningAssertionTests.test_assertWarnsOnMethod.<locals>.Warn.deprecatedN)r r r r r r r r r� c s r� r� r� N)r� r� r� r r3 �r r� �wr� r r r �test_assertWarnsOnMethod_ s
�
�z.WarningAssertionTests.test_assertWarnsOnMethodc C sT G dd� d�}|� }| � tdt|d�}| �|d� | � tdt|d�}| �|d� dS )zM
Test assertWarns works on instance with C{__call__} method.
c @ s e Zd Zdd� ZdS )z:WarningAssertionTests.test_assertWarnsOnCall.<locals>.Warnc S s t jdtd� |S )N�Egg deprecatedr� r� r� r r r �__call__u s zCWarningAssertionTests.test_assertWarnsOnCall.<locals>.Warn.__call__N)r r r r� r r r r r� t s r� r� r� Nr� r� r r r �test_assertWarnsOnCallp s
�
�z,WarningAssertionTests.test_assertWarnsOnCallc C s* dd� }| � tdt|d�}| �|d� dS )zD
Test assertWarns on a warning filtered by default.
c S s t jdtd� | S r� �r� r� �PendingDeprecationWarningr� r r r r � s z@WarningAssertionTests.test_assertWarnsFilter.<locals>.deprecatedr� r� N)r� r� r� r3 r� r r r �test_assertWarnsFilter� s �z,WarningAssertionTests.test_assertWarnsFilterc s( dd� � � fdd�}| � tdt|� dS )z�
C{assertWarns} does not raise an exception if the function it is passed
triggers the same warning more than once.
c S s t jdtd� d S r� r� r r r r r � s zJWarningAssertionTests.test_assertWarnsMultipleWarnings.<locals>.deprecatedc s � � � � d S r r r r r r �f� s zAWarningAssertionTests.test_assertWarnsMultipleWarnings.<locals>.fr� N)r� r� r� )r r� r r r � test_assertWarnsMultipleWarnings� s �z6WarningAssertionTests.test_assertWarnsMultipleWarningsc C s6 dd� }| � | j| jtdt|d�}| �t|�d� dS )z�
For now, assertWarns is unable to handle multiple different warnings,
so it should raise an exception if it's the case.
c S s t jdtd� t jdtd� d S )Nr� r� z Another one)r� r� r� r� r� r r r r � s zKWarningAssertionTests.test_assertWarnsDifferentWarnings.<locals>.deprecatedr� r� z Can't handle different warningsN)rp r2 r� r� r� r3 r4 )r r rP r r r �!test_assertWarnsDifferentWarnings� s �z7WarningAssertionTests.test_assertWarnsDifferentWarningsc sX G dd� dt �� � fdd�}|d� | �� dt|d� | �|g�\}| �|d d� dS ) z�
Warnings emitted before L{TestCase.assertWarns} is called do not get
flushed and do not alter the behavior of L{TestCase.assertWarns}.
c @ s e Zd ZdS )zPWarningAssertionTests.test_assertWarnsAfterUnassertedWarning.<locals>.TheWarningN)r r r r r r r �
TheWarning� s r� c s t j| � d� d S )Nr� )r� r� )rm �r� r r r� � s zGWarningAssertionTests.test_assertWarnsAfterUnassertedWarning.<locals>.frn ro rm N)�Warningr� r� �
flushWarningsr3 )r r� Zwarningr r� r �&test_assertWarnsAfterUnassertedWarning� s z<WarningAssertionTests.test_assertWarnsAfterUnassertedWarningN)r r r r� r� r� r� r� r� r� r� r� r� r� r� r� r r r r r� � s r� c @ s� e Zd ZdZe� Zeed��Zdd� Z dd� Z
dd� Z d d
� Z d d � Z
d
d� Zdd� Zdd� Zdd� Zdd� Zdd� Zdd� Zdd � Zd d � Zd d � Zd!d"� Zd#d$� Zd%S )&�ResultOfAssertionsTestsz�
Tests for L{SynchronousTestCase.successResultOf},
L{SynchronousTestCase.failureResultOf}, and
L{SynchronousTestCase.assertNoResult}.
z Bad timesc C s | � | j| jt� � dS )z�
L{SynchronousTestCase.successResultOf} raises
L{SynchronousTestCase.failureException} when called with a L{Deferred}
with no current result.
N)rp r2 �successResultOfr r r r r �test_withoutSuccessResult� s
�z1ResultOfAssertionsTests.test_withoutSuccessResultc C s | � | j| jt| j�� dS )z�
L{SynchronousTestCase.successResultOf} raises
L{SynchronousTestCase.failureException} when called with a L{Deferred}
with a failure result.
N)rp r2 r� r �failurer r r r � test_successResultOfWithFailure� s
�z7ResultOfAssertionsTests.test_successResultOfWithFailurec
C sT z| � t| j�� W n: | jk
rN } z| �| j�� t|�� W 5 d}~X Y nX dS )z�
L{SynchronousTestCase.successResultOf} raises a
L{SynchronousTestCase.failureException} that has the original failure
traceback when called with a L{Deferred} with a failure result.
N)r� r r� r2 rN � getTracebackr4 r� r r r �+test_successResultOfWithFailureHasTraceback� s zCResultOfAssertionsTests.test_successResultOfWithFailureHasTracebackc C s | � | j| jt� � dS )z�
L{SynchronousTestCase.failureResultOf} raises
L{SynchronousTestCase.failureException} when called with a L{Deferred}
with no current result.
N)rp r2 �failureResultOfr r r r r �test_withoutFailureResult� s
�z1ResultOfAssertionsTests.test_withoutFailureResultc C s | � | j| jt| j�� dS )z�
L{SynchronousTestCase.failureResultOf} raises
L{SynchronousTestCase.failureException} when called with a L{Deferred}
with a success result.
N)rp r2 r r r6 r r r r � test_failureResultOfWithSuccess� s
�z7ResultOfAssertionsTests.test_failureResultOfWithSuccessc C s | � | j| jt| j�t� dS )z�
L{SynchronousTestCase.failureResultOf} raises
L{SynchronousTestCase.failureException} when called with a L{Deferred}
with a failure type that was not expected.
N)rp r2 r r r� �KeyErrorr r r r �$test_failureResultOfWithWrongFailure� s �z<ResultOfAssertionsTests.test_failureResultOfWithWrongFailurec
C sr z| � t| j�t� W nV | jk
rl } z6| �| j�� t|�� | �d�tj tj
�t|�� W 5 d}~X Y nX dS )aV
L{SynchronousTestCase.failureResultOf} raises
L{SynchronousTestCase.failureException} when called with a L{Deferred}
with a failure type that was not expected, and the
L{SynchronousTestCase.failureException} message contains the original
failure traceback as well as the expected failure type
z%Failure of type ({0}.{1}) expected onN) r r r� r r2 rN r r4 r� r r r� r r r �6test_failureResultOfWithWrongFailureOneExpectedFailure s ��zNResultOfAssertionsTests.test_failureResultOfWithWrongFailureOneExpectedFailurec C s| z| � t| j�tt� W n^ | jk
rv } z>| �| j�� t|�� | �d� tj
tj tj
tj �t|�� W 5 d}~X Y nX dS )at
L{SynchronousTestCase.failureResultOf} raises
L{SynchronousTestCase.failureException} when called with a L{Deferred}
with a failure type that was not expected, and the
L{SynchronousTestCase.failureException} message contains the original
failure traceback as well as the expected failure types in the error
message
z0Failure of type ({0}.{1} or {2}.{3}) expected onN) r r r� r �IOErrorr2 rN r r4 r� r r r� r r r �8test_failureResultOfWithWrongFailureMultiExpectedFailure s ��zPResultOfAssertionsTests.test_failureResultOfWithWrongFailureMultiExpectedFailurec C s | � | j| �t| j��� dS )a
When passed a L{Deferred} which currently has a result (ie,
L{Deferred.addCallback} would cause the added callback to be called
before C{addCallback} returns), L{SynchronousTestCase.successResultOf}
returns that result.
N)�assertIdenticalr6 r� r r r r r �test_withSuccessResult' s �z.ResultOfAssertionsTests.test_withSuccessResultc C s& | � | j| �t| j�| jjt�� dS )a7
When passed a L{Deferred} which currently has a L{Failure} result (ie,
L{Deferred.addErrback} would cause the added errback to be called
before C{addErrback} returns), L{SynchronousTestCase.failureResultOf}
returns that L{Failure} if that L{Failure}'s type is expected.
N)r
r� r r r� r r r r r � test_withExpectedFailureResult2 s ��z6ResultOfAssertionsTests.test_withExpectedFailureResultc C s | � | j| �t| j��� dS )a
When passed a L{Deferred} which currently has a L{Failure} result
(ie, L{Deferred.addErrback} would cause the added errback to be called
before C{addErrback} returns), L{SynchronousTestCase.failureResultOf}
returns that L{Failure}.
N)r
r� r r r r r r �test_withFailureResult? s �z.ResultOfAssertionsTests.test_withFailureResultc C s | � | j| jt| j�� dS )z�
When passed a L{Deferred} which currently has a success result (see
L{test_withSuccessResult}), L{SynchronousTestCase.assertNoResult} raises
L{SynchronousTestCase.failureException}.
N)rp r2 �assertNoResultr r6 r r r r �test_assertNoResultSuccessJ s
�z2ResultOfAssertionsTests.test_assertNoResultSuccessc C s | � | j| jt| j�� dS )z�
When passed a L{Deferred} which currently has a failure result (see
L{test_withFailureResult}), L{SynchronousTestCase.assertNoResult} raises
L{SynchronousTestCase.failureException}.
N)rp r2 r r r� r r r r �test_assertNoResultFailureT s
�z2ResultOfAssertionsTests.test_assertNoResultFailurec C s | � t� � dS )zC
When passed a L{Deferred} with no current result,
N)r r r r r r �test_assertNoResult^ s z+ResultOfAssertionsTests.test_assertNoResultc C s4 t � }| �|� |�| j� | �| j| �|�� dS )z�
When passed a L{Deferred} with no current result, which is then
fired with a success result, L{SynchronousTestCase.assertNoResult}
doesn't modify the result of the L{Deferred}.
N)r r �callbackr6 r3 r� �r �dr r r �$test_assertNoResultPropagatesSuccesse s
z<ResultOfAssertionsTests.test_assertNoResultPropagatesSuccessc C s4 t � }| �|� |�| j� | �| j| �|�� dS )z�
When passed a L{Deferred} with no current result, which is then
fired with a L{Failure} result, L{SynchronousTestCase.assertNoResult}
doesn't modify the result of the L{Deferred}.
N)r r Zerrbackr� r3 r r r r r �)test_assertNoResultPropagatesLaterFailureq s
zAResultOfAssertionsTests.test_assertNoResultPropagatesLaterFailurec C sF t | j�}z| �|� W n | jk
r. Y nX | �d| �|�� dS )z�
When passed a L{Deferred} which currently has a L{Failure} result,
L{SynchronousTestCase.assertNoResult} changes the result of the
L{Deferred} to a success.
N)r r� r r2 r3 r� r r r r �+test_assertNoResultSwallowsImmediateFailure} s
zCResultOfAssertionsTests.test_assertNoResultSwallowsImmediateFailureN)r r r r" r� r6 r � Exceptionr� r� r� r r r r r r r r r
r r r r r r r r r r r� � s(
r� c @ s8 e Zd ZdZdd� Zdd� Zdd� Zdd � Zd
d � Zd S )
�AssertionNamesTestszK
Tests for consistency of naming within TestCase assertion methods
c s" i � t | � d� � fdd�� D �S )N�assertc s& g | ] }|� d �s|dkr� | �qS )ZNot�_)r� )�.0�k�Zdctr r �
<listcomp>� s
z3AssertionNamesTests._getAsserts.<locals>.<listcomp>)r r r r r � _getAsserts� s z AssertionNamesTests._getAssertsc C s |j S r )r ry r r r �_name� s zAssertionNamesTests._namec C s0 t | �� �}t t| d��}| �||�|�� dS )a�
The C{failUnless*} test methods are a subset of the C{assert*} test
methods. This is intended to ensure that methods using the
I{failUnless} naming scheme are not added without corresponding methods
using the I{assert} naming scheme. The I{assert} naming scheme is
preferred, and new I{assert}-prefixed methods may be added without
corresponding I{failUnless}-prefixed methods.
r\ N)�setr r r3 � intersection)r �assertsZ failUnlessesr r r � test_failUnlessMatchesAssert� s �z0AssertionNamesTests.test_failUnlessMatchesAssertc C s< t tjd�}t tjd�}| �t|| jd�t|| jd�� d S )NZ assertNotrR )�key)r r
r> r3 �sortedr! )r r$ ZfailIfsr r r � test_failIf_matches_assertNot� s
�z1AssertionNamesTests.test_failIf_matches_assertNotc C s� t | ��� D ]�\}}t|�s q |�d�r\| �t| |d �d||f � | �|t| |d �� |�d�r | �t| |d d� �d||d d� f � | �|t| |d d� �� q d S )NZEqual�sz
%s but no %ssZEquals���z %s but no %s)�vars�items�callable�endswithrZ �hasattrr3 r� )r r �valuer r r �test_equalSpelling� s
�
�z&AssertionNamesTests.test_equalSpellingN) r r r r" r r! r% r( r1 r r r r r � s r c @ sV e Zd ZdZedddd�Zdd� Zdd� Zd d
� Zd d � Z d
d� Z
dd� Z dd� Z dS )�CallDeprecatedTestsz\
Test use of the L{SynchronousTestCase.callDeprecated} method with version objects.
ZTwisted� r c C s& | � | jtd� | �| �� g d� dS )zj
callDeprecated calls a deprecated callable, suppressing the
deprecation warning.
rn zNo warnings should be shownN)�callDeprecated�version� oldMethodr3 r� r r r r �$test_callDeprecatedSuppressesWarning� s �z8CallDeprecatedTests.test_callDeprecatedSuppressesWarningc C s | � | jtd�}| �d|� dS )zn
L{callDeprecated} actually calls the callable passed to it, and
forwards the result.
rn N)r4 r5 r6 r3 r5 r r r � test_callDeprecatedCallsFunction� s z4CallDeprecatedTests.test_callDeprecatedCallsFunctionc C s6 dd� }| � | j| j| j|�}| �d| t|�� dS )zd
L{callDeprecated} raises a test failure if the callable is not
deprecated.
c S s d S r r r r r r �
notDeprecated� s zGCallDeprecatedTests.test_failsWithoutDeprecation.<locals>.notDeprecatedz%r is not deprecated.N)rp r2 r4 r5 r3 r4 )r r9 rq r r r � test_failsWithoutDeprecation� s � �z0CallDeprecatedTests.test_failsWithoutDeprecationc C sR t dddd�}| �| j| j|td�}| �t| j�t|�� | �t|�t|�� dS )z�
callDeprecated raises a test failure if the callable was deprecated
at a different version to the one expected.
�Foor8 rG rI rn N) r
rp r2 r4 r6 rN r r5 r4 )r �differentVersionrq r r r �"test_failsWithIncorrectDeprecation� s �z6CallDeprecatedTests.test_failsWithIncorrectDeprecationc C sT t dddd�}dd� }t|�|�}| �||d� | �� }| �t|�dd�|�� d S )
a:
L{callDeprecated} ignores all deprecations apart from the first.
Multiple warnings are generated when a deprecated function calls
another deprecated function. The first warning is the one generated by
the explicitly called function. That's the warning that we care about.
r; r8 rG rI c W s t | � S r )r6 )�argsr r r �nestedDeprecation� s zECallDeprecatedTests.test_nestedDeprecation.<locals>.nestedDeprecation� zUnexpected warnings: {}N)r
r r4 r� r3 r< r� )r r< r? Z
warningsShownr r r �test_nestedDeprecation� s �z*CallDeprecatedTests.test_nestedDeprecationc C s | � | jdftd� dS )zj
L{callDeprecated} can take a message argument used to check the warning
emitted.
� newMethodr8 N)r4 r5 �oldMethodReplacedr r r r � test_callDeprecationWithMessage
s �z3CallDeprecatedTests.test_callDeprecationWithMessagec C sF | � | j| j| jdftd�}| �t| j�t|�� | �dt|�� dS )z|
If the message passed to L{callDeprecated} doesn't match,
L{callDeprecated} raises a test failure.
zsomething.wrongr8 z please use newMethod insteadN)rp r2 r4 r5 rC rN r r4 )r rq r r r �$test_callDeprecationWithWrongMessage s �z8CallDeprecatedTests.test_callDeprecationWithWrongMessageN)
r r r r" r
r5 r7 r8 r: r= rA rD rE r r r r r2 � s
r2 c C s | S )z(
Deprecated method for testing.
r �rc r r r r6 # s r6 rB )Z replacementc C s d| S )zh
Another deprecated method, which has been deprecated in favor of the
mythical 'newMethod'.
rG r rF r r r rC + s rC ))r" Z
__future__r r r� r
r+ Ztwisted.python.utilr Ztwisted.python.reflectr r r Ztwisted.python.deprecater Z incrementalr
r Ztwisted.python.failurer Z
twisted.trialZtwisted.internet.deferr r r r� r r re r% r> r? rW r` r� r� r r2 r5 r6 rC r r r r �<module> s: 9MM s E S0g