Cleanup test classes to eliminate warnings coming from PyTest. #168
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.
Fixes #167
Resolved all Pytest warnings. Mostly by renaming and/or rescoping test supporting classes that were incorrectly being picked up as tests. For some classes, this was a rename. Detailed info on each issue resolves is found in #167.
Added in a pytest.ini file to automatically run all the tests in strict / warnings-as-error mode. This should cause the local builds, GitHub builds, and ADO builds to all run tests in the same way.
The only code error fixed was in the CosmosDB storage provider which was failing to close the config file after loading it to JSON. This was flagged by PyTest as a resource leak once the strict mode was enabled, so I cleaned that up.