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
TST: investigate and fix xfail_xp_backend with test class inheritance #452
I would like to investigate this, starting with a regression test rather than assuming inheritance itself is the cause.
On current main (2aeb675), I ran a minimal parent/child test-class case using the existing library and xp fixtures: a class-level xfail_xp_backend(Backend.NUMPY) correctly applies to inherited plain and parametrized methods (3 parent cases passed, 3 child cases xfailed; pytest 9.1.1, Python 3.12). This does not reproduce the original Sparse/argpartition case, and I have not tested that backend yet.
Would a useful next step be to recreate the original TestArgpartition inheritance pattern with Sparse and check whether the explicit test-method wrappers are still necessary? If it is specific to an older pytest/backend combination, is there a version you would like covered?
Activity
Cyril-36 commentedon Oct 22, 2026
I would like to investigate this, starting with a regression test rather than assuming inheritance itself is the cause.
On current main (2aeb675), I ran a minimal parent/child test-class case using the existing library and xp fixtures: a class-level xfail_xp_backend(Backend.NUMPY) correctly applies to inherited plain and parametrized methods (3 parent cases passed, 3 child cases xfailed; pytest 9.1.1, Python 3.12). This does not reproduce the original Sparse/argpartition case, and I have not tested that backend yet.
Would a useful next step be to recreate the original TestArgpartition inheritance pattern with Sparse and check whether the explicit test-method wrappers are still necessary? If it is specific to an older pytest/backend combination, is there a version you would like covered?