Open radekwlsk opened 3 years ago
Hey! Can you show minimal example of broken test?
Thanks for opening the issue!
The problem comes from this code change: https://github.com/FactoryBoy/factory_boy/pull/828/files#diff-92a7290251f0a9a1c6f4309e8a63df0920e00a52cbf1257aa1ee62bbc11da044L497
The problem doens't come frompytest-lazy-fixture
but from pytest-factoryboy
, see this PR for failing tests https://github.com/pytest-dev/pytest-factoryboy/pull/125
Update: It looks like it comes from pytest-lazy-fixture because the plugin is calling the _fillfixtures method/fixture first. So it is triggering the behaviour which would happen else a bit later anyway
I think @TvoroG you can close this issue (and if you want help to fix the issue on the pytest-factoryboy side)
After updating factoryboy to
3.2.0
my tests usinglazy_fixture
with fixtures that useTrait
(in result usingMaybe
) raiseAttributeError: 'Maybe' object has no attribute 'call'
.Attached is a full traceback from failed test case.
Seems like it could be a problem in
pytest_factoryboy
itself but I've seen it raised only for tests usinglazy_fixture
.