feat: Add test cases for loading boundary with GeoJSON, BytesIO, BBOX string, and invalid boundary types #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… string, and invalid boundary types
donaldte
changed the title
donaldte
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
hotosm#203
I've added comprehensive test cases for loading the boundary in the basemapper module. These tests cover various input types including GeoJSON files, BytesIO objects containing GeoJSON data, BBOX strings, and invalid boundary types to ensure proper error handling.
These tests enhance the test coverage and ensure the robustness of the codebase, contributing to better reliability and maintainability.
Please review and merge at your earliest convenience.
Thank you!