@@ -261,7 +261,7 @@ pytest.mark.xfail
261261
262262Marks a test function as *expected to fail *.
263263
264- .. py :function :: pytest.mark.xfail(condition = False , * , reason = None , raises = None , run = True , strict = xfail_strict )
264+ .. py :function :: pytest.mark.xfail(condition = False , * , reason = None , raises = None , run = True , strict = strict_xfail )
265265
266266 :keyword Union[bool, str] condition:
267267 Condition for marking the test function as xfail (``True/False `` or a
@@ -286,7 +286,7 @@ Marks a test function as *expected to fail*.
286286 that are always failing and there should be a clear indication if they unexpectedly start to pass (for example
287287 a new release of a library fixes a known bug).
288288
289- Defaults to :confval: `xfail_strict `, which is ``False `` by default.
289+ Defaults to :confval: `strict_xfail `, which is ``False `` by default.
290290
291291
292292Custom marks
@@ -2070,7 +2070,7 @@ passed multiple times. The expected format is ``name=value``. For example::
20702070 "auto" can be used to explicitly use the global verbosity level.
20712071
20722072
2073- .. confval :: xfail_strict
2073+ .. confval :: strict_xfail
20742074
20752075 If set to ``True ``, tests marked with ``@pytest.mark.xfail `` that actually succeed will by default fail the
20762076 test suite.
@@ -2080,7 +2080,11 @@ passed multiple times. The expected format is ``name=value``. For example::
20802080 .. code-block :: ini
20812081
20822082 [pytest]
2083- xfail_strict = True
2083+ strict_xfail = True
2084+
2085+ .. versionchanged :: 9.0
2086+ Renamed from ``xfail_strict `` to ``strict_xfail ``.
2087+ ``xfail_strict `` is accepted as an alias for ``strict_xfail ``.
20842088
20852089.. confval :: strict_parametrization_ids
20862090
0 commit comments