I have added the return type hints to some test functions.
Motivation and Context
Taking advantage of type hints, this contributes to make the test functions more clear and readable.
Have you tested this? If so, how?
I have run, locally, on macOS:
python -m pytest
All tests are passing. Overall, there is no change in behavior.
Checklist for PR author(s)
[x] Changes are covered by unit tests (no major decrease in code coverage %).
[x] All tests pass.
[x] Docstring coverage is 100% via tox -e docs or interrogate -c pyproject.toml (I mean, we should set a good example :smile:).
[x] Updates to documentation:
[x] Document any relevant additions/changes in README.rst.
[x] Manually update both the README.rstanddocs/index.rst for any new/changed CLI flags.
[x] Any changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecateddirectives. Find the appropriate next version in the project's __init__.py file.
Hey, I just made a Pull Request!
Description
I have added the return type hints to some test functions.
Motivation and Context
Taking advantage of type hints, this contributes to make the test functions more clear and readable.
Have you tested this? If so, how?
I have run, locally, on macOS:
All tests are passing. Overall, there is no change in behavior.
Checklist for PR author(s)
tox -e docs
orinterrogate -c pyproject.toml
(I mean, we should set a good example :smile:).README.rst
.README.rst
anddocs/index.rst
for any new/changed CLI flags.versionadded
,versionchanged
, ordeprecated
directives. Find the appropriate next version in the project's__init__.py
file.Release note