[nonatomiclabs]

Context

Pytest’s xfail marker identifies tests that are expected to fail, for instance because of a known bug. Pytest supports a "strict" xfail mode through @pytest.mark.xfail(strict=True) or the xfail_strict configuration option. In this mode, an unexpectedly passing test (XPASS) is treated as a failure. This is useful to ensure that xfail markers are removed when a bug is fixed.

Currently, allure-pytest reports these tests as Failed, but provides no failure details, leaving out both the strict XPASS indication and the xfail reason.

This PR populates the failure details with pytest’s [XPASS(strict)] message, including the reason when present. This follows the approach already used in allure-pytest-bdd (see the code and the "Xfail support" section in #845).

Regression tests cover explicit and configured strict mode, with and without a reason, and verify that existing XFAIL and ordinary failure reporting remain unchanged.

Checklist

• Sign Allure CLA
• Provide unit tests

Verification

• The new unit tests pass:

  $ PYTEST_DISABLE_PLUGIN_AUTOLOAD=true python3 -m pytest tests/allure_pytest/acceptance/status/xfail_call_status_test.py -q
  ...........                                                                                                                                                                                                                             [100%]
  11 passed in 0.28s
  

• I created a small project and we can see that the new behavior works as intended:

  • before:
    

  • after: