Skip to content
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

Improve test coverage #42

Open
thwllms opened this issue Jun 3, 2024 · 0 comments
Open

Improve test coverage #42

thwllms opened this issue Jun 3, 2024 · 0 comments
Labels
testing Related to unit tests, functional testing, etc.

Comments

@thwllms
Copy link
Contributor

thwllms commented Jun 3, 2024

Following resolution of #41, let's do as much as we can to close remaining gaps in test coverage. E.g.,

  • Methods returning empty GeoDataFrame objects when data is missing
  • For methods throwing NotImplementedException -- write very simple tests verifying that that exception is indeed thrown. This will serve as a reminder to write those tests when those methods are finally implemented.

We should be able to get pretty close to 100% test coverage overall.

@thwllms thwllms added the testing Related to unit tests, functional testing, etc. label Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Related to unit tests, functional testing, etc.
Projects
None yet
Development

No branches or pull requests

1 participant