Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Improve async code coverage #344

Open
viceroypenguin opened this issue Apr 21, 2023 · 0 comments
Open

Improve async code coverage #344

viceroypenguin opened this issue Apr 21, 2023 · 0 comments
Milestone
Future

Comments

@viceroypenguin
Copy link
Owner

Currently, code coverage in async version is hampered because each line of await code involves two branches: the sync version and the async version. Currently, only the async version is tested on most lines. Figure out some way to improve coverage by testing both sync and async versions of the await.
@viceroypenguin viceroypenguin added this to the Future milestone Apr 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Future
Development

No branches or pull requests
1 participant
@viceroypenguin