Build tools: don't use the pytest.fixtures decorator anymore in class fixtures #3458
Conversation
This comment has been minimized.
This comment has been minimized.
|
Don't merge just yet, why did this not get triggered: https://codecov.io/gh/scikit-image/scikit-image/pull/3458/changes |
This seems related - https://docs.pytest.org/en/latest/nose.html?highlight=setUp#unsupported-idioms-known-issues . |
|
@soupault so because we subclassed |
stefanv
left a comment
There was a problem hiding this comment.
This looks OK to me. We could probably consider refactoring to remove the test suite classes, and then using the fixtures directly, but this works.
| mesh_surface_area, correct_mesh_orientation) | ||
| from skimage._shared import testing | ||
| from skimage._shared.testing import assert_array_equal | ||
| from skimage._shared._warnings import expected_warnings |
There was a problem hiding this comment.
Could you revert this commit, please? Otherwise, good-to-go.
fd373ab to
fc07227
Compare
…s as explained by a pytest warning RemovedInPytest4Warning: Fixture "setUp" called directly. Fixtures are not meant to be called directly, are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/latest/fixture.html for more information.
fc07227 to
c0c2c5d
Compare
|
@jni, this is the PR i mentioned that lets the tests pass. |
|
oh, thanks! |
|
Thanks @hmaarrfk, sorry I missed this the first time around! |
|
@sciunto do I look like Meeseeks? LOL @meeseeksdev backport to v0.14.x |
…orator anymore in class fixtures
|
:D :D :D |
…8-on-v0.14.x Backport PR #3458 on branch v0.14.x (TST: don't use the pytest.fixtures decorator anymore in class fixtures )
as explained by a pytest warning
If you can make sense of why this works, you are a hero. I can't, but it works.
For reviewers
later.
__init__.py.doc/release/release_dev.rst.@meeseeksdev backport to v0.14.x