Support test functions that are located inside classes about python-pytest-steps HOT 6 CLOSED

Fixed in 1.7.0 (to be released in a few minutes)

from python-pytest-steps.

It would be non-trivial to fix this: indeed the way we currently generate the wrappers around test functions is done with a hacked version of decorator to add arguments in the signature, and the only way I found as of today is to prepend the new arguments at the beginning of the positional arguments in the new signature.

When a function is located inside a class, its first argument is 'self' or 'cls', and should remain the first argument, even after our wrapping.

We could however inspect the test functions and detect that it is an instance, class or static method, so that we handle the case specifically.

Let's wait for users actually requiring it :)

from python-pytest-steps.

uhm...here i am :D

from python-pytest-steps.

Thanks for caring! As of today as I wrote above, this would require a major non-trivial modification.

A workaround is to use the "new" pytest style (i.e. no classes, just plain old functions in separate modules). But I understand that in large projects this might not be satisfying.

I would gladly accept contributions on the topic if anyone feels ready to dig into dynamic code compilation.

from python-pytest-steps.

Looks like a MUSTHAVE feature

from python-pytest-steps.

It seems that this is doable quite easily with current status of the code (now that I rely on makefun do manipulate the signatures). I'll have a look.

from python-pytest-steps.