Your IP : 216.73.216.213

Current Path : /opt/alt/python35/lib/python3.5/site-packages/nose/plugins/__pycache__/
Upload File :
Current File : //opt/alt/python35/lib/python3.5/site-packages/nose/plugins/__pycache__/plugintest.cpython-35.pyc



�^�]�4�@stdZddlZddlZddlmZyddlmZWn"ek
rfddlmZYnXddgZddl	m
Z
Gdd	�d	e�Zydd
l
mZeZWnek
r�eZYnXGdd�de�ZGdd
�d
e�Zdd�Zdd�Zdd�Zdd�Zdd�Zdd�Zdd�ZedkrpddlZej�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@smeZdZdZdd�Zdd�Zdd�Zdd	�Zd
dd�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.
    cCs7t�|_t�j�|_t�|_d|_dS)Nr)r�_MultiProcessFile__master�Manager�Queue�_MultiProcessFile__queuer�_MultiProcessFile__buffer�	softspace)�self�r�H/opt/alt/python35/lib/python3.5/site-packages/nose/plugins/plugintest.py�__init__~szMultiProcessFile.__init__cCs�t�|jkrdSddlm}ddlm}|t�}xSy|jj�\}}Wn|k
rsPYnX|fkr�d}|||7<qEWx(t	|�D]}|j
j||�q�WdS)Nr)�Empty)�defaultdict�}Ô%�I�T)r)rr�queuer�collectionsr�strrZ
get_nowait�sortedr�write)rrr�cache�pid�datarrr�buffer�s
zMultiProcessFile.buffercCs6ddlm}|�j}|jj||f�dS)Nr)�current_process)�multiprocessingr�	_identityr�put)rrrrrrrr�szMultiProcessFile.writecCs|j�|jS)zgetattr doesn't work for iter())rr)rrrr�__iter__�s
zMultiProcessFile.__iter__rcCs|j�|jj||�S)N)rr�seek)r�offset�whencerrrr#�s
zMultiProcessFile.seekcCs|j�|jj�S)N)rr�getvalue)rrrrr&�s
zMultiProcessFile.getvaluecCst|j|�S)N)�getattrr)r�attrrrr�__getattr__�szMultiProcessFile.__getattr__N)�__name__�
__module__�__qualname__�__doc__rrrr"r#r&r)rrrrrnsr)r	c@sdeZdZdZdZdZdZiZdZgZ	dZ
dd�Zdd�Zdd�Z
dS)	ra%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

    NcCs
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)rrrr�	makeSuite�szPluginTester.makeSuitec	Cs�ddlm}ddlm}ddlm}d}t�}|d|jd|d|d|j��}|j	dk	r�|j	|_	|j
s�|j�}|d	|jd
|d|dd
�|_
t|�|_dS)z7execute the plugin on the internal test suite.
        r)�Config)�TestProgram)�
PluginManagerN�env�stream�plugins�argv�config�suite�exitF)�nose.configr0Z	nose.corer1�nose.plugins.managerr2�Bufferr3r5�ignoreFiles�	suitepathr/r6�nose�AccessDecorator�output)rr0r1r2r8r4Zconfrrr�_execPlugin�s		zPluginTester._execPlugincCsXd|jg|_|jr.|jj|j�|jrJ|jj|j�|j�dS)zUruns nosetests with the specified test suite, all plugins
        activated.
        �	nosetestsN)�activater6�args�extendr>�appendrB)rrrr�setUps		zPluginTester.setUp)r*r+r,r-rDr>rEr3r6r5r=r/rBrHrrrrr�s!c@sLeZdZdZdZdd�Zdd�Zdd�Zdd	�ZdS)
r@NcCs6||_|jd�|j�|_|jd�dS)Nr)r4r#�read�_buf)rr4rrrrs	
zAccessDecorator.__init__cCs
||jkS)N)rJ)r�valrrr�__contains__szAccessDecorator.__contains__cCs
t|j�S)N)�iterr4)rrrrr"szAccessDecorator.__iter__cCs|jS)N)rJ)rrrr�__str__szAccessDecorator.__str__)	r*r+r,r4rJrrLr"rNrrrrr@sr@ccs�g}xj|jd�D]Y}|j|�|j�}|s[|jd�r|jd�rdj|�Vg}qW|r�dj|�VdS)z9a bunch of === characters is also considered a blank lineTz===�=�N)�
splitlinesrG�strip�
startswith�join)�text�block�linerrr�blankline_separated_blocks#s
&
rXcCsftjdtjtjBtjB�}g}x-t|�D]}|j|jd|��q6Wdj|�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>rP)	�re�compile�VERBOSE�	MULTILINE�DOTALLrXrG�subrT)�outZtraceback_reZblocksrVrrr�remove_stack_traces0s
r`cCs,tjdtjtjB�}|jd|�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>)rYrZr[r\r^)r_Zwarn_rerrr�simplify_warningsFsracCstjdd|�S)NzRan (\d+ tests?) in [0-9.]+szRan \1 in ...s)rYr^)r_rrr�remove_timingsQsrbcCs.t|�}t|�}t|�}|j�S)z6Modify nose output to make it easy to use in doctests.)r`rarbrR)r_rrr�munge_nose_output_for_doctestVsrccOslddlm}ddlm}ddlm}t�}d|kr�|jdg�}t|t	�ru|d|�}|jdi�}|d|d|�|d<d|kr�d	d
g|d<||d_
tj}tj
}	|jdd�r|t_
t_d
}
nd}
tdtdd�z|||�Wd|
rK|t_|	t_
X|j�}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)r0)r2r7r5r3r6rCz-v�
buffer_allFTaThe 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().�
stacklevel�N)r?rr:r0r;r2r<�pop�
isinstance�listr4�sys�stderr�stdoutr�DeprecationWarningr&�printrc)�arg�kwrr0r2rr5r3rkrl�restorer_rrrr^s8	
			
	
cOsd|d<t||�dS)NTrd)r)rorprrr�run_buffered�s
rr�__main__)r-rYrj�warningsr�ior�ImportError�__all__�osr�objectrrr	r<rr@rXr`rarbrcrrrr*�doctest�testmodrrrr�<module>`s6
?

`
<