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
Given the changes made at #491, using config/bootstrap.php as bootstrap of phpunit is not possible if .env.local.php exists without variables that closely belongs to the "test" env ("KERNEL_CLASS", "SYMFONY_DEPRECATIONS_HELPER", etc); since the file from where these variables should be loaded (.env.test) isn't required at all:
Since these variables are not common for the local environment, the dumped array at .env.local.php doesn't contains them, making the test suite unusable without changes:
Yes, that's correct. We need to enhance documentation around this as it's quite new.
As you spotted, .env.local.php freezes .env files. As such and on purpose, it's only for prod-like needs. Don't use it in test nor dev.
Given the changes made at #491, using
config/bootstrap.php
as bootstrap of phpunit is not possible if.env.local.php
exists without variables that closely belongs to the "test" env ("KERNEL_CLASS", "SYMFONY_DEPRECATIONS_HELPER", etc); since the file from where these variables should be loaded (.env.test
) isn't required at all:recipes/symfony/phpunit-bridge/3.3/.env.test
Lines 2 to 4 in c466e7a
Since these variables are not common for the local environment, the dumped array at
.env.local.php
doesn't contains them, making the test suite unusable without changes:recipes/symfony/framework-bundle/3.3/config/bootstrap.php
Lines 9 to 13 in c466e7a
The text was updated successfully, but these errors were encountered: