-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TST: Update for pytest 7 #83
Conversation
Remove 36 PytestRemovedIn8Warning and PytestReturnNotNoneWarning warnings.
Python 3.5 and 3.6 are no longer supported by |
@StefRe thanks for the update! I can take a look at this soon |
@StefRe -- anything else you think should go in here? |
Looking at the CI test output, there are still 16 warnings. I think they are all due to missing pytest plugins:
|
I only now saw that all the tests are run twice: first in Basic unit tests and then in Image comparison tests. The latter installs |
I'm sure I had a reason at the time. Maybe the img tests were flaky and allowed to fail? In any case, I can't think of a good reason now. |
Oh also the img tests are only run on the "latest" version of python, not e.g., 3.8, 3.9, etc. Maybe that should change |
My point was that Basic unit tests and Image comparison tests do the same thing, i.e. all tests are run twice (even more so now that the python version matrices are identical). So if we want to run the image comparison tests separately then maybe it's clearer to add |
Yeah I agree. Since all python versions in the img-comp matrix are passing, I'd be inclined to scrap the "vanilla" tests altogether. |
Remove 36 PytestRemovedIn8Warning and PytestReturnNotNoneWarning warnings.