文件操作 - test_assertions.cpython-310.pyc
返回文件管理
返回主菜单
删除本文件
文件: /usr/lib/python3/dist-packages/twisted/trial/test/__pycache__/test_assertions.cpython-310.pyc
编辑文件内容
o �b�� � @ s� d Z ddlZddlZddlmZmZ ddlmZm Z m Z ddl m Z m Z ddlmZ ddlmZmZmZ ddlmZ dd lmZ G d d � d e�ZG d d � d �ZG dd� dej�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 d d � d ej�Z"G d d � d ej�Z#e e#j$�d d!� �Z%e e#j$d"d#�d$d%� �Z&G d&d'� d'ej�Z'd(d)� Z(e(Z)e e'j$d*e*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). � N)�Version�getVersionString)�Deferred�fail�succeed)� deprecated�deprecatedModuleAttribute)�Failure)�accumulateMethods�fullyQualifiedName�prefixedMethods)� FancyEqMixin)�unittestc @ s& e Zd ZdZdd� Zdefdd�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__�returnc C s d| j � d�S )Nz MockEquality(�)r �r r r r �__repr__' � zMockEquality.__repr__N)�__name__� __module__� __qualname__�compareAttributesr �strr r r r r r ! s r c @ s e Zd ZdZdd� ZeZeZdS )�ComparisonErrorzH An object which raises exceptions from its comparison methods. c C s t d��)NzComparison is broken)� ValueError)r �otherr r r �_error0 � 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 @ � e Zd Zdd� ZdS )z TestFailureTests.FailingTestc C s | � d� d S )NzThis test fails.�r r r r r � test_failsD r z'TestFailureTests.FailingTest.test_failsN)r r r r, r r r r � FailingTestC � 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- �pyunit� TestLoader�loader�loadTestsFromName�join�suite�list�test)r � componentsr r r �setUpG s zTestFailureTests.setUpc C sZ z| j �d� W n | j jy% } z| �dt|�� W Y d}~dS d}~ww | �d� dS )z} L{SynchronousTestCase.fail} raises L{SynchronousTestCase.failureException} with the given argument. �failedNzRSynchronousTestCase.fail method did not raise SynchronousTestCase.failureException)r8 r �failureException� assertEqualr �r �resultr r r � test_failQ 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) r1 � TestResultr6 �run� assertFalse� wasSuccessfulr= �errors�len�failuresr8 r> r r r �test_failingExceptionFails` s z+TestFailureTests.test_failingExceptionFailsN) r r r r& r �SynchronousTestCaser- r: r@ rI r r r r r) 7 s r) c @ �@ 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|���}||kr | � d|��� qdS )z� Perform the positive case test for C{failIf} or C{assertFalse}. @param method: The test method to test. r � FNr � failed on �Did not return argument r+ )r �method�notTruer? r r r �_assertFalseFalsex s ��z"AssertFalseTests._assertFalseFalsec C s� dddddgdfD ]<}z ||d|��� W n% | j y: } z| �d|��t|�d|�d|��� W Y d }~q d }~ww | �d |j|f � q d S ) z� Perform the negative case test for C{failIf} or C{assertFalse}. @param method: The test method to test. rA T�cat� �� � rN � Raised incorrect exception on �: N�Call to %s(%r) didn't fail�r< �assertInr r r )r rP �true�er r r �_assertFalseTrue� s& �������z!AssertFalseTests._assertFalseTruec C � | � | j� dS )zt L{SynchronousTestCase.failIf} returns its argument if its argument is not considered true. N)rR �failIfr r r r �test_failIfFalse� � z!AssertFalseTests.test_failIfFalsec C r` )zy L{SynchronousTestCase.assertFalse} returns its argument if its argument is not considered true. N)rR rD r r r r �test_assertFalseFalse� rc z&AssertFalseTests.test_assertFalseFalsec C r` )z� L{SynchronousTestCase.failIf} raises L{SynchronousTestCase.failureException} if its argument is considered true. N)r_ ra r r r r �test_failIfTrue� � z AssertFalseTests.test_failIfTruec C r` )z� L{SynchronousTestCase.assertFalse} raises L{SynchronousTestCase.failureException} if its argument is considered true. N)r_ rD r r r r �test_assertFalseTrue� rf z%AssertFalseTests.test_assertFalseTrueN) r r r r& rR r_ rb rd re rg r r r r rL m s rL c @ rK )�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 ]<}z ||d|��� W n% | j y9 } z| �d|��t|�d|�d|��� W Y d}~qd}~ww | �d |j|f � qdS ) z� Perform the negative case test for C{assertTrue} and C{failUnless}. @param method: The test method to test. r rM FNr rN rX rY rZ r[ )r rP rQ r^ r r r �_assertTrueFalse� s& �������z AssertTrueTests._assertTrueFalsec C sD dddddgdfD ]}||d|���}||kr | � d|��� q dS ) z� Perform the positive case test for C{assertTrue} and C{failUnless}. @param method: The test method to test. rA TrS rT rU rN rO Nr+ )r rP r] r? r r r �_assertTrueTrue� s ��z AssertTrueTests._assertTrueTruec C r` )z� L{SynchronousTestCase.assertTrue} raises L{SynchronousTestCase.failureException} if its argument is not considered true. N)ri � assertTruer r r r �test_assertTrueFalse� rf z$AssertTrueTests.test_assertTrueFalsec C r` )z� L{SynchronousTestCase.failUnless} raises L{SynchronousTestCase.failureException} if its argument is not considered true. N)ri � failUnlessr r r r �test_failUnlessFalse� rf z$AssertTrueTests.test_failUnlessFalsec C r` )zt L{SynchronousTestCase.assertTrue} returns its argument if its argument is considered true. N)rj rk r r r r �test_assertTrueTrue� rc z#AssertTrueTests.test_assertTrueTruec C r` )zt L{SynchronousTestCase.failUnless} returns its argument if its argument is considered true. N)rj rm r r r r �test_failUnlessTrue� rc z#AssertTrueTests.test_failUnlessTrueN) r r r r& ri rj rl rn ro rp r r r r rh � s rh c @ sl 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�dSu r�dTe+_/dSS 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 d S )Nz)assertEqual should return first parameter)r= r )r �first�second�xr r r �_testEqualPair s �z)SynchronousAssertionsTests._testEqualPairc C s� d}z| � ||� W nM | jyW } z@t�d�}z|� ||� W n, |jyL } z d}t|�}t|�}||krB| �d|�d|��� W Y d}~nd}~ww W Y d}~nd}~ww |sh| �d|�d|�d �� dS 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. Fr: Tz Expected: z; Got: NzCall to assertEqual(z, z ) didn't fail)r= r< r1 �TestCaser r ) r rr rs �raised� ourFailure�case� theirFailure�got�expectedr r r �_testUnequalPair s( ���� �z+SynchronousAssertionsTests._testUnequalPairc C s: | � dd� | �dd� | � dgdg� | �dgd� d S )NrS �dogrA �orange)ru r} r r r r �test_assertEqual_basic/ s z1SynchronousAssertionsTests.test_assertEqual_basicc C sL t d�}t d�}t d�}| �||� | �||� | �||� | �||� d S )Nrr rs )r ru r} )r rt �y�zr r r �test_assertEqual_custom5 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)� assertRaisesr< r= r\ r )r r� � exceptionr r r �test_assertEqualMessage> 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}. r� r� N)r� r< r= r )r �exceptionForNone�exceptionWithoutr r r �test_assertEqualNoneMessageI s � �z6SynchronousAssertionsTests.test_assertEqualNoneMessagec C sf t � }dg}z| �||� W n | jy | �d� Y d S ty' Y d S w | �d�||�� d S )Nr z6Fail raised when ValueError ought to have been raised.z7Comparing {!r} and {!r} should have raised an exception)r! r= r< r r" �format)r �appler r r r � test_assertEqual_incomparableV s ���z8SynchronousAssertionsTests.test_assertEqual_incomparablec C s |�r r )r �errorr r r � _raiseErrorg � z&SynchronousAssertionsTests._raiseErrorc C s& | � t| jt�}| �t|t�d� d S )Nz?Expect failUnlessRaises to return instance of raised exception.)�failUnlessRaisesr" r� rk � isinstance�r rt r r r � test_failUnlessRaises_expectedj s �z9SynchronousAssertionsTests.test_failUnlessRaises_expectedc C sV z | � t| jt� W n ty | �d� Y d S | jy# Y d S w | �d� d S )Nz9failUnlessRaises shouldn't re-raise unexpected exceptionsz4Expected exception wasn't raised. Should have failed)r� r" r� � TypeErrorr r< r r r r � test_failUnlessRaises_unexpectedq s �z;SynchronousAssertionsTests.test_failUnlessRaises_unexpectedc sd d� z | � t� fdd�� W n | jy* } z| �t|�d� W Y d }~d S d }~ww | �d� d S )NrV c s � S r r r �� returnValuer r �<lambda> � zNSynchronousAssertionsTests.test_failUnlessRaises_noException.<locals>.<lambda>z"ValueError not raised (3 returned)z(Exception not raised. Should have failed)r� r" r< r= r r �r r^ r r� r �!test_failUnlessRaises_noException| s ��z<SynchronousAssertionsTests.test_failUnlessRaises_noExceptionc C sn | � | j| j| j�}| �t|| j�d| j�d�� z | � | j| jt�}W n | jy/ Y d S w | �d� d S )Nz Expected z instance to be returnedz Should have raised exception)r� r< r� rk r� r" r r� r r r �&test_failUnlessRaises_failureException� s � � ��zASynchronousAssertionsTests.test_failUnlessRaises_failureExceptionc C s: t d�}| �t ��}|�1 sw Y | �||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" r� �assertIsr� )r r� �contextr r r � test_assertRaisesContextExpected� s �z;SynchronousAssertionsTests.test_assertRaisesContextExpectedc C s� z| � t�� td��1 sw Y W n, | jy@ } z t|�}djtt�d�}| �|�|�d�|�� W Y d}~dS d}~ww | � 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� Nz/{type} raised instead of ValueError: Traceback)�typez=Exception message did not begin with expected information: {}�:Mismatched exception type should have caused test failure.) r� r" r� r< r r� r rk � startswithr )r r� r� r| r r r �"test_assertRaisesContextUnexpected� s" ����� z=SynchronousAssertionsTests.test_assertRaisesContextUnexpectedc C sz z| � t�� W d � n1 sw Y W n | jy5 } zt|�}| �|d� W Y d}~dS d}~ww | �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. Nz%ValueError not raised (None returned)z5Non-exception result should have caused test failure.)r� r" r< r r= r )r r� r� r r r �#test_assertRaisesContextNoException� s ����z>SynchronousAssertionsTests.test_assertRaisesContextNoExceptionc C s� z| � ttf�� t� �1 sw Y W nE | jyZ } z8t|�}d|v}d|v}g }|r3|�d� |r:|�d� |rO| �d�|�d|� �� W Y d}~dS W Y d}~dS d}~ww | �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. Nr" r� z(expected ValueError in exception messagez'expected TypeError in exception messagez; z message = r� ) r� r" r� �AttributeErrorr< r �appendr r5 )r r� r� � valueError� typeErrorrF r r r �test_brokenName� s& � &��� z*SynchronousAssertionsTests.test_brokenNamec C s\ dgdgdg}}}| � ||�}| �||d� | �| j| j ||� | �| j| j ||� d S )NrA rT �)failIfEqual should return first parameter)� failIfEqualr= r� r< �r rt r� r� �retr r r �test_failIfEqual_basic� � z1SynchronousAssertionsTests.test_failIfEqual_basicc C sX t d�}t d�}t d�}| �||�}| �||d� | �| j| j||� | �||d� d S )Nrr rs �fecundr� z"__ne__ should make these not equal)r r� r= r� r< 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�failIfIdenticalr= )r rt r� r? 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� r� r< r� r� r r r � test_failIfIdenticalNegative s z7SynchronousAssertionsTests.test_failIfIdenticalNegativec C s\ dgdgdg}}}| � ||�}| �||d� | �| j| j ||� | �| j| j ||� d S )NrA rT z1failUnlessIdentical should return first parameter)�failUnlessIdenticalr= r� r< r� r r r �test_failUnlessIdentical r� 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�������?)�failUnlessApproximatesr= r� r< 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))�failUnlessAlmostEqualr= r� r< �r � precisionrt r� r� r� r r r �test_failUnlessAlmostEqual 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))�failIfAlmostEqualr= r� r< r� r r r �test_failIfAlmostEqual. s ���z1SynchronousAssertionsTests.test_failIfAlmostEqualc C s^ d}d}d}| � ||� | � ||�}| �||d� | �| j| j ||� | �| j| j ||� d S �NrS z the dog satz the cat satz should return first parameter)�failUnlessSubstringr= r� r< r� r r r �test_failUnlessSubstring@ � z3SynchronousAssertionsTests.test_failUnlessSubstringc C s^ d}d}d}| � ||� | � ||�}| �||d� | �| j| j ||� | �| j| j ||� d S r� )�failIfSubstringr= r� r< r� r r r �test_failIfSubstringJ r� z/SynchronousAssertionsTests.test_failIfSubstringc C s t d�}| �||� dS )zB L{assertIs} passes if two objects are identical. rr N)r r� �r �ar r r � test_assertIsT s z(SynchronousAssertionsTests.test_assertIsc C s6 t d�t d�}}| �||� | �| j| j||� dS )zE L{assertIs} fails if two objects are not identical. rr N)r r= r� r< r� �r r� �br r r �test_assertIsError[ s z-SynchronousAssertionsTests.test_assertIsErrorc C s. t d�t d�}}| �||� | �||� dS )zI L{assertIsNot} passes if two objects are not identical. rr N)r r= � assertIsNotr� r r r �test_assertIsNotc s z+SynchronousAssertionsTests.test_assertIsNotc C s t d�}| �| j| j||� dS )zD L{assertIsNot} fails if two objects are identical. rr N)r r� r< r� r� r r r �test_assertIsNotErrork 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_assertIsInstancer 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_assertIsInstanceMultipleClassesz 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� r� r< 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. rV zSilly assertionN)r� r< r� r r\ )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 sF t dtfi �}|� }| �| j| j||�}| �t|�|�d|� �� dS )z9 Test an error with assertNotIsInstance. r� z is an instance of N)r� r� r� r< r� r= r )r r� r� r� 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� r� r< 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� rA N)�assertDictEqualr r r r �test_assertDictEqual� � z/SynchronousAssertionsTests.test_assertDictEqualr� Nz:assertDictEqual is not available on this version of Python)0r r r r& ru 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� r� r� r� r� r� r� r� r� �getattrr rJ �skipr r r r rq s\ ��rq 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 �* dd� }| � tdt|d�}| �|d� dS )z0 Test basic assertWarns report. c S � t jdtd� | S �N�Woo deprecated��category��warnings�warn�DeprecationWarning�r� r r r r � � z:WarningAssertionTests.test_assertWarns.<locals>.deprecatedr� �{ N�� assertWarnsr� �__file__r= �r r �rr r r �test_assertWarns� � �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 r� r� r� r� r r r r � r� zGWarningAssertionTests.test_assertWarnsRegistryClean.<locals>.deprecatedr� r� �A Nr� )r r �r1�r2r r r � test_assertWarnsRegistryClean� s � �z3WarningAssertionTests.test_assertWarnsRegistryCleanc C �& dd� }| � | j| jtdt|d� dS )zH Test assertWarns failure when no warning is generated. c S � | S r r r� r r r �normal� r� z;WarningAssertionTests.test_assertWarnsError.<locals>.normalr� r� N�r� r< r� r� r )r r r r r �test_assertWarnsError� s �z+WarningAssertionTests.test_assertWarnsErrorc C r )zF Test assertWarns failure when the category is wrong. c S r� �N�Foo deprecatedr� r� r� r r r r r� zGWarningAssertionTests.test_assertWarnsWrongCategory.<locals>.deprecatedr r� N)r� r< r� � UserWarningr �r r r r r � test_assertWarnsWrongCategory � �z3WarningAssertionTests.test_assertWarnsWrongCategoryc C r )zE Test assertWarns failure when the message is wrong. c S r� r r� r� r r r r r� zFWarningAssertionTests.test_assertWarnsWrongMessage.<locals>.deprecated�Bar deprecatedr� Nr r r r r � test_assertWarnsWrongMessage r z2WarningAssertionTests.test_assertWarnsWrongMessagec C r )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 rT )r� � stacklevelr� r� r r r r 4 s zCWarningAssertionTests.test_assertWarnsWrongFile.<locals>.deprecatedr r� Nr r r r r �test_assertWarnsWrongFile. 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 @ r* )z;WarningAssertionTests.test_assertWarnsOnClass.<locals>.Warnc S � t jdtd� d S )N�Do not call mer� )r� r� �RuntimeWarningr r r r r S � zDWarningAssertionTests.test_assertWarnsOnClass.<locals>.Warn.__init__N)r r r r r r r r �WarnR r. r r N)r� r r rk r� )r r r r r r �test_assertWarnsOnClassM 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 @ r* )z<WarningAssertionTests.test_assertWarnsOnMethod.<locals>.Warnc S � t jdtd� |S )Nr r� r� r� r r r r a r� zGWarningAssertionTests.test_assertWarnsOnMethod.<locals>.Warn.deprecatedN)r r r r r r r r r ` r. r r r N)r� r� r r r= �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 @ r* )z:WarningAssertionTests.test_assertWarnsOnCall.<locals>.Warnc S r )N�Egg deprecatedr� r� r� r r r �__call__u r� zCWarningAssertionTests.test_assertWarnsOnCall.<locals>.Warn.__call__N)r r r r# r r r r r t r. r r" r Nr� r r r r �test_assertWarnsOnCallo s z,WarningAssertionTests.test_assertWarnsOnCallc C r� )zD Test assertWarns on a warning filtered by default. c S r� r� �r� r� �PendingDeprecationWarningr� r r r r � r� z@WarningAssertionTests.test_assertWarnsFilter.<locals>.deprecatedr� r� N)r� r& r r= r r r r �test_assertWarnsFilter r 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 r r� r% r r r r r � r 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)r� r< r� r� r r= r )r r r^ 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� �r� �r, r r r) � r zGWarningAssertionTests.test_assertWarnsAfterUnassertedWarning.<locals>.fr� r� r� N)�Warningr� r � flushWarningsr= )r r) �warningr r. r �&test_assertWarnsAfterUnassertedWarning� s z<WarningAssertionTests.test_assertWarnsAfterUnassertedWarningN)r r r r r r r r r r r! r$ r' r* r+ r2 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%d&� Zd'd(� Zd)S )*�ResultOfAssertionsTestsz� Tests for L{SynchronousTestCase.successResultOf}, L{SynchronousTestCase.failureResultOf}, and L{SynchronousTestCase.assertNoResult}. � Bad timesc C � | � | j| jt� � dS )z� L{SynchronousTestCase.successResultOf} raises L{SynchronousTestCase.failureException} when called with a L{Deferred} with no current result. N)r� r< �successResultOfr r r r r �test_withoutResult� � z*ResultOfAssertionsTests.test_withoutResultc C � | � | j| jt| j�� dS )z� L{SynchronousTestCase.successResultOf} raises L{SynchronousTestCase.failureException} when called with a L{Deferred} with a failure result. N)r� r< r6 r �failurer r r r � test_successResultOfWithFailure� � �z7ResultOfAssertionsTests.test_successResultOfWithFailurec C sV z | � t| j�� W dS | jy* } z| �| j�� t|�� W Y d}~dS d}~ww )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)r6 r r: r< r\ � getTracebackr r� r r r �+test_successResultOfWithFailureHasTraceback� s $��zCResultOfAssertionsTests.test_successResultOfWithFailureHasTracebackc C r5 )z� L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a L{Deferred} with no current result. N)r� r< �failureResultOfr r r r r �!test_failureResultOfWithoutResult� r8 z9ResultOfAssertionsTests.test_failureResultOfWithoutResultc C r9 )z� L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a L{Deferred} with a success result. N)r� r< r? r r? r r r r � test_failureResultOfWithSuccess� r< z7ResultOfAssertionsTests.test_failureResultOfWithSuccessc C s | � | j| jt| j�t� dS )z� L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a L{Deferred} that fails with an exception type that was not expected. N)r� r< r? r r: �KeyErrorr r r r �$test_failureResultOfWithWrongFailure� s �z<ResultOfAssertionsTests.test_failureResultOfWithWrongFailurec C s^ z | � t| j�t� W dS | jy. } z| �d�tjtj�t |�� W Y d}~dS d}~ww )a= L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a L{Deferred} that fails with an exception type that was not expected, and the L{SynchronousTestCase.failureException} message contains the expected exception type. �#Failure of type ({}.{}) expected onN) r? r r: rB r< r\ r� r r r r� r r r �6test_failureResultOfWithWrongFailureOneExpectedFailure s ����zNResultOfAssertionsTests.test_failureResultOfWithWrongFailureOneExpectedFailurec C sX z | � t| j�t� W dS | jy+ } z| �| j�� t|�� W Y d}~dS d}~ww )a@ L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a L{Deferred} that fails with an exception type that was not expected, and the L{SynchronousTestCase.failureException} message contains the original failure traceback. N)r? r r: rB r< r\ r= r r� r r r �;test_failureResultOfWithWrongFailureOneExpectedFailureHasTB s $��zSResultOfAssertionsTests.test_failureResultOfWithWrongFailureOneExpectedFailureHasTBc C sh z | � t| j�tt� W dS | jy3 } z| �d�tjtj tjtj �t |�� W Y d}~dS d}~ww )aH L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a L{Deferred} with an exception type that was not expected, and the L{SynchronousTestCase.failureException} message contains the expected exception types in the error message. �,Failure of type ({}.{} or {}.{}) expected onN) r? r r: rB �IOErrorr< r\ r� r r r r� r r r �9test_failureResultOfWithWrongFailureMultiExpectedFailures% s ����zQResultOfAssertionsTests.test_failureResultOfWithWrongFailureMultiExpectedFailuresc C sZ z | � t| j�tt� W dS | jy, } z| �| j�� t|�� W Y d}~dS d}~ww )aJ L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a L{Deferred} with an exception type that was not expected, and the L{SynchronousTestCase.failureException} message contains the original failure traceback in the error message. N) r? r r: rB rH r< r\ r= r r� r r r �>test_failureResultOfWithWrongFailureMultiExpectedFailuresHasTB: s $��zVResultOfAssertionsTests.test_failureResultOfWithWrongFailureMultiExpectedFailuresHasTBc C � | � | 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)�assertIdenticalr? r6 r r r r r �%test_successResultOfWithSuccessResultG � z=ResultOfAssertionsTests.test_successResultOfWithSuccessResultc C s& | � | j| �t| j�| jjt�� 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} if its contained exception type is expected. N)rL r: r? r r� rB r r r r �-test_failureResultOfWithExpectedFailureResultP s �zEResultOfAssertionsTests.test_failureResultOfWithExpectedFailureResultc C rK )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)rL r: r? r r r r r �%test_failureResultOfWithFailureResult\ rN z=ResultOfAssertionsTests.test_failureResultOfWithFailureResultc C r9 )z� When passed a L{Deferred} which currently has a success result (see L{test_withSuccessResult}), L{SynchronousTestCase.assertNoResult} raises L{SynchronousTestCase.failureException}. N)r� r< �assertNoResultr r? r r r r �test_assertNoResultSuccesse r< z2ResultOfAssertionsTests.test_assertNoResultSuccessc C r9 )z� When passed a L{Deferred} which currently has a failure result (see L{test_withFailureResult}), L{SynchronousTestCase.assertNoResult} raises L{SynchronousTestCase.failureException}. N)r� r< rQ r r: r r r r �test_assertNoResultFailureo r< z2ResultOfAssertionsTests.test_assertNoResultFailurec C s | � t� � dS )z� When passed a L{Deferred} with no current result, L{SynchronousTestCase.assertNoResult} does not raise an exception. N)rQ r r r r r �test_assertNoResulty rc z+ResultOfAssertionsTests.test_assertNoResultc C �4 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 rQ �callbackr? r= r6 �r �dr r r �$test_assertNoResultPropagatesSuccess� � z<ResultOfAssertionsTests.test_assertNoResultPropagatesSuccessc C rU )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 rQ �errbackr: r= r? rX r r r �)test_assertNoResultPropagatesLaterFailure� r[ zAResultOfAssertionsTests.test_assertNoResultPropagatesLaterFailurec C sD t | j�}z| �|� W n | jy Y nw | �d| �|�� dS )�� 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: rQ r< r= r6 rX r r r �+test_assertNoResultSwallowsImmediateFailure� s �zCResultOfAssertionsTests.test_assertNoResultSwallowsImmediateFailureN) r r r r& r� r? r � Exceptionr: r7 r; r> r@ rA rC rE rF rI rJ rM rO rP rR rS rT rZ r] r` r r r r r3 � s. r3 c @ s� e Zd ZdZe� Zed�Zee�Z dd� Z dd� Z d0dd �Z d d � Z d d � Zdd� Zdd� Zdd� Zdd� Zdd� Zdd� Zdd� Zd d � Zd d � Zd d!� Zd"d#� Zd$d%� Zd&d'� Zd(d)� Z d*d+� Z d,d-� Z d.d/� Z dS )1� ResultOfCoroutineAssertionsTestsz� Tests for L{SynchronousTestCase.successResultOf}, L{SynchronousTestCase.failureResultOf}, and L{SynchronousTestCase.assertNoResult} when given a coroutine. r4 c � s �| j S r )r? r r r r � successResult� s �z.ResultOfCoroutineAssertionsTests.successResultc � s �t � I d H d S r )r r r r r �noCurrentResult� s �z0ResultOfCoroutineAssertionsTests.noCurrentResultNc � s �|d u r| j }|�r )r� �r r� r r r �raisesException� s �z0ResultOfCoroutineAssertionsTests.raisesExceptionc C � | � | j| j| �� � dS )z� L{SynchronousTestCase.successResultOf} raises L{SynchronousTestCase.failureException} when called with a coroutine with no current result. N)r� r< r6 rd r r r r r7 � � �z3ResultOfCoroutineAssertionsTests.test_withoutResultc C rg )z� L{SynchronousTestCase.successResultOf} raises L{SynchronousTestCase.failureException} when called with a coroutine that raises an exception. N)r� r< r6 rf r r r r �!test_successResultOfWithException� rh zBResultOfCoroutineAssertionsTests.test_successResultOfWithExceptionc C sh t d�}z | �| �|�� W dS | jy3 } z| �dt|�� | �dt|�� W Y d}~dS d}~ww )z� L{SynchronousTestCase.successResultOf} raises a L{SynchronousTestCase.failureException} that has the original failure traceback when called with a coroutine with a failure result. r4 zSuccess result expected on� builtins.Exception: Bad timesN)ra r6 rf r< r\ r �r r� r^ r r r r> � s ��zLResultOfCoroutineAssertionsTests.test_successResultOfWithFailureHasTracebackc C rg )z� L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a coroutine with no current result. N)r� r< r? rd r r r r r@ � rh zBResultOfCoroutineAssertionsTests.test_failureResultOfWithoutResultc C rg )z� L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a coroutine with a success result. N)r� r< r? rc r r r r rA � rh z@ResultOfCoroutineAssertionsTests.test_failureResultOfWithSuccessc C s | � | j| j| �� t� dS )z� L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a coroutine that raises an exception that was not expected. N)r� r< r? rf rB r r r r rC � s �zEResultOfCoroutineAssertionsTests.test_failureResultOfWithWrongFailurec C s\ z | � | �� t� W dS | jy- } z| �d�tjtj�t|�� W Y d}~dS d}~ww )aF L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a coroutine that raises an exception with a failure type that was not expected, and the L{SynchronousTestCase.failureException} message contains the expected exception type. rD N) r? rf rB r< r\ r� r r r r� r r r �:test_failureResultOfWithWrongExceptionOneExpectedException� s ����z[ResultOfCoroutineAssertionsTests.test_failureResultOfWithWrongExceptionOneExpectedExceptionc C sj t d�}z | �| �|�t� W dS | jy4 } z| �dt|�� | �dt|�� W Y d}~dS d}~ww )aK L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a coroutine that raises an exception with a failure type that was not expected, and the L{SynchronousTestCase.failureException} message contains the original exception traceback. r4 z/Failure of type (builtins.KeyError) expected onrj N)ra r? rf rB r< r\ r rk r r r �?test_failureResultOfWithWrongExceptionOneExpectedExceptionHasTB s ��z`ResultOfCoroutineAssertionsTests.test_failureResultOfWithWrongExceptionOneExpectedExceptionHasTBc C sf z | � | �� tt� W dS | jy2 } z| �d�tjtjtjtj�t |�� W Y d}~dS d}~ww )aN L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a coroutine that raises an exception of a type that was not expected, and the L{SynchronousTestCase.failureException} message contains expected exception types in the error message. rG N) r? rf rB rH r< r\ r� r r r r� r r r �=test_failureResultOfWithWrongExceptionMultiExpectedExceptions s ����z^ResultOfCoroutineAssertionsTests.test_failureResultOfWithWrongExceptionMultiExpectedExceptionsc C sl t d�}z | �| �|�tt� W dS | jy5 } z| �dt|�� | �dt|�� W Y d}~dS d}~ww )aV L{SynchronousTestCase.failureResultOf} raises L{SynchronousTestCase.failureException} when called with a coroutine that raises an exception of a type that was not expected, and the L{SynchronousTestCase.failureException} message contains the original exception traceback in the error message. r4 zCFailure of type (builtins.KeyError or builtins.OSError) expected onrj N)ra r? rf rB rH r< r\ r rk r r r �Btest_failureResultOfWithWrongExceptionMultiExpectedExceptionsHasTB2 s � ��zcResultOfCoroutineAssertionsTests.test_failureResultOfWithWrongExceptionMultiExpectedExceptionsHasTBc C s | � | j| �| �� �� dS )a$ When passed a coroutine which currently has a result (ie, if converted into a L{Deferred}, L{Deferred.addCallback} would cause the added callback to be called before C{addCallback} returns), L{SynchronousTestCase.successResultOf} returns that result. N)rL r? r6 rc r r r r rM E s zFResultOfCoroutineAssertionsTests.test_successResultOfWithSuccessResultc C s( | � | jj| �| �� | jjt�j� dS )ar When passed a coroutine which currently has an exception result (ie, if converted into a L{Deferred}, L{Deferred.addErrback} would cause the added errback to be called before C{addErrback} returns), L{SynchronousTestCase.failureResultOf} returns a L{Failure} containing that exception, if the exception type is expected. N)r= r: �valuer? rf r� rB r r r r �)test_failureResultOfWithExpectedExceptionN s ��zJResultOfCoroutineAssertionsTests.test_failureResultOfWithExpectedExceptionc C s | � | jj| �| �� �j� dS )aW When passed a coroutine which currently has an exception result (ie, if converted into a L{Deferred}, L{Deferred.addErrback} would cause the added errback to be called before C{addErrback} returns), L{SynchronousTestCase.failureResultOf} returns returns a L{Failure} containing that exception. N)r= r: rp r? rf r r r r �!test_failureResultOfWithException] s �zBResultOfCoroutineAssertionsTests.test_failureResultOfWithExceptionc C rg )z� When passed a coroutine which currently has a success result (see L{test_withSuccessResult}), L{SynchronousTestCase.assertNoResult} raises L{SynchronousTestCase.failureException}. N)r� r< rQ rc r r r r rR i rh z;ResultOfCoroutineAssertionsTests.test_assertNoResultSuccessc C rg )z� When passed a coroutine which currently has an exception result (see L{test_withFailureResult}), L{SynchronousTestCase.assertNoResult} raises L{SynchronousTestCase.failureException}. N)r� r< rQ rf r r r r rS s rh z;ResultOfCoroutineAssertionsTests.test_assertNoResultFailurec C s | � | �� � dS )z� When passed a coroutine with no current result, L{SynchronousTestCase.assertNoResult} does not raise an exception. N)rQ rd r r r r rT } s z4ResultOfCoroutineAssertionsTests.test_assertNoResultc sF t � � � fdd�}|� }| �� � � �| j� | �| j| �|�� dS )z� When passed a coroutine awaiting 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}. c � � �� I d H S r r r �rY r r rd � � � z^ResultOfCoroutineAssertionsTests.test_assertNoResultPropagatesSuccess.<locals>.noCurrentResultNrV )r rd �cr rt r rZ � s zEResultOfCoroutineAssertionsTests.test_assertNoResultPropagatesSuccessc sP t | j�}t� � � fdd�}|� }| �� � � �|� | �|j| �|�j� dS )z� When passed a coroutine awaiting 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}. c � rs r r r rt r r rd � ru zcResultOfCoroutineAssertionsTests.test_assertNoResultPropagatesLaterFailure.<locals>.noCurrentResultN)r r� r rQ r\ r= rp r? )r r) rd rv r rt r r] � s zJResultOfCoroutineAssertionsTests.test_assertNoResultPropagatesLaterFailurec sV t | j�� � fdd�}|� }z| �� � W n | jy Y nw | �d| �|�� dS )r^ c � rs r r r rt r r rf � ru zeResultOfCoroutineAssertionsTests.test_assertNoResultSwallowsImmediateFailure.<locals>.raisesExceptionNr_ )r rf rv r rt r r` � s �zLResultOfCoroutineAssertionsTests.test_assertNoResultSwallowsImmediateFailurer ) r r r r& r� r? ra r� r r: rc rd rf r7 ri r> r@ rA rC rl rm rn ro rM rq rr rR rS rT rZ r] r` r r r r rb � s6 rb 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 )�Not�_)r� )�.0�k��dctr r � <listcomp>� s & z3AssertionNamesTests._getAsserts.<locals>.<listcomp>)r r r r} r � _getAsserts� s z AssertionNamesTests._getAssertsc C s |j S r )r r� 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. rm N)�setr� r r= � intersection)r �asserts� failUnlessesr r r � test_failUnlessMatchesAssert� s z0AssertionNamesTests.test_failUnlessMatchesAssertc C s< t tjd�}t tjd�}| �t|| jd�t|| jd�� d S )N� assertNotra )�key)r r rJ r= �sortedr� )r r� �failIfsr r r � test_failIf_matches_assertNot� s �z1AssertionNamesTests.test_failIf_matches_assertNotc C s� t | ��� D ]R\}}t|�sq|�d�r0| �t| |d �|� d|� d�� | �|t| |d �� |�d�rX| �t| |d d� �|� d|d d� � �� | �|t| |d d� �� qd S )N�Equal�sz but no �Equals���)�vars�items�callable�endswithrk �hasattrr= r� )r r rp r r r �test_equalSpelling� s " ,��z&AssertionNamesTests.test_equalSpellingN) r r r r& r� r� r� r� r� r r r r rw � s rw 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. �Twisted� r c C s& | � | jtd� | �| �� g d� dS )zj callDeprecated calls a deprecated callable, suppressing the deprecation warning. r� zNo warnings should be shownN)�callDeprecated�version� oldMethodr= r0 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. r� N)r� r� r� r= r> 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 r� zGCallDeprecatedTests.test_failsWithoutDeprecation.<locals>.notDeprecatedz%r is not deprecated.N)r� r< r� r� r= r )r r� r� 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. �FoorA rT rV r� N) r r� r< r� r� r\ r r� r )r �differentVersionr� 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� rA rT rV c W s t | � S r )r� )�argsr r r �nestedDeprecation& r% zECallDeprecatedTests.test_nestedDeprecation.<locals>.nestedDeprecation� zUnexpected warnings: N)r r r� r0 r= rG )r r� r� � 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. � newMethodrA N)r� r� �oldMethodReplacedr r r r � test_callDeprecationWithMessage3 r� 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.wrongrA z please use newMethod insteadN)r� r< r� r� r� r\ r r re r r r �$test_callDeprecationWithWrongMessage: s �z8CallDeprecatedTests.test_callDeprecationWithWrongMessageN) r r r r& r r� r� r� r� r� r� r� r� r r r r r� � s r� c C r )z( Deprecated method for testing. r �rt r r r r� J s r� r� )� replacementc C s d| S )zh Another deprecated method, which has been deprecated in favor of the mythical 'newMethod'. rT r r� r r r r� R s r� c @ s> e Zd ZdZedddd�Zdd� Zdd � Zd d � Zd d � Z dS )�!GetDeprecatedModuleAttributeTestsz� Test L{SynchronousTestCase.getDeprecatedModuleAttribute} @ivar version: The version at which L{test_assertions.somethingOld} is marked deprecated. @type version: L{incremental.Version} �BarrA rT rV c C s, | � t| �td| j�� | �g | �� � dS )z� L{getDeprecatedModuleAttribute} returns the specified attribute and consumes the deprecation warning that generates. � somethingOldN�r� � _somethingOld� getDeprecatedModuleAttributer r� r= r0 r r r r �test_deprecatedf s ��z1GetDeprecatedModuleAttributeTests.test_deprecatedc C s0 | � t| jtd| jdd�� | �g | �� � dS )z� The I{message} argument to L{getDeprecatedModuleAttribute} matches the prefix of the deprecation message. r� zIt's oldr- Nr� r r r r � test_messageu s �� z.GetDeprecatedModuleAttributeTests.test_messagec C s. | � | j| jtd| jd� | �g | �� � dS )z� L{getDeprecatedModuleAttribute} fails the test if the I{message} isn't part of the deprecation message prefix. r� zIt's shiny and newN)r� r< r� r r� r= r0 r r r r �test_messageMismatch� s �z6GetDeprecatedModuleAttributeTests.test_messageMismatchc C s | � | j| jtd| j� dS )z� L{getDeprecatedModuleAttribute} fails the test when used to get an attribute that isn't actually deprecated. � somethingNewN)r� r< r� r r� r r r r �test_notDeprecated� s �z4GetDeprecatedModuleAttributeTests.test_notDeprecatedN) r r r r& r r� r� r� r� r� r r r r r� [ s r� c C � dS )zj A deprecated module attribute. Used by L{GetDeprecatedModuleAttributeTests.test_deprecated}. Nr r r r r r� � r� r� zIt's old and clunkyc C r� )zy A module attribute that is not deprecated. Used by L{GetDeprecatedModuleAttributeTests.test_notDeprecated}. Nr r r r r r� � r� r� ),r& r r1 r� � incrementalr r �twisted.internet.deferr r r �twisted.python.deprecater r �twisted.python.failurer �twisted.python.reflectr r r �twisted.python.utilr � twisted.trialr r! rv r) rJ rL rh rq r� r3 rb rw r� r� r� r� r� r� r� r r� r r r r �<module> sT 6MM O q b -c G�
修改文件时间
将文件时间修改为当前时间的前一年
删除文件