pytest-rerunfailures
pytest plugin to re-run tests to eliminate flaky failures
Description
.. contents:: pytest-rerunfailures ==================== .. START-SHORT-DESCRIPTION pytest-rerunfailures is a plugin for `pytest <https://pytest.org>`_ that re-runs tests to eliminate intermittent failures. .. END-SHORT-DESCRIPTION .. image:: https://img.shields.io/badge/license-MPL%202.0-blue.svg :target: https://github.com/pytest-dev/pytest-rerunfailures/blob/master/LICENSE :alt: License .. image:: https://img.shields.io/pypi/v/pytest-rerunfailures.svg :target: https://pypi.python.org/pypi/pytest-rerunfailures/ :alt: PyPI .. image:: https://github.com/pytest-dev/pytest-rerunfailures/workflows/Test/badge.svg :target: https://github.com/pytest-dev/pytest-rerunfailures/actions :alt: GitHub Actions .. image:: https://readthedocs.org/projects/pytest-rerunfailures/badge/?version=latest :target: https://pytest-rerunfailures.readthedocs.io/latest/?badge=latest :alt: Documentation Status .. START-INSTALLATION Requirements ------------ You will need the following prerequisites in order to use pytest-rerunfailures: - Python 3.10+ or PyPy3 - pytest 8.0 or newer This plugin can recover from a hard crash with the following optional prerequisites: - pytest-xdist 2.3.0 or newer This package is currently tested against the last 5 minor pytest releases. In case you work with an older version of pytest you should consider updating or use one of the earlier versions of this package. Installation ------------ To install pytest-rerunfailures: .. code-block:: bash $ pip install pytest-rerunfailures .. END-INSTALLATION Recover from hard crashes ------------------------- If one or more tests trigger a hard crash (for example: segfault), this plugin will ordinarily be unable to rerun the test. However, if a compatible version of pytest-xdist is installed, and the tests are run within pytest-xdist using the ``-n`` flag, this plugin will be able to rerun crashed tests, assuming the workers and controller are on the same LAN (this assumption is valid for almost all cases because most of the time the workers and controller are on the same computer). If this assumption is not the case, then this functionality may not operate. Re-run all failures ------------------- To re-run all test failures, use the ``--reruns`` command line option with the maximum number of times you'd like the tests to run: .. code-block:: bash $ pytest --reruns 5 Failed fixture or setup_class will also be re-executed. To add a delay time between re-runs use the ``--reruns-delay`` command line option with the amount of seconds that you would like wait before the next test re-run is launched: .. code-block:: bash $ pytest --reruns 5 --reruns-delay 1 Re-run all failures matching certain expressions ------------------------------------------------ To re-run only those failures that match a certain list of expressions, use the ``--only-rerun`` flag and pass it a regular expression. For example, the following would only rerun those errors that match ``AssertionError``: .. code-block:: bash $ pytest --reruns 5 --only-rerun AssertionError Passing the flag multiple times accumulates the arguments, so the following would only rerun those errors that match ``AssertionError`` or ``ValueError``: .. code-block:: bash $ pytest --reruns 5 --only-rerun AssertionError --only-rerun ValueError Re-run all failures other than matching certain expressions ----------------------------------------------------------- To re-run only those failures that do not match a certain list of expressions, use the ``--rerun-except`` flag and pass it a regular expression. For example, the following would only rerun errors other than that match ``AssertionError``: .. code-block:: bash $ pytest --reruns 5 --rerun-except AssertionError Passing the flag multiple times accumulates the arguments, so the following would only rerun those errors that does not match with ``AssertionError`` or ``OSError``: .. code-block:: bash $ pytest --reruns 5 --rerun-except AssertionError --rerun-except OSError Re-run individual failures -------------------------- To mark individual tests as flaky, and have them automatically re-run when they fail, add the ``flaky`` mark with the maximum number of times you'd like the test to run: .. code-block:: python @pytest.mark.flaky(reruns=5) def test_example(): import random assert random.choice([True, False]) Note that when teardown fails, two reports are generated for the case, one for the test case and the other for the teardown error. You can also specify the re-run delay time in the marker: .. code-block:: python @pytest.mark.flaky(reruns=5, reruns_delay=2) def test_example(): import random assert random.choice([True, False]) You can also specify an optional ``condition`` in the re-run marker: .. code-block:: python @pytest.mark.flaky(reruns=5, condition=sys.platform.startswith("win32")) def test_example(): import random assert random.ch
Release History
| Version | Changes | Urgency | Date |
|---|---|---|---|
| 16.1 | Imported from PyPI (16.1) | Low | 4/21/2026 |
| 16.0.1 | Tag 16.0.1 | Low | 9/2/2025 |
| 16.0 | Tag 16.0 | Low | 8/29/2025 |
| 15.1 | Tag 15.1 | Low | 5/8/2025 |
| 15.0 | Tag 15.0 | Low | 11/20/2024 |
| 14.0 | Tag 14.0 | Low | 3/13/2024 |
| 13.0 | Tag 13.0 | Low | 11/22/2023 |
| 12.0 | Tag 12.0 | Low | 7/5/2023 |
| 11.1.2 | Tag 11.1.2 | Low | 3/9/2023 |
| 11.1.1 | Tag 11.1.1 | Low | 2/17/2023 |
| 11.1 | Tag 11.1 | Low | 2/9/2023 |
| 11.0 | Tag 11.0 | Low | 1/12/2023 |
| 10.3 | Tag 10.3 | Low | 11/22/2022 |
| 10.2 | Tag 10.2 | Low | 9/17/2021 |
| 10.1 | Tag 10.1 | Low | 7/2/2021 |
| 10.0 | Tag 10.0 | Low | 5/26/2021 |
| 9.1.1 | Tag 9.1.1 | Low | 9/29/2020 |
| 9.1 | Tag 9.1 | Low | 8/26/2020 |
| 9.0 | Tag 9.0 | Low | 3/18/2020 |
| 8.0 | Tag 8.0 | Low | 11/18/2019 |
