-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Add CLI flag to generate only one type of CC & Logging regardless of phpunit.xml #4401
Comments
The above makes sense to me and I will implement this for PHPUnit 9.4. |
Ping @Jean85 as this may help your https://github.com/facile-it/paraunit too |
Thanks for the ping but I follow a different approach, without altering the original XML config; I only use CLI options. |
This is going OT, by the way we don't manipulate anything. @Jean85 if you run |
@Slamdunk Thank you for the clarification! |
I think this should be done after #4292. |
Supersed by #4446. |
Hi, I'm the current maintainer of https://github.com/paratestphp/paratest, a tool to run PHPUnit in parallel, leveraging sub-processes.
A feature we must provide is to generate code-coverage and logging accordingly to
phpunit.xml
specifications.Our tool should:
phpunit.xml
<filter/coverage>
and<logging>
sections, which may all set to all the available configurationscoverage-php
andlog-junit
into PHPUnit sub-processesphpunit.xml
<filter/coverage>
and<logging>
sectionsAs of yet this can't be done because if
<filter/coverage>
and<logging>
sections are specified inphpunit.xml
, cc and logs are always generated except with--no-coverage
/--no-logging
active, but with--no-coverage
/--no-logging
active no cc nor logs are generated at all.The workaround we are using right now is suggesting not to have any section in
phpunit.xml
except the<whitelist>
one, and specify each option in the CLI, so ParaTest can easily rewrite them as wish, but of course this is sub-optimal.So I'm asking something like
vendor/bin/phpunit --no-coverage --coverage-php tmp.php --no-logging --log-junit tmp.log
.If you so kind to write down few instructions to how and where implement such feature, I'm happy to propose a PR.
The text was updated successfully, but these errors were encountered: