As part of T112204, the configuration for the test surveys was copypastad over to the BC configuration file. This approach was taken because:

• we didn't want to have the default configuration for QuickSurveys to include test surveys – including a disabled example survey is reasonable
• we didn't want to require a file in the BC configuration file that wasn't the extension's entry point

There's got to be a cleaner way to share this configuration between our per-commit integration tests, which is stored in /path/to/QuickSurveys/tests/browser/LocalSettings.php, and the nightly integration tests run against the BC.

Possible solutions

• being able to configure surveys on-wiki and creating them during the integration tests – this would be neato!
• actually loading the test survey configuration from a shared file by requireing it in the BC configuration file
• storing the test survey configuration in the extensions configuration and enabling the surveys in the BC configuration file
• something glaringly obvious that we've missed