-
Notifications
You must be signed in to change notification settings - Fork 166
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
Improved test setup #960
Improved test setup #960
Conversation
@jonasBoss this is quite a lot to review I guess, sorry. This isn't urgent, but if you don't have time to spare any time soon I feel fine with just merging it. I'm not sure if there is anything important to look at, no features were added or bugs fixed, it's just refactoring and changes to tests. The |
There are lots of new TODO comments scattered about mentioning dependency injection. A case-sensitive search for |
@jonasBoss are you currently available? |
yeah I currently have some free time. |
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.
So this is mostly about moving all the standalone functions into classes?
I don't see any obvious issues!
Applying a few things I learned in the past 2 years to input-remapper.
With this, import order and patch order doesn't matter anymore
This allows:
@patch.object(...)
) and it allows to do things without having to call super() in setUp and tearDown.