Migrate to pytest #420
Merged
Migrate to pytest #420
Conversation
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
pp-mo
approved these changes
Apr 16, 2024
Member
pp-mo
left a comment
There was a problem hiding this comment.
Totally good with this !
Just one question : are the lockfiles re-resolved or manually edited ?
I can see they lose nose + gain a few new things, but no version change to existing packages. I guess that must be "ok", but possibly not optimal ?
Member
Author
Member
Author
|
Awesome, thanks guys! 🥳 |
Closed
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.
This pull-request migrates away from the home-brew
noserunner implementation topytest.Note that, the tests may be now run from the command line using
noxorpytest. However, when usingpytestfrom the CLI theirisenvironment variableOVERRIDE_TEST_DATA_REPOSITORYrequires to be also configured.I've not used the
pytest-xdistplugin, as I didn't deem it in scope ATM; the existing runtime of the tests is relatively short.In the future, we should look to use filterwarnings to control and manage the expected warnings raised during a test run.