This file is indexed.

/usr/share/doc/python-pytest/html/unittest.html is in python-pytest-doc 3.3.2-2.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>unittest.TestCase Support &#8212; pytest documentation</title>
    <link rel="stylesheet" href="_static/flasky.css" type="text/css" />
    <link rel="stylesheet" href="_static/pygments.css" type="text/css" />
    <script type="text/javascript">
      var DOCUMENTATION_OPTIONS = {
        URL_ROOT:    './',
        VERSION:     '3.3',
        COLLAPSE_INDEX: false,
        FILE_SUFFIX: '.html',
        HAS_SOURCE:  true,
        SOURCELINK_SUFFIX: '.txt'
      };
    </script>
    <script type="text/javascript" src="_static/jquery.js"></script>
    <script type="text/javascript" src="_static/underscore.js"></script>
    <script type="text/javascript" src="_static/doctools.js"></script>
    <link rel="shortcut icon" href="_static/pytest1favi.ico"/>
    <link rel="search" title="Search" href="search.html" />
    <link rel="next" title="Running tests written for nose" href="nose.html" />
    <link rel="prev" title="Cache: working with cross-testrun state" href="cache.html" />
   
  
  <meta name="viewport" content="width=device-width, initial-scale=0.9, maximum-scale=0.9">

  </head>
  <body>
  
  
  


    <div class="related" role="navigation" aria-label="related navigation">
      <h3>Navigation</h3>
      <ul>
        <li class="right" style="margin-right: 10px">
          <a href="nose.html" title="Running tests written for nose"
             accesskey="N">next</a></li>
        <li class="right" >
          <a href="cache.html" title="Cache: working with cross-testrun state"
             accesskey="P">previous</a> |</li>
        <li class="nav-item nav-item-0"><a href="contents.html">pytest-3.3</a> &#187;</li> 
      </ul>
    </div>  

    <div class="document">
      <div class="documentwrapper">
        <div class="bodywrapper">
          <div class="body" role="main">
            
  <div class="section" id="unittest-testcase-support">
<span id="unittest"></span><span id="unittest-testcase"></span><h1>unittest.TestCase Support<a class="headerlink" href="#unittest-testcase-support" title="Permalink to this headline"></a></h1>
<p><code class="docutils literal"><span class="pre">pytest</span></code> supports running Python <code class="docutils literal"><span class="pre">unittest</span></code>-based tests out of the box.
It's meant for leveraging existing <code class="docutils literal"><span class="pre">unittest</span></code>-based test suites
to use pytest as a test runner and also allow to incrementally adapt
the test suite to take full advantage of pytest's features.</p>
<p>To run an existing <code class="docutils literal"><span class="pre">unittest</span></code>-style test suite using <code class="docutils literal"><span class="pre">pytest</span></code>, type:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">pytest</span> <span class="n">tests</span>
</pre></div>
</div>
<p>pytest will automatically collect <code class="docutils literal"><span class="pre">unittest.TestCase</span></code> subclasses and
their <code class="docutils literal"><span class="pre">test</span></code> methods in <code class="docutils literal"><span class="pre">test_*.py</span></code> or <code class="docutils literal"><span class="pre">*_test.py</span></code> files.</p>
<p>Almost all <code class="docutils literal"><span class="pre">unittest</span></code> features are supported:</p>
<ul class="simple">
<li><code class="docutils literal"><span class="pre">&#64;unittest.skip</span></code> style decorators;</li>
<li><code class="docutils literal"><span class="pre">setUp/tearDown</span></code>;</li>
<li><code class="docutils literal"><span class="pre">setUpClass/tearDownClass()</span></code>;</li>
</ul>
<p>Up to this point pytest does not have support for the following features:</p>
<ul class="simple">
<li><a class="reference external" href="https://docs.python.org/3/library/unittest.html#load-tests-protocol">load_tests protocol</a>;</li>
<li><a class="reference external" href="https://docs.python.org/3/library/unittest.html#setupmodule-and-teardownmodule">setUpModule/tearDownModule</a>;</li>
<li><a class="reference external" href="https://docs.python.org/3/library/unittest.html#distinguishing-test-iterations-using-subtests">subtests</a>;</li>
</ul>
<div class="section" id="benefits-out-of-the-box">
<h2>Benefits out of the box<a class="headerlink" href="#benefits-out-of-the-box" title="Permalink to this headline"></a></h2>
<p>By running your test suite with pytest you can make use of several features,
in most cases without having to modify existing code:</p>
<ul class="simple">
<li>Obtain <a class="reference internal" href="example/reportingdemo.html#tbreportdemo"><span class="std std-ref">more informative tracebacks</span></a>;</li>
<li><a class="reference internal" href="capture.html#captures"><span class="std std-ref">stdout and stderr</span></a> capturing;</li>
<li><a class="reference internal" href="usage.html#select-tests"><span class="std std-ref">Test selection options</span></a> using <code class="docutils literal"><span class="pre">-k</span></code> and <code class="docutils literal"><span class="pre">-m</span></code> flags;</li>
<li><a class="reference internal" href="usage.html#maxfail"><span class="std std-ref">Stopping after the first (or N) failures</span></a>;</li>
<li><a class="reference internal" href="usage.html#pdb-option"><span class="std std-ref">--pdb</span></a> command-line option for debugging on test failures
(see <a class="reference internal" href="#pdb-unittest-note"><span class="std std-ref">note</span></a> below);</li>
<li>Distribute tests to multiple CPUs using the <a class="reference external" href="http://pypi.python.org/pypi/pytest-xdist">pytest-xdist</a> plugin;</li>
<li>Use <a class="reference internal" href="assert.html#assert"><span class="std std-ref">plain assert-statements</span></a> instead of <code class="docutils literal"><span class="pre">self.assert*</span></code> functions (<a class="reference external" href="https://pypi.python.org/pypi/unittest2pytest/">unittest2pytest</a> is immensely helpful in this);</li>
</ul>
</div>
<div class="section" id="pytest-features-in-unittest-testcase-subclasses">
<h2>pytest features in <code class="docutils literal"><span class="pre">unittest.TestCase</span></code> subclasses<a class="headerlink" href="#pytest-features-in-unittest-testcase-subclasses" title="Permalink to this headline"></a></h2>
<p>The following pytest features work in <code class="docutils literal"><span class="pre">unittest.TestCase</span></code> subclasses:</p>
<ul class="simple">
<li><a class="reference internal" href="mark.html#mark"><span class="std std-ref">Marks</span></a>: <a class="reference internal" href="skipping.html#skip"><span class="std std-ref">skip</span></a>, <a class="reference internal" href="skipping.html#skipif"><span class="std std-ref">skipif</span></a>, <a class="reference internal" href="skipping.html#xfail"><span class="std std-ref">xfail</span></a>;</li>
<li><a class="reference internal" href="#mixing-fixtures"><span class="std std-ref">Auto-use fixtures</span></a>;</li>
</ul>
<p>The following pytest features <strong>do not</strong> work, and probably
never will due to different design philosophies:</p>
<ul class="simple">
<li><a class="reference internal" href="fixture.html#fixture"><span class="std std-ref">Fixtures</span></a> (except for <code class="docutils literal"><span class="pre">autouse</span></code> fixtures, see <a class="reference internal" href="#mixing-fixtures"><span class="std std-ref">below</span></a>);</li>
<li><a class="reference internal" href="parametrize.html#parametrize"><span class="std std-ref">Parametrization</span></a>;</li>
<li><a class="reference internal" href="writing_plugins.html#writing-plugins"><span class="std std-ref">Custom hooks</span></a>;</li>
</ul>
<p>Third party plugins may or may not work well, depending on the plugin and the test suite.</p>
</div>
<div class="section" id="mixing-pytest-fixtures-into-unittest-testcase-subclasses-using-marks">
<span id="mixing-fixtures"></span><h2>Mixing pytest fixtures into <code class="docutils literal"><span class="pre">unittest.TestCase</span></code> subclasses using marks<a class="headerlink" href="#mixing-pytest-fixtures-into-unittest-testcase-subclasses-using-marks" title="Permalink to this headline"></a></h2>
<p>Running your unittest with <code class="docutils literal"><span class="pre">pytest</span></code> allows you to use its
<a class="reference internal" href="fixture.html#fixture"><span class="std std-ref">fixture mechanism</span></a> with <code class="docutils literal"><span class="pre">unittest.TestCase</span></code> style
tests.  Assuming you have at least skimmed the pytest fixture features,
let's jump-start into an example that integrates a pytest <code class="docutils literal"><span class="pre">db_class</span></code>
fixture, setting up a class-cached database object, and then reference
it from a unittest-style test:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="c1"># content of conftest.py</span>

<span class="c1"># we define a fixture function below and it will be &quot;used&quot; by</span>
<span class="c1"># referencing its name from tests</span>

<span class="kn">import</span> <span class="nn">pytest</span>

<span class="nd">@pytest</span><span class="o">.</span><span class="n">fixture</span><span class="p">(</span><span class="n">scope</span><span class="o">=</span><span class="s2">&quot;class&quot;</span><span class="p">)</span>
<span class="k">def</span> <span class="nf">db_class</span><span class="p">(</span><span class="n">request</span><span class="p">):</span>
    <span class="k">class</span> <span class="nc">DummyDB</span><span class="p">(</span><span class="nb">object</span><span class="p">):</span>
        <span class="k">pass</span>
    <span class="c1"># set a class attribute on the invoking test context</span>
    <span class="n">request</span><span class="o">.</span><span class="n">cls</span><span class="o">.</span><span class="n">db</span> <span class="o">=</span> <span class="n">DummyDB</span><span class="p">()</span>
</pre></div>
</div>
<p>This defines a fixture function <code class="docutils literal"><span class="pre">db_class</span></code> which - if used - is
called once for each test class and which sets the class-level
<code class="docutils literal"><span class="pre">db</span></code> attribute to a <code class="docutils literal"><span class="pre">DummyDB</span></code> instance.  The fixture function
achieves this by receiving a special <code class="docutils literal"><span class="pre">request</span></code> object which gives
access to <a class="reference internal" href="fixture.html#request-context"><span class="std std-ref">the requesting test context</span></a> such
as the <code class="docutils literal"><span class="pre">cls</span></code> attribute, denoting the class from which the fixture
is used.  This architecture de-couples fixture writing from actual test
code and allows re-use of the fixture by a minimal reference, the fixture
name.  So let's write an actual <code class="docutils literal"><span class="pre">unittest.TestCase</span></code> class using our
fixture definition:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="c1"># content of test_unittest_db.py</span>

<span class="kn">import</span> <span class="nn">unittest</span>
<span class="kn">import</span> <span class="nn">pytest</span>

<span class="nd">@pytest</span><span class="o">.</span><span class="n">mark</span><span class="o">.</span><span class="n">usefixtures</span><span class="p">(</span><span class="s2">&quot;db_class&quot;</span><span class="p">)</span>
<span class="k">class</span> <span class="nc">MyTest</span><span class="p">(</span><span class="n">unittest</span><span class="o">.</span><span class="n">TestCase</span><span class="p">):</span>
    <span class="k">def</span> <span class="nf">test_method1</span><span class="p">(</span><span class="bp">self</span><span class="p">):</span>
        <span class="k">assert</span> <span class="nb">hasattr</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="s2">&quot;db&quot;</span><span class="p">)</span>
        <span class="k">assert</span> <span class="mi">0</span><span class="p">,</span> <span class="bp">self</span><span class="o">.</span><span class="n">db</span>   <span class="c1"># fail for demo purposes</span>

    <span class="k">def</span> <span class="nf">test_method2</span><span class="p">(</span><span class="bp">self</span><span class="p">):</span>
        <span class="k">assert</span> <span class="mi">0</span><span class="p">,</span> <span class="bp">self</span><span class="o">.</span><span class="n">db</span>   <span class="c1"># fail for demo purposes</span>
</pre></div>
</div>
<p>The <code class="docutils literal"><span class="pre">&#64;pytest.mark.usefixtures(&quot;db_class&quot;)</span></code> class-decorator makes sure that
the pytest fixture function <code class="docutils literal"><span class="pre">db_class</span></code> is called once per class.
Due to the deliberately failing assert statements, we can take a look at
the <code class="docutils literal"><span class="pre">self.db</span></code> values in the traceback:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span>$ pytest test_unittest_db.py
=========================== test session starts ============================
platform linux -- Python 3.x.y, pytest-3.x.y, py-1.x.y, pluggy-0.x.y
rootdir: $REGENDOC_TMPDIR, inifile:
collected 2 items

test_unittest_db.py FF                                               [100%]

================================= FAILURES =================================
___________________________ MyTest.test_method1 ____________________________

self = &lt;test_unittest_db.MyTest testMethod=test_method1&gt;

    def test_method1(self):
        assert hasattr(self, &quot;db&quot;)
&gt;       assert 0, self.db   # fail for demo purposes
E       AssertionError: &lt;conftest.db_class.&lt;locals&gt;.DummyDB object at 0xdeadbeef&gt;
E       assert 0

test_unittest_db.py:9: AssertionError
___________________________ MyTest.test_method2 ____________________________

self = &lt;test_unittest_db.MyTest testMethod=test_method2&gt;

    def test_method2(self):
&gt;       assert 0, self.db   # fail for demo purposes
E       AssertionError: &lt;conftest.db_class.&lt;locals&gt;.DummyDB object at 0xdeadbeef&gt;
E       assert 0

test_unittest_db.py:12: AssertionError
========================= 2 failed in 0.12 seconds =========================
</pre></div>
</div>
<p>This default pytest traceback shows that the two test methods
share the same <code class="docutils literal"><span class="pre">self.db</span></code> instance which was our intention
when writing the class-scoped fixture function above.</p>
</div>
<div class="section" id="using-autouse-fixtures-and-accessing-other-fixtures">
<h2>Using autouse fixtures and accessing other fixtures<a class="headerlink" href="#using-autouse-fixtures-and-accessing-other-fixtures" title="Permalink to this headline"></a></h2>
<p>Although it's usually better to explicitly declare use of fixtures you need
for a given test, you may sometimes want to have fixtures that are
automatically used in a given context.  After all, the traditional
style of unittest-setup mandates the use of this implicit fixture writing
and chances are, you are used to it or like it.</p>
<p>You can flag fixture functions with <code class="docutils literal"><span class="pre">&#64;pytest.fixture(autouse=True)</span></code>
and define the fixture function in the context where you want it used.
Let's look at an <code class="docutils literal"><span class="pre">initdir</span></code> fixture which makes all test methods of a
<code class="docutils literal"><span class="pre">TestCase</span></code> class execute in a temporary directory with a
pre-initialized <code class="docutils literal"><span class="pre">samplefile.ini</span></code>.  Our <code class="docutils literal"><span class="pre">initdir</span></code> fixture itself uses
the pytest builtin <a class="reference internal" href="tmpdir.html#tmpdir"><span class="std std-ref">tmpdir</span></a> fixture to delegate the
creation of a per-test temporary directory:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="c1"># content of test_unittest_cleandir.py</span>
<span class="kn">import</span> <span class="nn">pytest</span>
<span class="kn">import</span> <span class="nn">unittest</span>

<span class="k">class</span> <span class="nc">MyTest</span><span class="p">(</span><span class="n">unittest</span><span class="o">.</span><span class="n">TestCase</span><span class="p">):</span>

    <span class="nd">@pytest</span><span class="o">.</span><span class="n">fixture</span><span class="p">(</span><span class="n">autouse</span><span class="o">=</span><span class="kc">True</span><span class="p">)</span>
    <span class="k">def</span> <span class="nf">initdir</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">tmpdir</span><span class="p">):</span>
        <span class="n">tmpdir</span><span class="o">.</span><span class="n">chdir</span><span class="p">()</span> <span class="c1"># change to pytest-provided temporary directory</span>
        <span class="n">tmpdir</span><span class="o">.</span><span class="n">join</span><span class="p">(</span><span class="s2">&quot;samplefile.ini&quot;</span><span class="p">)</span><span class="o">.</span><span class="n">write</span><span class="p">(</span><span class="s2">&quot;# testdata&quot;</span><span class="p">)</span>

    <span class="k">def</span> <span class="nf">test_method</span><span class="p">(</span><span class="bp">self</span><span class="p">):</span>
        <span class="k">with</span> <span class="nb">open</span><span class="p">(</span><span class="s2">&quot;samplefile.ini&quot;</span><span class="p">)</span> <span class="k">as</span> <span class="n">f</span><span class="p">:</span>
            <span class="n">s</span> <span class="o">=</span> <span class="n">f</span><span class="o">.</span><span class="n">read</span><span class="p">()</span>
        <span class="k">assert</span> <span class="s2">&quot;testdata&quot;</span> <span class="ow">in</span> <span class="n">s</span>
</pre></div>
</div>
<p>Due to the <code class="docutils literal"><span class="pre">autouse</span></code> flag the <code class="docutils literal"><span class="pre">initdir</span></code> fixture function will be
used for all methods of the class where it is defined.  This is a
shortcut for using a <code class="docutils literal"><span class="pre">&#64;pytest.mark.usefixtures(&quot;initdir&quot;)</span></code> marker
on the class like in the previous example.</p>
<p>Running this test module ...:</p>
<div class="highlight-default"><div class="highlight"><pre><span></span>$ pytest -q test_unittest_cleandir.py
.                                                                    [100%]
1 passed in 0.12 seconds
</pre></div>
</div>
<p>... gives us one passed test because the <code class="docutils literal"><span class="pre">initdir</span></code> fixture function
was executed ahead of the <code class="docutils literal"><span class="pre">test_method</span></code>.</p>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p><code class="docutils literal"><span class="pre">unittest.TestCase</span></code> methods cannot directly receive fixture
arguments as implementing that is likely to inflict
on the ability to run general unittest.TestCase test suites.</p>
<p>The above <code class="docutils literal"><span class="pre">usefixtures</span></code> and <code class="docutils literal"><span class="pre">autouse</span></code> examples should help to mix in
pytest fixtures into unittest suites.</p>
<p class="last">You can also gradually move away from subclassing from <code class="docutils literal"><span class="pre">unittest.TestCase</span></code> to <em>plain asserts</em>
and then start to benefit from the full pytest feature set step by step.</p>
</div>
<div class="admonition note" id="pdb-unittest-note">
<p class="first admonition-title">Note</p>
<p class="last">Running tests from <code class="docutils literal"><span class="pre">unittest.TestCase</span></code> subclasses with <code class="docutils literal"><span class="pre">--pdb</span></code> will
disable tearDown and cleanup methods for the case that an Exception
occurs. This allows proper post mortem debugging for all applications
which have significant logic in their tearDown machinery. However,
supporting this feature has the following side effect: If people
overwrite <code class="docutils literal"><span class="pre">unittest.TestCase</span></code> <code class="docutils literal"><span class="pre">__call__</span></code> or <code class="docutils literal"><span class="pre">run</span></code>, they need to
to overwrite <code class="docutils literal"><span class="pre">debug</span></code> in the same way  (this is also true for standard
unittest).</p>
</div>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">Due to architectural differences between the two frameworks, setup and
teardown for <code class="docutils literal"><span class="pre">unittest</span></code>-based tests is performed during the <code class="docutils literal"><span class="pre">call</span></code> phase
of testing instead of in <code class="docutils literal"><span class="pre">pytest</span></code>'s standard <code class="docutils literal"><span class="pre">setup</span></code> and <code class="docutils literal"><span class="pre">teardown</span></code>
stages. This can be important to understand in some situations, particularly
when reasoning about errors. For example, if a <code class="docutils literal"><span class="pre">unittest</span></code>-based suite
exhibits errors during setup, <code class="docutils literal"><span class="pre">pytest</span></code> will report no errors during its
<code class="docutils literal"><span class="pre">setup</span></code> phase and will instead raise the error during <code class="docutils literal"><span class="pre">call</span></code>.</p>
</div>
</div>
</div>


          </div>
        </div>
      </div>
      <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
        <div class="sphinxsidebarwrapper">
            <p class="logo"><a href="contents.html">
              <img class="logo" src="_static/pytest1.png" alt="Logo"/>
            </a></p><h3><a href="contents.html">Table Of Contents</a></h3>

<ul>
  <li><a href="index.html">Home</a></li>
  <li><a href="contents.html">Contents</a></li>
  <li><a href="getting-started.html">Install</a></li>
  <li><a href="example/index.html">Examples</a></li>
  <li><a href="customize.html">Customize</a></li>
  <li><a href="contact.html">Contact</a></li>
  <li><a href="talks.html">Talks/Posts</a></li>
  <li><a href="changelog.html">Changelog</a></li>
  <li><a href="backwards-compatibility.html">Backwards Compatibility</a></li>
  <li><a href="license.html">License</a></li>
</ul>
  <hr>
  <ul>
<li><a class="reference internal" href="#">unittest.TestCase Support</a><ul>
<li><a class="reference internal" href="#benefits-out-of-the-box">Benefits out of the box</a></li>
<li><a class="reference internal" href="#pytest-features-in-unittest-testcase-subclasses">pytest features in <code class="docutils literal"><span class="pre">unittest.TestCase</span></code> subclasses</a></li>
<li><a class="reference internal" href="#mixing-pytest-fixtures-into-unittest-testcase-subclasses-using-marks">Mixing pytest fixtures into <code class="docutils literal"><span class="pre">unittest.TestCase</span></code> subclasses using marks</a></li>
<li><a class="reference internal" href="#using-autouse-fixtures-and-accessing-other-fixtures">Using autouse fixtures and accessing other fixtures</a></li>
</ul>
</li>
</ul>
<h3>Related Topics</h3>
<ul>
  <li><a href="contents.html">Documentation overview</a><ul>
      <li>Previous: <a href="cache.html" title="previous chapter">Cache: working with cross-testrun state</a></li>
      <li>Next: <a href="nose.html" title="next chapter">Running tests written for nose</a></li>
  </ul></li>
</ul><h3>Useful Links</h3>
<ul>
  <li><a href="index.html">The pytest Website</a></li>
  <li><a href="contributing.html">Contribution Guide</a></li>
  <li><a href="https://pypi.python.org/pypi/pytest">pytest @ PyPI</a></li>
  <li><a href="https://github.com/pytest-dev/pytest/">pytest @ GitHub</a></li>
  <li><a href="http://plugincompat.herokuapp.com/">3rd party plugins</a></li>
  <li><a href="https://github.com/pytest-dev/pytest/issues">Issue Tracker</a></li>
  <li><a href="https://media.readthedocs.org/pdf/pytest/latest/pytest.pdf">PDF Documentation</a>
</ul>

<div id="searchbox" style="display: none" role="search">
  <h3>Quick search</h3>
    <form class="search" action="search.html" method="get">
      <div><input type="text" name="q" /></div>
      <div><input type="submit" value="Go" /></div>
      <input type="hidden" name="check_keywords" value="yes" />
      <input type="hidden" name="area" value="default" />
    </form>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
        </div>
      </div>
      <div class="clearer"></div>
    </div>

  <div class="footer">
    &copy; Copyright 2018, holger krekel and pytest-dev team.
    Created using <a href="http://sphinx.pocoo.org/">Sphinx</a>.
  </div>
  

  </body>
</html>