You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ExceptionGroup ergonomics in pytest.param(..., marks=xfail(raises=...))Â #12504
If your test is async though, you'll actually raise an ExceptionGroup(..., [IndexError]) (maybe with even more nesting), so the tests will still fail. Can we make this more ergonomic? What would a parametrize-aware RaisesGroup-like thing look like?
Actually, I don't see why this is about pytest.param at all. If pytest.mark.xfail(raises=...) got support for RaisesGroup (or equivalent) it should Just Work âĒïļ
#11671 has fallen behind the trio implementation, and is stalled by people wanting to have opinions on the interface design, otherwise I'd resolve this issue in it right away.
Activity
jakkdl commentedon Jul 16, 2024
I might be seeing nails everywhere, but I would do
and afaict the only code doing the matching is
pytest/src/_pytest/skipping.py
Lines 280 to 281 in d9a2fd0
where it would be straightforward to add
This of course depends on #11671 (or a version that fully implements trio.RaisesGroup functionality).
jakkdl commentedon Sep 17, 2024
Actually, I don't see why this is about
pytest.paramat all. Ifpytest.mark.xfail(raises=...)got support forRaisesGroup(or equivalent) it should Just Work âĒïļ#11671 has fallen behind the trio implementation, and is stalled by people wanting to have opinions on the interface design, otherwise I'd resolve this issue in it right away.
jakkdl commentedon Mar 13, 2025
Oh this also got fixed in #13192
chore(deps): update dependency pytest to v9 (#305)