12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273 |
- Metadata-Version: 2.0
- Name: pytest-forked
- Version: 0.2
- Summary: run tests in isolated forked subprocesses
- Home-page: https://github.com/pytest-dev/pytest-forked
- Author: pytest-dev
- Author-email: pytest-dev@python.org
- License: MIT
- Platform: linux
- Platform: osx
- Classifier: Development Status :: 7 - Inactive
- Classifier: Framework :: Pytest
- Classifier: Intended Audience :: Developers
- Classifier: License :: OSI Approved :: MIT License
- Classifier: Operating System :: POSIX
- Classifier: Operating System :: MacOS :: MacOS X
- Classifier: Topic :: Software Development :: Testing
- Classifier: Topic :: Software Development :: Quality Assurance
- Classifier: Topic :: Utilities
- Classifier: Programming Language :: Python
- Classifier: Programming Language :: Python :: 2
- Classifier: Programming Language :: Python :: 3
- Requires-Dist: pytest (>=2.6.0)
- pytest-forked: run each test in a forked subprocess
- ====================================================
- .. warning::
- this is a extraction of the xdist --forked module,
- future maintenance beyond the bare minimum is not plannend until a new maintainer is found
- * ``--forked``: (not available on Windows) run each test in a forked
- subprocess to survive ``SEGFAULTS`` or otherwise dying processes
- Installation
- -----------------------
- Install the plugin with::
- pip install pytest-forked
- or use the package in develope/in-place mode with
- a checkout of the `pytest-forked repository`_ ::
- pip install -e .
- Usage examples
- ---------------------
- If you have tests involving C or C++ libraries you might have to deal
- with tests crashing the process. For this case you may use the boxing
- options::
- py.test --forked
- which will run each test in a subprocess and will report if a test
- crashed the process. You can also combine this option with
- running multiple processes via pytest-xdist to speed up the test run
- and use your CPU cores::
- py.test -n3 --forked
- this would run 3 testing subprocesses in parallel which each
- create new forked subprocesses for each test.
- .. _`pytest-forked repository`: https://github.com/pytest-dev/pytest-forked
|