-
Notifications
You must be signed in to change notification settings - Fork 44
Modernize tests for esmvalcore.preprocessor.save
#1799
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
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1799 +/- ##
=======================================
Coverage 91.51% 91.51%
=======================================
Files 202 202
Lines 10908 10908
=======================================
Hits 9982 9982
Misses 926 926 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
esmvalcore.preprocessor.saveesmvalcore.preprocessor.save
valeriupredoi
left a comment
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.
cheers @bouweandela - wouldn't it even better to make those tests individual functions outside the overarching test class? Either way - modern now 😁
Yes, but it would make the diff much bigger. Anyway, I can do another commit to change it if you want? |
|
@valeriupredoi I removed the overarching class. Could you have another look please? |
valeriupredoi
left a comment
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.
lovely! I think the extra work is worth it, cheers, bud 🍺
|
@ESMValGroup/technical-lead-development-team Could someone please do a final check and merge? |
|
Thanks @bouweandela @valeriupredoi 🚀 |
Description
This modernizes the unit tests for
esmvalcore.preprocessor.saveand adds an extra test that the parent directory of the target file is created if it does not exist.Part of #1609.
Before you get started
Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.
To help with the number pull requests: