Test digitaltwin #2
Closed
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
12 tasks
…olumes mounted (used like this when deploying to AWS
LukeParky
force-pushed
the
test_digitaltwin
branch
from
edd51f3 to
2c48b0b
Compare
|
We're moving this PR into the main codebase so any updates will be in GeospatialResearch#175 |
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.
DESCRIPTION OF PR:
Unit test cases for the digitaltwin module
test_data_to_db is not working, unable to mock 'Engine'
Functions with 'Engine' as parameter were not tested
test_get_data_using_geoapis has 4 tests failing, will need to double-check if the failing unit tests are written correctly
Developer Checklist
Reviewer Checklist