Use plain asserts and pytest-mock in tests/unit/test_backend.py
#116
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.
In #115, I need to add tests, and the cleanest way to do that is with parametrization. But:
@mock.patch.object
decorators.So, this switches:
unittest.TestCase
with unittest asserts, to simple test functions with plain asserts.mock
topytest-mock
(a nice wrapper aroundunittest.mock
for pytest-style fixtures)This PR only refactors
tests/unit/test_backend.py
, not any of the other test files.(Contributions welcome to migrate the other tests.)
In order to review this PR, please review each commit separately. For the first commit make sure to "hide whitespace":
(see https://github.blog/news-insights/product-news/ignore-white-space-in-code-review/ for instructions on hiding whitespace changes).