-
Notifications
You must be signed in to change notification settings - Fork 921
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
Increase test coverage for generic modules #2806
Conversation
Eh, it's about ready now. Baby steps. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the clone
stuff may be a bit redundant after #2981?
But more tests = yay, so all approved from my side!
Besides that it doesn't build, could we have tests in the file they are testing? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests LGTM as well.
Let me know if you want me to fix the Web build, didn't look into why it fails rn.
- Rename attr_coverage functions to be more descriptive - Move tests to the file that they test - Fix build errors caused by changes to the Event enum Signed-off-by: John Nunley <[email protected]>
CHANGELOG.md
if knowledge of this change could be valuable to usersThis PR adds test cases for the higher-level modules of
winit
(dpi, event, etc). The goal here is to have 100% test coverage forwinit
, or at least as high as we can reasonably reach.WIP