pytest-runtime-xfail
pytest plugin, providing a runtime_xfail fixture, which is callable as runtime_xfail(), to allow runtime decisions to mark a test as xfail.
Installation
Install with pip:
pip install pytest-runtime-xfail
Usage
Include the fixture, then call it if you want to mark a test as xfail during runtime.
def test_something(runtime_xfail):
if (runtime_condition):
runtime_xfail()
# ... the rest of your test
Can also be used in a fixture, of course.
@pytest.fixture()
def foo(runtime_xfail):
if (runtime_condition):
runtime_xfail()
# ... the rest of your fixture
def test_something(foo):
# ... the rest of your test
Reason this plugin is needed
pytest allows you to mark tests as expected to fail, or xfail, in two ways.
-
@pytest.mark.xfail. This allows you to mark tests or test parametrizations asxfailduring test collection time.- pytest runs tests marked with
xfailjust like any other test. - If the test fails, it will result in
XFAIL. - If it passes,
XPASS. Unless you havexfail_strict=trueor@pytest.mark.xfail(strict=True), in which case, passing xfail-marked tests will result inFAIL.- This is useful to be alerted when an expected failing test starts to pass.
- pytest runs tests marked with
-
pytest.xfail(). If you need information only known at runtime to decide ifxfailis appropriate, you can callpytest.xfail()during a test or fixture.- pytest runs the test as normal UNTIL
pytest.xfail()is called. - When
pytest.xfail()is called, the test execution stops and the test results inXFAIL. - The rest of the test is not run.
- There is no way to get
XPASSfrompytest.xfail(). xfail_stricthas no effect.
- pytest runs the test as normal UNTIL
There are times when we want a combination of these behaviors.
- We don't know until runtime if we should mark a test as
xfail. - We want the test run.
- We want the possibility of both
XFAILandXPASSresults. - We want to be able to use
xfail_strict=trueto alert us when the test starts passing.
This plugin fills that gap.
Alternatives
You can get around the same limitation yourself by adding the marker through the requests object:
def test_something(request):
if (runtime_condition):
request.node.add_marker(pytest.mark.xfail(reason='some reason'))
# ... rest of test
That's basically what this plugin does, just in a fixture.
Example found in example/test_xfail.py
"""
Run this with
* pytest -v
* pytest -v -o xfail_strict=true
"""
import pytest
@pytest.mark.xfail()
def test_marker_pass():
'Can be XPASS or FAIL (if xfail_strict)'
assert True
@pytest.mark.xfail()
def test_marker_fail():
'Will always be XFAIL'
assert False # this statememt will be run
def test_old_xfail_pass():
'Will always be XFAIL'
pytest.xfail()
assert True # this statememt will NOT be run
def test_old_xfail_fail():
'Will always be XFAIL'
pytest.xfail()
assert False # this statememt will NOT be run
def test_runtime_xfail_pass(runtime_xfail):
runtime_xfail()
assert True # this statement will be run
def test_runtime_xfail_fail(runtime_xfail):
runtime_xfail()
assert False # this statement will be run
def test_runtime_xfail_reason(runtime_xfail):
runtime_xfail(reason="for demo")
assert False # this statement will be run
Output:
(venv) $ pytest -v test_xfail.py
========================= test session starts ==========================
collected 7 items
test_xfail.py::test_marker_pass XPASS [ 14%]
test_xfail.py::test_marker_fail XFAIL [ 28%]
test_xfail.py::test_old_xfail_pass XFAIL [ 42%]
test_xfail.py::test_old_xfail_fail XFAIL [ 57%]
test_xfail.py::test_runtime_xfail_pass XPASS [ 71%]
test_xfail.py::test_runtime_xfail_fail XFAIL [ 85%]
test_xfail.py::test_runtime_xfail_reason XFAIL (for demo) [100%]
==================== 5 xfailed, 2 xpassed in 0.05s =====================
(venv) $ pytest -v test_xfail.py -o xfail_strict=true
========================= test session starts ==========================
collected 7 items
test_xfail.py::test_marker_pass FAILED [ 14%]
test_xfail.py::test_marker_fail XFAIL [ 28%]
test_xfail.py::test_old_xfail_pass XFAIL [ 42%]
test_xfail.py::test_old_xfail_fail XFAIL [ 57%]
test_xfail.py::test_runtime_xfail_pass FAILED [ 71%]
test_xfail.py::test_runtime_xfail_fail XFAIL [ 85%]
test_xfail.py::test_runtime_xfail_reason XFAIL (for demo) [100%]
===================== 2 failed, 5 xfailed in 0.04s =====================
Metadata
Release files for pytest-runtime-xfail 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pytest_runtime_xfail-1.1.1.tar.gz | 5.8 kB | Without provenance | Details for pytest_runtime_xfail-1.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pytest_runtime_xfail-1.1.1-py3-none-any.whl | Python 3 | none | any | Details for pytest_runtime_xfail-1.1.1-py3-none-any.whl |
Total release size: 10.5 kB
Release files / pytest_runtime_xfail-1.1.1.tar.gz
| Download URL | pytest_runtime_xfail-1.1.1.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
773c013dea99700c82e71333b966a20254491a255ced3c4c72bc7ce1c339cf1b
|
|
BLAKE2b-256 checksum How to use checksums |
dc12ffffc8aa869d6bd0b6219e63b7936e29fc97607e7c7cdb010886ef6f69a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / pytest_runtime_xfail-1.1.1-py3-none-any.whl
| Download URL | pytest_runtime_xfail-1.1.1-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1927a7505367668bbf0a85ceb9224167bc6335bf24bb2b78b40cca311c6aeb6a
|
|
BLAKE2b-256 checksum How to use checksums |
2e0bec56d9c87a653f00bcdcf73160e4ccda3e8dacdf4c91cbc21d116a0392f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for pytest-runtime-xfail 1.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.