0x1998 - MANAGER
Düzenlenen Dosya: plugintest.cpython-37.pyc
B 2�Se�4 � @ s d Z ddlZddlZddlmZ yddlmZ W n ek rP ddlmZ Y nX ddgZddl m Z G dd � d e �Z ydd l mZ e ZW n ek r� eZY nX G d d� de �ZG d d � d e �Zdd� Zdd� Zdd� Zdd� Zdd� Zdd� Zdd� Zedk�rddlZe�� dS ) a_ Testing Plugins =============== The plugin interface is well-tested enough to safely unit test your use of its hooks with some level of confidence. However, there is also a mixin for unittest.TestCase called PluginTester that's designed to test plugins in their native runtime environment. Here's a simple example with a do-nothing plugin and a composed suite. >>> import unittest >>> from nose.plugins import Plugin, PluginTester >>> class FooPlugin(Plugin): ... pass >>> class TestPluginFoo(PluginTester, unittest.TestCase): ... activate = '--with-foo' ... plugins = [FooPlugin()] ... def test_foo(self): ... for line in self.output: ... # i.e. check for patterns ... pass ... ... # or check for a line containing ... ... assert "ValueError" in self.output ... def makeSuite(self): ... class TC(unittest.TestCase): ... def runTest(self): ... raise ValueError("I hate foo") ... return [TC('runTest')] ... >>> res = unittest.TestResult() >>> case = TestPluginFoo('test_foo') >>> _ = case(res) >>> res.errors [] >>> res.failures [] >>> res.wasSuccessful() True >>> res.testsRun 1 And here is a more complex example of testing a plugin that has extra arguments and reads environment variables. >>> import unittest, os >>> from nose.plugins import Plugin, PluginTester >>> class FancyOutputter(Plugin): ... name = "fancy" ... def configure(self, options, conf): ... Plugin.configure(self, options, conf) ... if not self.enabled: ... return ... self.fanciness = 1 ... if options.more_fancy: ... self.fanciness = 2 ... if 'EVEN_FANCIER' in self.env: ... self.fanciness = 3 ... ... def options(self, parser, env=os.environ): ... self.env = env ... parser.add_option('--more-fancy', action='store_true') ... Plugin.options(self, parser, env=env) ... ... def report(self, stream): ... stream.write("FANCY " * self.fanciness) ... >>> class TestFancyOutputter(PluginTester, unittest.TestCase): ... activate = '--with-fancy' # enables the plugin ... plugins = [FancyOutputter()] ... args = ['--more-fancy'] ... env = {'EVEN_FANCIER': '1'} ... ... def test_fancy_output(self): ... assert "FANCY FANCY FANCY" in self.output, ( ... "got: %s" % self.output) ... def makeSuite(self): ... class TC(unittest.TestCase): ... def runTest(self): ... raise ValueError("I hate fancy stuff") ... return [TC('runTest')] ... >>> res = unittest.TestResult() >>> case = TestFancyOutputter('test_fancy_output') >>> _ = case(res) >>> res.errors [] >>> res.failures [] >>> res.wasSuccessful() True >>> res.testsRun 1 � N)�warn)�StringIO� PluginTester�run)�getpidc @ sJ e Zd ZdZdd� Zdd� Zdd� Zdd � Zdd d �Zd d� Z dd� Z dS )�MultiProcessFilea\ helper for testing multiprocessing multiprocessing poses a problem for doctests, since the strategy of replacing sys.stdout/stderr with file-like objects then inspecting the results won't work: the child processes will write to the objects, but the data will not be reflected in the parent doctest-ing process. The solution is to create file-like objects which will interact with multiprocessing in a more desirable way. All processes can write to this object, but only the creator can read. This allows the testing system to see a unified picture of I/O. c C s& t � | _t� �� | _t� | _d| _d S )Nr )r �_MultiProcessFile__master�Manager�Queue�_MultiProcessFile__queuer �_MultiProcessFile__buffer� softspace)�self� r �H/opt/alt/python37/lib/python3.7/site-packages/nose/plugins/plugintest.py�__init__~ s zMultiProcessFile.__init__c C s� t � | jkrd S ddlm} ddlm} |t�}xJy| j�� \}}W n |k rZ P Y nX |dkrhd}|| |7 < q2W x t |�D ]}| j � || � q�W d S )Nr )�Empty)� defaultdictr )g}Ô%�I�T) r r �queuer � collectionsr �strr Z get_nowait�sortedr �write)r r r �cache�pid�datar r r �buffer� s zMultiProcessFile.bufferc C s( ddl m} |� j}| j�||f� d S )Nr )�current_process)�multiprocessingr � _identityr �put)r r r r r r r r � s zMultiProcessFile.writec C s | � � | jS )z getattr doesn't work for iter())r r )r r r r �__iter__� s zMultiProcessFile.__iter__r c C s | � � | j�||�S )N)r r �seek)r �offset�whencer r r r" � s zMultiProcessFile.seekc C s | � � | j�� S )N)r r �getvalue)r r r r r% � s zMultiProcessFile.getvaluec C s t | j|�S )N)�getattrr )r �attrr r r � __getattr__� s z MultiProcessFile.__getattr__N)r ) �__name__� __module__� __qualname__�__doc__r r r r! r" r% r( r r r r r n s r )r c @ sD e Zd ZdZdZdZdZi ZdZg Z dZ dd� Z dd� Z dd� Z dS ) r a% A mixin for testing nose plugins in their runtime environment. Subclass this and mix in unittest.TestCase to run integration/functional tests on your plugin. When setUp() is called, the stub test suite is executed with your plugin so that during an actual test you can inspect the artifacts of how your plugin interacted with the stub test suite. - activate - the argument to send nosetests to activate the plugin - suitepath - if set, this is the path of the suite to test. Otherwise, you will need to use the hook, makeSuite() - plugins - the list of plugins to make available during the run. Note that this does not mean these plugins will be *enabled* during the run -- only the plugins enabled by the activate argument or other settings in argv or env will be enabled. - args - a list of arguments to add to the nosetests command, in addition to the activate argument - env - optional dict of environment variables to send nosetests Nc C s t �dS )a� returns a suite object of tests to run (unittest.TestSuite()) If self.suitepath is None, this must be implemented. The returned suite object will be executed with all plugins activated. It may return None. Here is an example of a basic suite object you can return :: >>> import unittest >>> class SomeTest(unittest.TestCase): ... def runTest(self): ... raise ValueError("Now do something, plugin!") ... >>> unittest.TestSuite([SomeTest()]) # doctest: +ELLIPSIS <unittest...TestSuite tests=[<...SomeTest testMethod=runTest>]> N)�NotImplementedError)r r r r � makeSuite� s zPluginTester.makeSuitec C s� ddl m} ddlm} ddlm} d}t� }|| j||| jd�d�}| j dk rX| j |_ | j sf| � � }|| j ||dd �| _ t|�| _dS ) z7execute the plugin on the internal test suite. r )�Config)� TestProgram)� PluginManagerN)�plugins)�env�streamr2 F)�argv�config�suite�exit)� nose.configr/ Z nose.corer0 �nose.plugins.managerr1 �Bufferr3 r2 � ignoreFiles� suitepathr. r5 �nose�AccessDecorator�output)r r/ r0 r1 r7 r4 Zconfr r r � _execPlugin� s zPluginTester._execPluginc C s@ d| j g| _| jr | j�| j� | jr4| j�| j� | �� dS )zUruns nosetests with the specified test suite, all plugins activated. � nosetestsN)�activater5 �args�extendr= �appendrA )r r r r �setUp s zPluginTester.setUp)r) r* r+ r, rC r= rD r3 r5 r2 r< r. rA rG r r r r r � s !c @ s4 e Zd ZdZdZdd� Zdd� Zdd� Zdd � ZdS ) r? Nc C s( || _ |�d� |�� | _|�d� d S )Nr )r4 r" �read�_buf)r r4 r r r r s zAccessDecorator.__init__c C s || j kS )N)rI )r �valr r r � __contains__ s z AccessDecorator.__contains__c C s t | j�S )N)�iterr4 )r r r r r! s zAccessDecorator.__iter__c C s | j S )N)rI )r r r r �__str__ s zAccessDecorator.__str__) r) r* r+ r4 rI r rK r! rM r r r r r? s r? c c sf g }xL| � d�D ]>}|�|� |�� }|r>|�d�r|�d�sd�|�V g }qW |rbd�|�V dS )z9a bunch of === characters is also considered a blank lineTz===�=� N)� splitlinesrF �strip� startswith�join)�text�block�liner r r �blankline_separated_blocks# s rW c C sL t �dt jt jB t jB �}g }x"t| �D ]}|�|�d|�� q(W d�|�S )NaD # Grab the traceback header. Different versions of Python have # said different things on the first traceback line. ^(?P<hdr> Traceback\ \( (?: most\ recent\ call\ last | innermost\ last ) \) : ) \s* $ # toss trailing whitespace on the header. (?P<stack> .*?) # don't blink: absorb stuff until... ^(?=\w) # a line *starts* with alphanum. .*?(?P<exception> \w+ ) # exception name (?P<msg> [:\n] .*) # the rest z"\g<hdr>\n...\n\g<exception>\g<msg>rO ) �re�compile�VERBOSE� MULTILINE�DOTALLrW rF �subrS )�outZ traceback_reZblocksrU r r r �remove_stack_traces0 s r_ c C s t �dt jt jB �}|�d| �S )Nz� # Cut the file and line no, up to the warning name ^.*:\d+:\s (?P<category>\w+): \s+ # warning category (?P<detail>.+) $ \n? # warning message ^ .* $ # stack frame z\g<category>: \g<detail>)rX rY rZ r[ r] )r^ Zwarn_rer r r �simplify_warningsF s r` c C s t �dd| �S )Nz Ran (\d+ tests?) in [0-9.]+szRan \1 in ...s)rX r] )r^ r r r �remove_timingsQ s ra c C s t | �} t| �} t| �} | �� S )z6Modify nose output to make it easy to use in doctests.)r_ r` ra rQ )r^ r r r � munge_nose_output_for_doctestV s rb c O s ddl m} ddlm} ddlm} t� }d|krn|�dg �}t|t �rR||d�}|�di �}|||d �|d< d |kr�d d g|d < ||d _ t j }t j } |�d d�r�| t _ t _ d} nd} tdtdd� z|| |� W d| r�|t _ | t _ X |�� } tt| �� dS )a� Specialized version of nose.run for use inside of doctests that test test runs. This version of run() prints the result output to stdout. Before printing, the output is processed by replacing the timing information with an ellipsis (...), removing traceback stacks, and removing trailing whitespace. Use this version of run wherever you are writing a doctest that tests nose (or unittest) test result output. Note: do not use doctest: +ELLIPSIS when testing nose output, since ellipses ("test_foo ... ok") in your expected test runner output may match multiple lines of output, causing spurious test passes! r )r )r/ )r1 r6 r2 )r2 r3 )r3 r2 r5 rB z-v� buffer_allFTa The behavior of nose.plugins.plugintest.run() will change in the next release of nose. The current behavior does not correctly account for output to stdout and stderr. To enable correct behavior, use run_buffered() instead, or pass the keyword argument buffer_all=True to run().� )� stacklevelN)r> r r9 r/ r: r1 r; �pop� isinstance�listr4 �sys�stderr�stdoutr �DeprecationWarningr% �printrb ) �arg�kwr r/ r1 r r2 r3 rj rk �restorer^ r r r r ^ s8 c O s d|d< t | |� d S )NTrc )r )rn ro r r r � run_buffered� s rq �__main__) r, rX ri �warningsr �ior � ImportError�__all__�osr �objectr r r r; r r? rW r_ r` ra rb r rq r) �doctest�testmodr r r r �<module>` s6 ? ` <
geri dön