Pytest Plugin for Distributed Testing and Loop-on-Failing Modes
The `pytest-xdist`_ plugin extends py.test with some unique
test execution modes:
* test run parallelization_: if you have multiple CPUs or hosts you can use
those for a combined test run. This allows to speed up
development or to use special resources of `remote machines`_.
* ``--boxed``: (not available on Windows) run each test in a boxed_
subprocess to survive ``SEGFAULTS`` or otherwise dying processes
* ``--looponfail``: run your tests repeatedly in a subprocess. After each run
py.test waits until a file in your project changes and then re-runs
the previously failing tests. This is repeated until all tests pass
after which again a full run is performed.
* `Multi-Platform`_ coverage: you can specify different Python interpreters
or different platforms and run tests in parallel on all of them.
Before running tests remotely, ``py.test`` efficiently "rsyncs" your
program source code to the remote place. All test results
are reported back and displayed to your local terminal.
You may specify different Python versions and interpreters.
- Developed at devel:languages:python:pytest
- Sources inherited from project openSUSE:Factory
-
9
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Backports:SLE-15-SP4:FactoryCandidates/python-pytest-xdist && cd $_ - Create Badge
Source Files
| Filename | Size | Changed |
|---|---|---|
| pytest-xdist-3.3.1.tar.gz | 0000077751 75.9 KB | |
| python-pytest-xdist.changes | 0000021365 20.9 KB | |
| python-pytest-xdist.spec | 0000003161 3.09 KB |
Revision 23 (latest revision is 25)
Dominique Leuenberger (dimstar_suse)
accepted
request 1088464
from
Dirk Mueller (dirkmueller)
(revision 23)
- update to 3.3.1:
* Avoid remote calls during startup as execnet by default does
not ensure remote affinity with the main thread and might
accidentally schedule the pytest worker into a non-main
thread, which breaks numerous frameworks, for example
``asyncio``, ``anyio``, ``PyQt/PySide``, etc.
A more safe correction will require thread affinity in
``execnet``
Comments 0