We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When running paratest compared to phpunit the deprecations are not listed in the console output.
paratest
phpunit
The deprecations are simply not shown in the output.
Place some deprecation in your code or in vendor code that you call:
@trigger_error('foo', \E_USER_DEPRECATED);
Deprecations should be shown.
In case this matters - this is how we call with and without paratest depending on processes:
if [[ "$processes" = "1" ]]; then exec docker compose run --rm \ --entrypoint=php \ php \ -dpcov.enabled=1 \ -dpcov.directory=/var/www/html \ -dpcov.exclude=~vendor~ \ vendor/bin/phpunit \ -c phpunit.xml \ $@ else exec docker compose run --rm \ --entrypoint=php \ php \ -dpcov.enabled=1 \ -dpcov.directory=/var/www/html \ -dpcov.exclude=~vendor~ \ vendor/bin/paratest \ --passthru-php="-dpcov.enabled=1 -dpcov.directory=/var/www/html -dpcov.exclude=~vendor~" \ --processes=$processes \ -c phpunit.xml \ $@ fi
The lower part is missing when running our suite with paratest:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Summary
When running
paratest
compared tophpunit
the deprecations are not listed in the console output.Current behavior
The deprecations are simply not shown in the output.
How to reproduce: command, code and error stack trace
Place some deprecation in your code or in vendor code that you call:
Expected behavior
Deprecations should be shown.
In case this matters - this is how we call with and without paratest depending on processes:
The lower part is missing when running our suite with paratest:
The text was updated successfully, but these errors were encountered: