-
Notifications
You must be signed in to change notification settings - Fork 1
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
95 uc tests #128
95 uc tests #128
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## dev #128 +/- ##
==========================================
+ Coverage 84.86% 86.17% +1.31%
==========================================
Files 10 10
Lines 674 738 +64
==========================================
+ Hits 572 636 +64
Misses 102 102
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
This all LGTM - thanks for putting this together!
I've checked all fixtures and unit tests within this updated test file, and it all performs as expected. In particular, the new unit tests checking the behaviours of the population thresholding, diagonal cell inclusion/exclusion, total cluster thresholding, and filling methods are performing as expected (I've confirmed all the assertions match expectations). The addition polygon checks on the vectorised urban centre boundary and bbox are working as expected too.
Overall, this is a great example of designing unit tests to prove correct methodology whilst keeping the tests maintainable - nice job!
I'm happy to merge this PR into dev
.
Description
Added unit tests to check for intermediate and final outputs of the
raster_uc
module.Fixes #95
Motivation and Context
Currently tests check for input and output types, but they don't check if actual output is as expected.
Type of change
How Has This Been Tested?
Unit tests run and passed using default values. Unit tests failing as expected if modifying fixtures or expected values in assertion.
Test configuration details:
Advice for reviewer
Where there are several tests for the same function or output, they have been grouped in classes so they use the same parametrisation. However, when output is checked, only those combinations that are expected to not return error are considered.
Note that docstrings are not included in this test script, but this will be added later.
Checklist:
Additional comments