Add pytest-asyncio as a dev requirement so we don't skip so many tests in CI #358
Conversation
This file contains 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
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.
Currently, all
async deftest functions are being skipped: see the CI runs in https://github.com/python/blurb_it/actions/runs/6453980405/job/17518591042 for an example. Withpytest-asyncioinstalled, these are no longer skipped!We also need to add
asyncio_mode=autoto the pytest config in order for this plugin to do its job, which necessitated adding a pytest config. So I did that as well, and enhanced the coveragepy config while I was about it.