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
-
10
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:ARM:Factory:Contrib:ILP32/python-pytest-xdist && cd $_
- Create Badge
Source Files
Filename | Size | Changed |
---|---|---|
pytest-xdist-3.5.0.tar.gz | 0000078977 77.1 KB | |
python-pytest-xdist.changes | 0000022084 21.6 KB | |
python-pytest-xdist.spec | 0000003138 3.06 KB |
Revision 25 (latest revision is 26)
- update to 3.5.0: * ``--dist=loadscope`` now sorts scopes by number of tests to assign largest scopes early -- in many cases this should improve overall test session running time, as there is less chance of a large scope being left to be processed near the end of the session, leaving other workers idle. not ensure remote affinity with the main thread and might * Internal errors in workers are now propagated to the master node. * New ``pytest_xdist_auto_num_workers`` hook can be implemented by plugins or ``conftest.py`` files to control the number of workers when * ``psutil`` has proven to make ``pytest-xdist`` installation in certain platforms and containers problematic, so to use it for automatic number * Drop backward-compatibility "slave" aliases related to worker nodes. We deliberately moved away from this terminology years ago, and it seems like the right time to finish * New functions ``xdist.is_xdist_worker``, ``xdist.is_xdist_master``, ``xdist.get_xdist_worker_id``, pytest_report_from_serializable hooks from pytest 4.4 - new ``worker_id`` fixture, returns the id of the worker in a test or - Update to 1.10
Comments 0