-
Notifications
You must be signed in to change notification settings - Fork 110
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
Implement quick wins to fix code coverage in Image Prioritizer and Embed Optimizer #1945
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## trunk #1945 +/- ##
==========================================
+ Coverage 71.08% 72.37% +1.29%
==========================================
Files 86 85 -1
Lines 6969 6998 +29
==========================================
+ Hits 4954 5065 +111
+ Misses 2015 1933 -82
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM !!
However just a small concern,
Coverage of Image Prioritizer
seems to be improved a little, now at 89%
but embed-optimizer
remained at 67%.
Maybe because of missing unit test cases.
If that's the case then the code refactoring part of embed optimizer
along with new test cases should ideally be in another PR ?
Just a suggestion 🙇🏻
@sarthak-19 Thanks for checking. Yes, it's expected that Embed Optimizer would barely have any improvement since there was barely any change. So yes, let's follow up with another PR to add the tests for the functions that exist in |
Sure thing !! 😄 |
@covers
// @codeCoverageIgnoreEnd
inhooks.php
.@access private
tags to the functions in Embed Optimizer.Note the large diff in Embed Optimizer is just moving the functions out of
hooks.php
to be placed inhelpers.php
which follows the pattern used by other plugins.See #1789