Skip to content
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

Add code coverage analysis #77

Closed
ErikBjare opened this issue Dec 24, 2020 · 2 comments · Fixed by #88 · May be fixed by #93
Closed

Add code coverage analysis #77

ErikBjare opened this issue Dec 24, 2020 · 2 comments · Fixed by #88 · May be fixed by #93
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Milestone

Comments

@ErikBjare
Copy link
Collaborator

Another improvement to the CI pipeline.

We don't have much in the way of tests, but we do have the auto examples which run a fair bit of the code. It'd be nice to know exactly which code is somewhat tested in CI, and which isn't (and when new code is added, how well covered it is by tests/examples).

This should be easy enough to do with coverage.py.

@JohnGriffiths
Copy link
Collaborator

Agree- the examples have a very test-like function but that isn't explicitly documented. Coverage tracking would be great to include

@JohnGriffiths JohnGriffiths added documentation Improvements or additions to documentation enhancement New feature or request labels Mar 19, 2021
@JohnGriffiths JohnGriffiths added this to the q2-2021 milestone Mar 19, 2021
@ErikBjare
Copy link
Collaborator Author

ErikBjare commented Mar 26, 2021

I added coverage for *.ipynb notebooks in my thesis repo the other day, but I'm not sure how to do it for the auto_examples...

I gave it a shot in #88, but it's not ready yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
2 participants