-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Monitor code coverage #93
Comments
Do you have idea how this can be done? |
Nope, doing it in CLI is easy but displaying the result might be harder. It might be possible to do through GitHub artifacts but I have no experience with it. |
Jest integrates with Istanbul to create nice HTML visualizations of code
coverage, could we integrate that into a GH action/artifact?
…On Wed, Oct 20, 2021 at 2:50 PM Jonatan Asketorp ***@***.***> wrote:
Nope, doing it in CLI is easy
<https://jestjs.io/docs/cli#--coverageboolean> but displaying the result
might be harder. It might be possible to do through GitHub artifacts but I
have no experience with it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#93 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEBHUR24M57WC2M56EYIZ7TUH4FNXANCNFSM5AW4HDVQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
We can probably show the change in code coverage using GitHub's commit status API. It might be possible to use the URL to download the Istanbul visualization even if we can't display it. |
Is your feature request related to a problem? Please describe.
It would be nice to monitor the code coverage if we hope more volunteers will be contributing. E.g., how does a specific PR change the code coverage compared to the
main
branch?The text was updated successfully, but these errors were encountered: