-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Measure test coverage #9203
Comments
Can you assign this to me? |
@yeikel done. Thank you! |
Can you assign this to me? |
@smoookeeey I assigned you too, but @yeikel asked to be assigned first. Please make sure you don't duplicate any work @yeikel might have already done. |
Yes I will make sure not too do that |
I haven't started yet, and I won't have capacity until sometime next week. @smoookeeey, if you pick it up before that, feel free to create the PR and link it here |
I will look into it brother |
Thanks a lot @yeikel and @smoookeeey ! |
I just discovered that test coverage was previously added in #2576 to prevent a regression. Originally line coverage was set to 80% and branch coverage to 70%, with It was later gated behind the |
I think that rather than enforcing a certain %, we can start reporting it for awareness |
I agree. Reporting-only is a good start. Then something like |
@smoookeeey Are you still working on this? Feel free to create a draft PR whenever you're ready |
@yeikel I think you can go ahead with this if you want. |
Code improvement description
Test coverage is a simple measure of how much of the codebase has been tested. I think that setting specific coverage levels is not very helpful beyond a certain point, but it can help identify parts of the codebase that are poorly tested and may require more attention.
The most popular library for measuring code coverage in Ruby is simplecov.
The text was updated successfully, but these errors were encountered: