-
Notifications
You must be signed in to change notification settings - Fork 3
Units tests for data_load.py #548
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
base: main
Are you sure you want to change the base?
Conversation
…overage/core-data_load
…overage/core-data_load
The failing test is almost certainly my fault. I can go in a fix it. edit: apparently just re-running it worked. yay 🥳 |
@neilSchroeder Thanks! |
Yeah, sometimes the test environment just doesn't build right. Sigh |
@elehmer can you take a look at this code and approve? |
Will try and get to it this afternoon |
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.
Looks really good. If we merge the all_touched
PR first we will need to make a test for that option. Thanks
@elehmer Can do |
Summary of changes and related issue
Add more unit tests for core.data_load.py to get coverage up to 83%. Add type hints to data_load.py.
Relevant motivation and context
We want to increase test coverage to at least 80%.
No tests written for read_catalog_from_csv(), which is unused and will be removed.
How to test
These tests have taken ~7 minutes to complete for me locally. Many of the tests are loading and checking real datasets.
I ran the interactive_data_access_and_viz and historical_climate_data_comparisons notebooks to check that changes to data_load.py have not affected any workflows.
Type of change
To-Do
_
before the name