You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When PHPUnit is installed via Composer and Composer's vendor/autoload.php is used as PHPUnit's bootstrap then the Composer-installed PHPUnit will be used instead of the one actually invoked, for instance one invoked from a PHAR:
$ cat composer.json
{
"require-dev": {
"phpunit/phpunit": "~3.7"
}
}
$ ./vendor/bin/phpunit --version
PHPUnit 3.7.38 by Sebastian Bergmann.
$ php phpunit.phar --version
PHPUnit 4.4.5 by Sebastian Bergmann.
$ php phpunit.phar --bootstrap vendor/autoload.php tests
PHPUnit 3.7.38 by Sebastian Bergmann.
Configuration read from /home/sb/test/phpunit.xml
.
.
.
The text was updated successfully, but these errors were encountered:
It was discussed in one of the existing issues already. The only way to "force" the code of the .phar would be to front-load all PHPUnit files into memory, so that the classloader is no longer triggered.
When PHPUnit is installed via Composer and Composer's
vendor/autoload.php
is used as PHPUnit's bootstrap then the Composer-installed PHPUnit will be used instead of the one actually invoked, for instance one invoked from a PHAR:The text was updated successfully, but these errors were encountered: