-
Notifications
You must be signed in to change notification settings - Fork 69
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
[SPIKE] Discovery on using Codecov.io #16136
Comments
Hey team! Please add your planning poker estimate with Zenhub @ariperez @edmund-dunn @JunTaoLuo @olivereri @teeshe |
We're unlikely to adopt Codecov.io as our code coverage reporting tool in the near future. The main roadblock is getting the right permissions to use the tool in this repository. Here's a short write up of the findings from this discovery task. The purpose of Codecov.io is to present PHPUnit's code coverage information in a more reader friendly format and track that coverage over time. For example, our current coverage is available in the logs, it is rarely inspected and changes over time is not easy to track: Setting up this tool is also relatively simple, here's an example PR with all the necessary changes which is simply several lines in our GHA workflow file. However the main issue with the tool is that in order for all the interactions we showed above, we need to have the permission to configure the app for the repository owner (i.e. department-of-veterans-affairs) instead the repository we control (i.e. va.gov-cms). This is a major blocker for adopting this tool but we can likely work with the VA to get this set up. Here's a follow-up issue to track that work. Finally, given that we are an open source project, Codecov.io's free tier will provide all of the features we need. Note that the free tier doesn't support private repos but that doesn't matter in this case since the repos we want coverage report for in CMS are public. Here's a link to the pricing for those interested. |
Description
Followup to #15554.
The platform does not appear to have a single 1 recommended solution for code coverage reporting. I'm a fan of Codecov.io and it appears to be free for our use, so I'd like to do discovery into adopting it on a purely advisory, non-PR-blocking level.
Acceptance Criteria
Footnotes
Slack conversation ↩
The text was updated successfully, but these errors were encountered: