[5.4 + LTS] Fix tests code coverage config. #19609
Merged
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.
Hi folks,
I've just seen that since.. a long time ago (don't know when exactly), the code coverage config is completely outdated, so all the views was dumped instead of lunching code coverage.
This post from @egorpe show exactly the issue:
https://laracasts.com/discuss/channels/laravel/phpunit-coverage-for-laravel-framework-spits-out-html-instead-of-running-tests
You can see the failure on his travis build:
https://travis-ci.org/egorpe/framework/jobs/241038092
This PR update the config, so the code coverage is passing now (but is actually a bit scary ^^")