-
Notifications
You must be signed in to change notification settings - Fork 10
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
Test coverage is not triggered by github action #669
Comments
With github actions, this might be difficult to do. Found this workaround, but have no idea if there is a simpler way: |
I can also update the covering at each release manually |
Anyone can also run coverage locally to see whether it increased or not |
Using coveralls instead of python-coveralls we could trigger directly on github-action: https://coveralls-python.readthedocs.io/en/latest/usage/configuration.html#github-actions-support |
Hi @Bachibouzouk, what I've found out:
Sadly, I did not get coveralls to run with pvcompare --> I will stop for today and let you know in case I get a step further ;) |
I've managed to upload test coverage automatically at commit, however test coverage is not shown - you can only check the tested / not tested lines (click on modules), see coveralls pvcompare well, step by step ;) note that I had to use Update: maybe there was a bug yesterday at coveralls.io, because now it's working 👍 |
The command to implement in the githut action
.github/workflows/main.yml
file as the last step is the following:This had failed when calling
coverage report -m
because of an import error on python 3.6 --> need to find out why and a solutionThe text was updated successfully, but these errors were encountered: