The Ruby browser test running script has this enviable clause, https://phabricator.wikimedia.org/source/integration-config/browse/master/dockerfiles/quibble-stretch-bundle/mwselenium.sh$35-39
I want the same thing for selenium testsOur use case is T190829, so that MediaWiki configuration can be added before my test. Infor which we want to add this specific case, for T190829 I want to add:configuration to LocalSettings.php:
$wgEnableUploads = true;
ActuIdeally, the `mwselenium.sh` wouldn't quite work in our casewe can install this custom config and launch a corresponding PHP server for just this one extension's browser tests. I can imagine that we use a LocalSettings.d similar to how mediawiki-vagrant is configured, since the test is being run from mw-core so the `base_dir` is irrelevant to the extension repo where we need to adjust the LocalSettings.php. For the same reason, I'm not seeing an easy workaround where I inject settings from an extension script. If anything, I need to do this injection from the test case itselfor maybe we can just supply the configuration on the command-line to reduce potential race conditions if servers are launched for other extensions.
This just became possible with T199116.
== Precedents ==
The Ruby browser test running script would cat directly onto LocalSettings.php,
https://phabricator.wikimedia.org/source/integration-config/browse/master/dockerfiles/quibble-stretch-bundle/mwselenium.sh$35-39
Unfortunately, which feels very wrongthis can't be cleaned up easily and will break isolation between tests.