-
-
Notifications
You must be signed in to change notification settings - Fork 377
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
Do not include (and execute) uncovered files #856
Comments
Thank you for your report. Please provide a minimal, self-contained, reproducing test case that shows the problem you are reporting. Without such a minimal, self-contained, reproducing test case I will not be able to investigate this issue. |
Here is minimal reproducible case: Let's have file
when coverage reporting is enabled, the phpunit currently fails to generate the coverage (empty coverage should be reported). |
I can reproduce this:
|
|
Closed via 2da4cf5. |
Summary
see https://github.com/atk4/ui/pull/1628/checks?check_run_id=2476898808#step:9:45
phpunit finishes successfully, but when coverage is disabled, it does fail
Current behavior
How to reproduce
see https://github.com/atk4/ui/pull/1628/checks?check_run_id=2476898808#step:9:45
Expected behavior
When class is not loaded in any phpunit tests, zero coverage must be generated even if parent class is not loadable and no error must be generated.
The text was updated successfully, but these errors were encountered: