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

Code coverage #107

Open
cscherrer opened this issue Mar 8, 2023 · 2 comments
Open

Code coverage #107

cscherrer opened this issue Mar 8, 2023 · 2 comments
Labels

Comments

@cscherrer
Copy link
Contributor

It can be useful to have a quick reference for a given PR telling about changes in code coverage. For example, codecov seems nice for this, though there are many others.
https://about.codecov.io/tool/pytest/

Let's see about getting something like this set up.

@cscherrer cscherrer changed the title Cover coverage Code coverage Mar 8, 2023
@SamWitty
Copy link
Collaborator

It looks like the master branch has some code coverage utilities built into the testing suite. @cscherrer could you try pulling from master and running ./scripts/test.sh and see if that satisfies what you're looking for here?

@cscherrer
Copy link
Contributor Author

Thanks @SamWitty, I should have been more specific about the goal of this. What I'd really like is some indication of changes in code coverage for a given PR, ideally just provided by some bot as a comment on the PR. According to @eb8680 , things had previously been set up this way, but it was disabled because any reduction in coverage was leading to lots of annoying email messages.

So ideally we could have

  • A bot that computes code coverage differences for a given PR, and
  • provides a useful summary as a comment in that PR, but
  • doesn't spam us about it

@eb8680 eb8680 added this to the Release 0.1.0 milestone Jul 11, 2023
@eb8680 eb8680 removed this from the Release 0.1.0 milestone Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants