CI: Use Pytest instead of Nose, update default build to Python 3.10#131
Merged
quaquel merged 2 commits intoquaquel:masterfrom May 18, 2022
Merged
CI: Use Pytest instead of Nose, update default build to Python 3.10#131quaquel merged 2 commits intoquaquel:masterfrom
quaquel merged 2 commits intoquaquel:masterfrom
Conversation
Owner
|
I agree on the connectors. Have been debating on how to do this for a while. You can mock everything, but that partly defeats the purpose. |
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I checked with nose2pytest if there were any test that needed to be rewritten, and that wasn't the case. After that migrating to Pytest was quite simple, just looking up the right equivalent CLI parameters.
This PR also updates the default build (with Ubuntu, macOS and Windows) to Python 3.10, since that now works.
At some point we should probably create a workflow to test the connectors, but that's something for another time.
Closes #128.