Decide what to do with outdated configuration path

[alexanderschnitzler]

Testbase does still fall back to typo3conf/LocalConfiguration.php although TYPO3 12 uses /config/system/settings.php nowadays. Should the fallback be dropped or at least be used after having tried /config/system/settings.php or should users simply switch to env variables?

Reference:

testing-framework/Classes/Core/Testbase.php

Line 464 in cd54b88

$originalConfigurationArray = require ORIGINAL_ROOT . 'typo3conf/LocalConfiguration.php';

[sbuerk]

Personally, I would remove that "magic" fallback. But I guess we can't to that so easiely. So it should be fallback to v12 composer style variant with TF8 .. and TF7 based installed core version.

I'm more for "explicitly configure it". Some may have such a "file" for extension level testing to avoid using env variables .. but in a project it reuses the real instance settings.There may be reasons for that.

So not sure ... at least we should align to used core version default behaviour. Which makes it for TF7 more jumpy.

Multi DBMBS testing is easier with env variables, using the config file is a lazy excude why not doing multi database functional tests.

Had it on todo list to thing about it, but good to know that someone stumpled upon it ;) so I guess the simply remove it is maybe off the table.