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
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
|
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="generator" content="Docutils 0.17.1: http://docutils.sourceforge.net/" />
<title>Resolving test suite problems — Gentoo Python Guide documentation</title>
<link rel="stylesheet" type="text/css" href="_static/pygments.css" />
<link rel="stylesheet" type="text/css" href="_static/alabaster.css" />
<script data-url_root="./" id="documentation_options" src="_static/documentation_options.js"></script>
<script src="_static/jquery.js"></script>
<script src="_static/underscore.js"></script>
<script src="_static/doctools.js"></script>
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="pytest recipes" href="pytest.html" />
<link rel="prev" title="Advanced dependencies" href="depend.html" />
<link rel="stylesheet" href="_static/custom.css" type="text/css" />
<meta name="viewport" content="width=device-width, initial-scale=0.9, maximum-scale=0.9" />
</head><body>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<section id="resolving-test-suite-problems">
<h1>Resolving test suite problems<a class="headerlink" href="#resolving-test-suite-problems" title="Permalink to this headline">¶</a></h1>
<section id="choosing-the-correct-test-runner">
<h2>Choosing the correct test runner<a class="headerlink" href="#choosing-the-correct-test-runner" title="Permalink to this headline">¶</a></h2>
<p>There are a few modules used to run tests in Python packages. The most
common include the built-in <a class="reference external" href="https://docs.python.org/3/library/unittest.html">unittest</a> module, <a class="reference external" href="https://docs.pytest.org/en/latest/">pytest</a> and <a class="reference external" href="https://github.com/nose-devs/nose">nose</a>. There
are also some rarely used test tools and domain-specific solutions,
e.g. <a class="reference external" href="https://www.djangoproject.com/">django</a> has its own test runner. This section will help you
determining which test runner to use and depend on.</p>
<p>Firstly, it is a good idea to look at test sources. Explicit imports
clearly indicate that a particular test runner needs to be installed,
and most likely used. For example, if at least one test file has
<code class="docutils literal notranslate"><span class="pre">import</span> <span class="pre">pytest</span></code>, pytest is the obvious choice. If it has <code class="docutils literal notranslate"><span class="pre">import</span>
<span class="pre">nose</span></code>, same goes for nosetests.</p>
<p>In some rare cases the tests may use multiple test packages
simultaneously. In this case, you need to choose one of the test
runners (see other suggestions) but depend on all of them.</p>
<p>Secondly, some test suites are relying on <em>implicit</em> features of a test
runner. For example, pytest and nose have less strict naming
and structural requirements for test cases. In some cases, unittest
runner will simply be unable to find all tests.</p>
<p>Thirdly, there are cases when a particular feature of a test runner
is desired even if it is not strictly necessary to run tests. This
is particularly the case with pytest’s output capture that can make
test output much more readable with particularly verbose packages.</p>
<p>Upstream documentation, tox configuration, CI pipelines can provide tips
on the test runner to be used. However, you should establish whether
this information is wholly correct and up-to-date, and whether
the particular test tool is really desirable.</p>
<p>If the test suite requires no particular runner (i.e. works with
built-in unittest module), using it is preferable to avoid unnecessary
dependencies. However, you need to make sure that it finds all tests
correctly (i.e. runs no less tests than the alternative) and that it
does not spew too much irrelevant output.</p>
<p>If both pytest and nose seem equally good, the former is recommended
as the latter has ceased development and requires downstream patching.
If you have some free time, convincing upstream to switch from nose
to pytest is a worthwhile goal.</p>
</section>
<section id="missing-test-files-in-pypi-packages">
<h2>Missing test files in PyPI packages<a class="headerlink" href="#missing-test-files-in-pypi-packages" title="Permalink to this headline">¶</a></h2>
<p>One of the more common test-related problems is that PyPI packages
(generated via <code class="docutils literal notranslate"><span class="pre">setup.py</span> <span class="pre">sdist</span></code>) often miss some or all test files.
The latter results in no tests being run, the former in test failures
or errors.</p>
<p>The simplest solution is to use a VCS snapshot instead of the PyPI
tarball:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># pypi tarballs are missing test data</span>
<span class="c1">#SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"</span>
<span class="nv">SRC_URI</span><span class="o">=</span><span class="s2">"https://github.com/</span><span class="si">${</span><span class="nv">PN</span><span class="si">}</span><span class="s2">/</span><span class="si">${</span><span class="nv">PN</span><span class="si">}</span><span class="s2">/archive/</span><span class="si">${</span><span class="nv">PV</span><span class="si">}</span><span class="s2">.tar.gz -> </span><span class="si">${</span><span class="nv">P</span><span class="si">}</span><span class="s2">.gh.tar.gz"</span>
</pre></div>
</div>
</section>
<section id="checklist-for-dealing-with-test-failures">
<h2>Checklist for dealing with test failures<a class="headerlink" href="#checklist-for-dealing-with-test-failures" title="Permalink to this headline">¶</a></h2>
<p>If you see some test failures but do not have a guess as to why they
would be happening, try the following for a start:</p>
<ol class="arabic simple">
<li><p>Check upstream CI (if any). That’s a quick way of verifying that
there is no known breakage at the relevant tag.</p></li>
<li><p>Try running tests as your regular user, the way upstream suggests
(e.g. via <code class="docutils literal notranslate"><span class="pre">tox</span></code>). Try using a git checkout at the specific tag.
This is the basic way of determining whether the package is actually
broken or if it is something on our end.</p></li>
<li><p>If the tests fail at the specified tag, try upstream master branch.
Maybe there was a fix committed.</p></li>
</ol>
<p>If it seems that the issue is on our end, try the following and see
if it causes the subset of failing tests to change:</p>
<ol class="arabic">
<li><p>Make sure that the test runner is started via <code class="docutils literal notranslate"><span class="pre">${EPYTHON}</span></code>
(the eclass-provided <code class="docutils literal notranslate"><span class="pre">epytest</span></code> and <code class="docutils literal notranslate"><span class="pre">eunittest</span></code> wrappers do that).
Calling system executables directly (either Python via absolute path
or system-installed tools that use absolute path in their shebangs)
may cause just-built modules not to be imported correctly.</p></li>
<li><p>Try running the test suite from another directory. If you’re seeing
failures to load compiled extensions, Python may be wrongly importing
modules from the current directory instead of the build/install tree.
Some test suite also depend on paths relative to where upstream run
tests.</p></li>
<li><p>Switch to PEP 517 mode, add <code class="docutils literal notranslate"><span class="pre">distutils_install_for_testing</span></code>
to the test sub-phase or <code class="docutils literal notranslate"><span class="pre">--install</span></code> to <code class="docutils literal notranslate"><span class="pre">distutils_enable_tests</span></code>
call. This resolves majority of problems with the test suite
requiring the package to be installed prior to testing.</p></li>
<li><p>Actually install the package to the system (with tests disabled).
This can confirm cases of package for whom the above function
does not work. In the worst case, you can set a test self-dependency
to force users to install the package before testing:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>test? <span class="o">(</span> ~dev-python/myself-<span class="si">${</span><span class="nv">PV</span><span class="si">}</span> <span class="o">)</span>
</pre></div>
</div>
</li>
<li><p>Try testing a different Python implementation. If a subset of tests
is failing with Python 3.6, see if it still happens with 3.7 or 3.8.
If 3.8 is passing but 3.9 is not, it’s most likely some
incompatibility upstream did not account for.</p></li>
<li><p>Run tests with <code class="docutils literal notranslate"><span class="pre">FEATURES=-network-sandbox</span></code>. Sometimes lack
of Internet access causes non-obvious failures.</p></li>
<li><p>Try a different test runner. Sometimes the subtle differences
in how tests are executed can lead to test failures. But beware:
some test runners may not run the full set of tests, so verify
that you have actually fixed them and not just caused them to
be skipped.</p></li>
</ol>
</section>
<section id="skipping-problematic-tests">
<h2>Skipping problematic tests<a class="headerlink" href="#skipping-problematic-tests" title="Permalink to this headline">¶</a></h2>
<p>While generally it is preferable to fix tests, sometimes you will face
failures that cannot be easily resolved. This especially applies
to tests that are broken themselves rather than indicating real problems
with the software. However, in some cases you will even find yourself
ignoring minor test failures.</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>When possible, it is preferable to use pytest along with its
convenient ignore/deselect options to skip problematic tests.
Using pytest instead of unittest is usually possible.</p>
</div>
<p>Tests that are known to fail reliably can be marked as <em>expected
failures</em>. This has the advantage that the test in question will
continue being run and the test suite will report when it unexpectedly
starts passing again.</p>
<p>Expected failures are not supported by the standard Python unittest
module. It is supported e.g. by pytest.</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>sed -i -e <span class="se">\</span>
<span class="s2">"/def test_start_params_bug():/i@pytest.mark.xfail(reason='Known to fail on Gentoo')"</span> <span class="se">\</span>
statsmodels/tsa/tests/test_arima.py <span class="o">||</span> die
</pre></div>
</div>
<p>Tests that cause inconsistent results, trigger errors, consume
horrendous amounts of disk space or cause another kind of undesirable
mayhem can be <em>skipped</em> instead. Skipping means that they will not be
run at all.</p>
<p>There are multiple ways to skip a test. You can patch it to use a skip
decorator, possibly with a condition:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># broken on py2.7, upstream knows</span>
sed -i -e <span class="s1">'5a\</span>
<span class="s1">import sys'</span> <span class="se">\</span>
-e <span class="s1">'/test_null_bytes/i\</span>
<span class="s1">@pytest.mark.skipif(sys.hexversion < 0x03000000, reason="broken on py2")'</span> <span class="se">\</span>
test/server.py <span class="o">||</span> die
</pre></div>
</div>
<p>The easy way to skip a test unconditioanlly is to prefix its name with
an underscore:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># tests requiring specific locales</span>
sed -i -e <span class="s1">'s:test_babel_with_language_:_&:'</span> <span class="se">\</span>
tests/test_build_latex.py <span class="o">||</span> die
sed -i -e <span class="s1">'s:test_polyglossia_with_language_:_&:'</span> <span class="se">\</span>
tests/test_build_latex.py <span class="o">||</span> die
</pre></div>
</div>
<p>Finally, if all tests in a particular file are problematic, you can
simply remove that file. If all tests belonging to the package
are broken, you can use <code class="docutils literal notranslate"><span class="pre">RESTRICT=test</span></code> to disable testing altogether.</p>
</section>
<section id="tests-requiring-internet-access">
<h2>Tests requiring Internet access<a class="headerlink" href="#tests-requiring-internet-access" title="Permalink to this headline">¶</a></h2>
<p>One of more common causes of test failures are attempts to use Internet.
With Portage blocking network access by default, packages performing
tests against remote servers often fail.</p>
<p>Ideally, packages would use mocking or replay tests rather than using
real Internet services. Devmanual provides a detailed explanation <a class="reference external" href="https://devmanual.gentoo.org/ebuild-writing/functions/src_test/#tests-that-require-network-or-service-access">why
tests must not use Internet</a>.</p>
<p>Some packages provide explicit methods of disabling network-based tests.
For example, <code class="docutils literal notranslate"><span class="pre">dev-python/tox</span></code> provides a switch for that:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>python_test<span class="o">()</span> <span class="o">{</span>
distutils_install_for_testing
epytest --no-network
<span class="o">}</span>
</pre></div>
</div>
<p>There are packages that skip tests if they fail specifically due to
connection errors, or detect whether Internet is accessible. Ideally,
you should modify those packages to disable network tests
unconditionally. For example, <code class="docutils literal notranslate"><span class="pre">dev-python/pygit2</span></code> ebuild does this:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># unconditionally prevent it from using network</span>
sed -i -e <span class="s1">'/def no_network/a \</span>
<span class="s1"> return True'</span> test/utils.py <span class="o">||</span> die
</pre></div>
</div>
<p>In other cases, you will have to explicitly disable these tests.
In some cases, it will be reasonable to remove whole test files or even
restrict tests entirely.</p>
<p>If the package’s test suite relies on Internet access entirely and there
is no point in running even a subset of tests, please implement running
tests and combine test restriction with <code class="docutils literal notranslate"><span class="pre">PROPERTIES=test_network</span></code>
to allow interested users to run tests when possible:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># users can use ALLOW_TEST=network to override this</span>
<span class="nv">PROPERTIES</span><span class="o">=</span><span class="s2">"test_network"</span>
<span class="nv">RESTRICT</span><span class="o">=</span><span class="s2">"test"</span>
distutils_enable_tests pytest
</pre></div>
</div>
</section>
<section id="tests-aborting-due-to-assertions">
<h2>Tests aborting (due to assertions)<a class="headerlink" href="#tests-aborting-due-to-assertions" title="Permalink to this headline">¶</a></h2>
<p>There are cases of package’s tests terminating with an unclear error
message and backtrace similar to the following:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="o">=============================</span> <span class="nb">test</span> session <span class="nv">starts</span> <span class="o">==============================</span>
platform linux -- Python <span class="m">3</span>.7.8, pytest-6.0.1, py-1.9.0, pluggy-0.13.1 -- /usr/bin/python3.7
cachedir: .pytest_cache
rootdir: /var/tmp/portage/dev-python/sabyenc-4.0.2/work/sabyenc-4.0.2, configfile: pytest.ini
collecting ... collected <span class="m">24</span> items
<span class="o">[</span>...<span class="o">]</span>
tests/test_decoder.py::test_crc_pickles PASSED <span class="o">[</span> <span class="m">54</span>%<span class="o">]</span>
tests/test_decoder.py::test_empty_size_pickles Fatal Python error: Aborted
Current thread 0x00007f748bc47740 <span class="o">(</span>most recent call first<span class="o">)</span>:
File <span class="s2">"/var/tmp/portage/dev-python/sabyenc-4.0.2/work/sabyenc-4.0.2/tests/testsupport.py"</span>, line <span class="m">74</span> <span class="k">in</span> sabyenc3_wrapper
File <span class="s2">"/var/tmp/portage/dev-python/sabyenc-4.0.2/work/sabyenc-4.0.2/tests/test_decoder.py"</span>, line <span class="m">119</span> <span class="k">in</span> test_empty_size_pickles
File <span class="s2">"/usr/lib/python3.7/site-packages/_pytest/python.py"</span>, line <span class="m">180</span> <span class="k">in</span> pytest_pyfunc_call
File <span class="s2">"/usr/lib/python3.7/site-packages/pluggy/callers.py"</span>, line <span class="m">187</span> <span class="k">in</span> _multicall
<span class="o">[</span>...<span class="o">]</span>
File <span class="s2">"/usr/lib/python-exec/python3.7/pytest"</span>, line <span class="m">11</span> <span class="k">in</span> <module>
/var/tmp/portage/dev-python/sabyenc-4.0.2/temp/environment: line <span class="m">2934</span>: <span class="m">66</span> Aborted <span class="o">(</span>core dumped<span class="o">)</span> pytest -vv
</pre></div>
</div>
<p>This usually indicates that the C code of some Python extension failed
an assertion. Since pytest does not print captured output when exiting
due to a signal, you need to disable output capture (using <code class="docutils literal notranslate"><span class="pre">-s</span></code>)
to get a more useful error, e.g.:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>$ python3.7 -m pytest -s
=============================================================== test session starts ===============================================================
platform linux -- Python 3.7.8, pytest-6.0.1, py-1.9.0, pluggy-0.13.1
rootdir: /tmp/sabyenc, configfile: pytest.ini
plugins: asyncio-0.14.0, forked-1.3.0, xdist-1.34.0, hypothesis-5.23.9, mock-3.2.0, flaky-3.7.0, timeout-1.4.2, freezegun-0.4.2
collected 25 items
tests/test_decoder.py .............python3.7: src/sabyenc3.c:596: decode_usenet_chunks: Assertion `PyByteArray_Check(PyList_GetItem(Py_input_list, lp))' failed.
Fatal Python error: Aborted
Current thread 0x00007fb5db746740 (most recent call first):
File "/tmp/sabyenc/tests/testsupport.py", line 73 in sabyenc3_wrapper
File "/tmp/sabyenc/tests/test_decoder.py", line 117 in test_empty_size_pickles
File "/usr/lib/python3.7/site-packages/_pytest/python.py", line 180 in pytest_pyfunc_call
File "/usr/lib/python3.7/site-packages/pluggy/callers.py", line 187 in _multicall
File "/usr/lib/python3.7/site-packages/pluggy/manager.py", line 87 in <lambda>
[...]
File "/usr/lib/python3.7/site-packages/pytest/__main__.py", line 7 in <module>
File "/usr/lib/python3.7/runpy.py", line 85 in _run_code
File "/usr/lib/python3.7/runpy.py", line 193 in _run_module_as_main
Aborted (core dumped)
</pre></div>
</div>
<p>Now the message clearly indicates the failed assertion.</p>
<p>It is also common that upstream is initially unable to reproduce
the bug. This is because Ubuntu and many other common distributions
build Python with <code class="docutils literal notranslate"><span class="pre">-DNDEBUG</span></code> and the flag leaks to extension builds.
As a result, all assertions are stripped at build time. Upstream
can work around that by explicitly setting <code class="docutils literal notranslate"><span class="pre">CFLAGS</span></code> for the build,
e.g.:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>$ <span class="nv">CFLAGS</span><span class="o">=</span><span class="s1">'-O0 -g'</span> python setup.py build build_ext -i
$ pytest -s
</pre></div>
</div>
</section>
<section id="installing-extra-dependencies-in-test-environment-e-g-example-plugins">
<h2>Installing extra dependencies in test environment (e.g. example plugins)<a class="headerlink" href="#installing-extra-dependencies-in-test-environment-e-g-example-plugins" title="Permalink to this headline">¶</a></h2>
<p>Rarely, the test suite expects some package being installed that
does not fit being packaged and installed system-wide. For example,
isort’s tests use a few example plugins that are not useful to end
users, or pip’s test suite still requires old virtualenv that collides
with the modern versions. These problems can be resolved by installing
the packages locally within the ebuild.</p>
<p>To do this, just use <code class="docutils literal notranslate"><span class="pre">distutils_install_for_testing</span></code> in every package
that you need to install. For example:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>python_test<span class="o">()</span> <span class="o">{</span>
<span class="c1"># the main package</span>
distutils_install_for_testing
<span class="c1"># additional plugins</span>
<span class="nb">local</span> p
<span class="k">for</span> p <span class="k">in</span> example*/<span class="p">;</span> <span class="k">do</span>
<span class="nb">pushd</span> <span class="s2">"</span><span class="si">${</span><span class="nv">p</span><span class="si">}</span><span class="s2">"</span> >/dev/null <span class="o">||</span> die
distutils_install_for_testing
<span class="nb">popd</span> >/dev/null <span class="o">||</span> die
<span class="k">done</span>
epytest
<span class="o">}</span>
</pre></div>
</div>
<p>If the extra packages are not included in the main distribution tarball,
you will also need to fetch them, e.g.:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="nv">VENV_PV</span><span class="o">=</span><span class="m">16</span>.7.10
<span class="nv">SRC_URI</span><span class="o">+=</span><span class="s2">"</span>
<span class="s2"> test? (</span>
<span class="s2"> https://github.com/pypa/virtualenv/archive/</span><span class="si">${</span><span class="nv">VENV_PV</span><span class="si">}</span><span class="s2">.tar.gz</span>
<span class="s2"> -> virtualenv-</span><span class="si">${</span><span class="nv">VENV_PV</span><span class="si">}</span><span class="s2">.tar.gz</span>
<span class="s2"> )</span>
<span class="s2">"</span>
python_test<span class="o">()</span> <span class="o">{</span>
distutils_install_for_testing
<span class="nb">pushd</span> <span class="s2">"</span><span class="si">${</span><span class="nv">WORKDIR</span><span class="si">}</span><span class="s2">/virtualenv-</span><span class="si">${</span><span class="nv">VENV_PV</span><span class="si">}</span><span class="s2">"</span> >/dev/null <span class="o">||</span> die
distutils_install_for_testing
<span class="nb">popd</span> >/dev/null <span class="o">||</span> die
epytest
<span class="o">}</span>
</pre></div>
</div>
</section>
</section>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="main navigation">
<div class="sphinxsidebarwrapper">
<h1 class="logo"><a href="index.html">Gentoo Python Guide</a></h1>
<h3>Navigation</h3>
<p class="caption" role="heading"><span class="caption-text">Contents:</span></p>
<ul class="current">
<li class="toctree-l1"><a class="reference internal" href="preface.html">Preface</a></li>
<li class="toctree-l1"><a class="reference internal" href="interpreter.html">Python interpreters</a></li>
<li class="toctree-l1"><a class="reference internal" href="eclass.html">Choosing between Python eclasses</a></li>
<li class="toctree-l1"><a class="reference internal" href="basic.html">Common basics</a></li>
<li class="toctree-l1"><a class="reference internal" href="any.html">python-any-r1 — build-time dependency</a></li>
<li class="toctree-l1"><a class="reference internal" href="single.html">python-single-r1 — single-impl packages</a></li>
<li class="toctree-l1"><a class="reference internal" href="multi.html">python-r1 — multi-impl packages</a></li>
<li class="toctree-l1"><a class="reference internal" href="distutils.html">distutils-r1 — standard Python build systems</a></li>
<li class="toctree-l1"><a class="reference internal" href="distutils-legacy.html">distutils-r1 legacy concepts</a></li>
<li class="toctree-l1"><a class="reference internal" href="helper.html">Common helper functions</a></li>
<li class="toctree-l1"><a class="reference internal" href="depend.html">Advanced dependencies</a></li>
<li class="toctree-l1 current"><a class="current reference internal" href="#">Resolving test suite problems</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#choosing-the-correct-test-runner">Choosing the correct test runner</a></li>
<li class="toctree-l2"><a class="reference internal" href="#missing-test-files-in-pypi-packages">Missing test files in PyPI packages</a></li>
<li class="toctree-l2"><a class="reference internal" href="#checklist-for-dealing-with-test-failures">Checklist for dealing with test failures</a></li>
<li class="toctree-l2"><a class="reference internal" href="#skipping-problematic-tests">Skipping problematic tests</a></li>
<li class="toctree-l2"><a class="reference internal" href="#tests-requiring-internet-access">Tests requiring Internet access</a></li>
<li class="toctree-l2"><a class="reference internal" href="#tests-aborting-due-to-assertions">Tests aborting (due to assertions)</a></li>
<li class="toctree-l2"><a class="reference internal" href="#installing-extra-dependencies-in-test-environment-e-g-example-plugins">Installing extra dependencies in test environment (e.g. example plugins)</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="pytest.html">pytest recipes</a></li>
<li class="toctree-l1"><a class="reference internal" href="concept.html">Advanced concepts</a></li>
<li class="toctree-l1"><a class="reference internal" href="expert-multi.html">Expert python-r1 usage</a></li>
<li class="toctree-l1"><a class="reference internal" href="buildsys.html">Integration with build systems written in Python</a></li>
<li class="toctree-l1"><a class="reference internal" href="porting.html">Porting tips</a></li>
<li class="toctree-l1"><a class="reference internal" href="migration.html">Migration guides</a></li>
<li class="toctree-l1"><a class="reference internal" href="package-maintenance.html">Python package maintenance</a></li>
<li class="toctree-l1"><a class="reference internal" href="interpreter-maintenance.html">Maintenance of Python implementations</a></li>
</ul>
<div class="relations">
<h3>Related Topics</h3>
<ul>
<li><a href="index.html">Documentation overview</a><ul>
<li>Previous: <a href="depend.html" title="previous chapter">Advanced dependencies</a></li>
<li>Next: <a href="pytest.html" title="next chapter">pytest recipes</a></li>
</ul></li>
</ul>
</div>
<div id="searchbox" style="display: none" role="search">
<h3 id="searchlabel">Quick search</h3>
<div class="searchformwrapper">
<form class="search" action="search.html" method="get">
<input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
<input type="submit" value="Go" />
</form>
</div>
</div>
<script>$('#searchbox').show(0);</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="footer">
©2020, Michał Górny, license: CC BY 4.0.
|
Powered by <a href="http://sphinx-doc.org/">Sphinx 4.4.0</a>
& <a href="https://github.com/bitprophet/alabaster">Alabaster 0.7.12</a>
|
<a href="_sources/test.rst.txt"
rel="nofollow">Page source</a>
</div>
</body>
</html>
|
GitWeb