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 I try to execute a functional test, the dynamically generated "TYPO3 Configuration" cannot be read. For example no connection to the TestDB can be created, because the credendtials are missing.
Cause is that the typo3/testing-framework creates a temporary typo3conf/LocalConfiguration.php file, but this is not accepted from the extended ConfigurationManager.
Now my question:
Do I have something configured wrong?
Is it possible to disable the extended ConfigurationManager from this package in FunctionalTests or to configure it to read the temporary LocalConfiguration?
kind regards
DM
The text was updated successfully, but these errors were encountered:
The only solution for now is to remove this package before executing functional tests. Since this is possible to automate in a CI, I don't think I'm going to provide any other workaround any time soon.
@devmes@moe2k A very simple fix would be to wrap the alias call with a check against an env var, so that the package can be disabled for test. Would this server the purpose for you? The only an env var needs to be exposed during testing.
When I try to execute a functional test, the dynamically generated "TYPO3 Configuration" cannot be read. For example no connection to the TestDB can be created, because the credendtials are missing.
Cause is that the typo3/testing-framework creates a temporary typo3conf/LocalConfiguration.php file, but this is not accepted from the extended ConfigurationManager.
Now my question:
kind regards
DM
The text was updated successfully, but these errors were encountered: