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
I expect the current design was chosen for a reason, but I don't quite understand. Please help me understand :)
Why is enabling pytest-mpl image comparison is not the default? Ie why is it only enabled when explicitly setting the --mpl flag?
Why are pytest-mpl tests logged as passed when the image comparison is in fact skipped?
I expect that just typing pytest is enough. I expect that this will run all tests, except some that are skipped because they can't be run, or don't make any sense to run, in the given context.
The current design carries a risk of the user incorrectly believing that all tests passed, when he in fact only executed a subset of the tests.
The text was updated successfully, but these errors were encountered:
I consider using pytest-mpl as a plugin in a few tests on an open source project. But if I do that, then I will have to change both the docs and the github actions, to run pytest with the --mpl argument. Right? I don't exactly love that. But there might be a good reason, and if so, please share it with me :)
I expect the current design was chosen for a reason, but I don't quite understand. Please help me understand :)
Why is enabling pytest-mpl image comparison is not the default? Ie why is it only enabled when explicitly setting the
--mpl flag
?Why are pytest-mpl tests logged as passed when the image comparison is in fact skipped?
I expect that just typing
pytest
is enough. I expect that this will run all tests, except some that are skipped because they can't be run, or don't make any sense to run, in the given context.The current design carries a risk of the user incorrectly believing that all tests passed, when he in fact only executed a subset of the tests.
The text was updated successfully, but these errors were encountered: