-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
include pytest-cov meta.yaml #126
Conversation
add `pytest-cov` coverage tool to `pytest` calls in `meta.yaml`, see how well it works.
Taking out of draft- the workflow will not run for draft PRs |
Seems to work great!
|
aacccctuualllllly i don't know why i'm getting coverage metrics for |
add `omit` field so that `pytest-cov` doesn't include testing scripts (have names matching `*/test_py`) in coverage metrics
for specifying testing paths/directories, etc. directories without testing paths/directories are commented out
I see what you mean. How does it distinguish the test scripts from the actual code, you're asking.
|
latest commit should take care of this! see |
can you see the updated coverage output in the CI logs? I looked for it but couldn't see it. The documentation CI "test" is unhappy now, not related to these updates I think. |
…`meta.yaml` this fixes the syntax highlighting locally when viewing the file in emacs.
restrict `pytest` and `pytest-cov` version to be later. make `.pytest.ini` config file reading more explicit in `pytest` call within `meta.yaml`
in github CI/CD, they move stuff to a temporary dir, so .coveragerc and .pytest.ini were not found by github's runners make references to these configs explicit in meta.yaml call now to help avoid confusion
…st-cov at all. last check before asking for review and merge. if this pipeline doesnt work, restrictions to versions will be added back in
... no, but i think i see something relevant here... from our CI/CD:
... from my local copy however:
for doc changes that fix this: #125 |
…argeted test directories. lets see if that helps the github CI/CD
looks good enough to me- the new empty merging! |
Describe your changes
add
pytest-cov
coverage tool topytest
calls inmeta.yaml
, see how well it works.not totally sure I want to merge this yet, but it's easier to run the workflow with a draft PR open.
Issue ticket number and link (if applicable)
Issue #122
Checklist before requesting a review
N/A
I tried to comment my codeN/A
I wrote a new test, if applicableN/A
I wrote new instructions/documentation, if applicableN/A
I ran pylint and attempted to implement some of it's feedback