| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
By making testing and coverage separate parts of the configuration, VSCode no longer chokes on discovering tests. This should also make test discovery easier in IDEs like PyCharm. The main problem was that coverage was being treated as default part of testing by always passing coverage flags to pytest (this was also noted in a comment in setup.cfg). Moving this to pyproject.toml may have been unnecessary in the end, but the resources I found online suggested this was the way to go. Adding tox provides a solution to NLeSC#38.
There was a problem hiding this comment.
I depend on GH action to run my tests with different pythons, but doing it locally with tox is helpful.
Can you document a bit the usage of tox and pytest+coverage in the README.dev.md? Now that pytest does not automatically do coverage we should tell the template user about it in another way.
Sorry, something went wrong.
|
@sverhoeven Added documentation in 6d78d07. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
In #311, I forgot to add the .tox directory to .gitignore. Tox stores environments and logs and such there.
| Back | FazBrowse Home | New Git URL |
This PR changes two things:
Edit: also updated a broken link.