Sylvain Marié

Thanks @jenstroeger ! I am curious to see the thoughts of the community of users here

Thanks a lot for reporting @jayqi ! For now inded the workaround is to use `pytest

Thanks @mroeschke for your feedback ! Not sure when this can get implemented but it will be the next mod to implement for sure.

Indeed I am able to reproduce, thanks @jgersti for reporting ! The issue is due to the fact that our own version of `MetaFunc.parametrize` is not patched onto the `metafunc`...

Issue opened: https://github.com/pytest-dev/pluggy/issues/441 Until the fix is available, we can mark the test as expected to fail. EDIT : I commented the whole `tests/pytest_extension/issues/test_issue_269.py` test file, let's uncomment it when...

Thanks @ImplyingICheck for reporting this issue, and very sorry for the long delay in answering ! Indeed, the documentation is probably a bit light on this, would you like to...

Thanks @ImplyingICheck for your proposal and first tests ! The changes seem limited in scope so I would be happy to consider this feature for inclusion. Still, that would require...

Good catch @lucapton ! Looking at the source code, this is...normal :( This is because my current code in `_unpack_fixture` only reuses the original fixture's scope if the provided source...

Very clear @lucapton , thanks! I'll see what I can do one of these days

Nice proposal @tokarenko ! It reminds me of #281 but seems more straightforward. Would you like to propose a PR, similar to the `unpack_fixture` function ? https://smarie.github.io/python-pytest-cases/api_reference/#unpack_fixture Note that the...