feat: add '--only-covered' option to '--coverage'#1626
Open
SimonBroekaert wants to merge 1 commit intopestphp:4.xfrom
Open
feat: add '--only-covered' option to '--coverage'#1626SimonBroekaert wants to merge 1 commit intopestphp:4.xfrom
SimonBroekaert wants to merge 1 commit intopestphp:4.xfrom
Conversation
SimonBroekaert
force-pushed
the
feat/add_only-covered_option
branch
from
3416b94 to
c362084
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What:
Description:
This PR adds a new
--only-coveredoption to the Code Coverage feature.This will hide all files from the output that have 0% coverage visually so that it does not break any other --coverage options like --min and --exact.
Reasoning
When working on large applications with lots of files and still wanting to achieve 100% test coverage, it is hard to keep an overview when you want to check if your newly written test file covers a whole feature/Model/Controller/Class...
That's why I propose this option that allows you to keep a better overview by hiding the files that are not covered at all.
Usage