Fix test name collision (test_writeArrayToRaster) #669
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
This change renames the writeArrayToRaster series of tests so that none of them override each other by having the same name. The test that wasn't running had a small error that I assume was a typo, and it has been corrected.
Aside: I found this error by running
ruff
on the project. I did not add tests to ensure a similar problem won't occur again because #650 may already provide a comprehensive solution.Motivation and Context
test_util.py
has two functions namedtest_writeArrayToRaster_3
. Because of the way Python works, the first function was being erased and replaced with the second one, causing it to never run.How Has This Been Tested?
This change does not break any tests. The test that was re-enabled passes too.
Type of change
Checklist:
I have written new tests for your core changes, as applicable.My change requires a change to the documentation.I have updated the documentation accordingly.