- Issue created by @tstoeckler
- Status changed to Active
about 2 months ago 9:39am 4 June 2025 - 🇩🇪Germany tstoeckler Essen, Germany
Looked into this now. Core's
InstallerConfigDirectoryTestBase
really is a bit strange, at the very least for our use-case here. I realized that we were previously not really testing what I thought we were. At the very least you could previously write a test that seemingly would install Standard profile from existing configuration. That is currently not possible and only works in the test becauseInstallerConfigDirectoryTestBase
creates a fake test profile in the site-specific profiles directory.So will first open an MR to fix that which will hopefully allow adding some test coverage with a profile with a config/sync directory more easily next.
- Merge request !33Issue #3395781 by tstoeckler: Improve/fix ExistingConfigTestBase → (Merged) created by tstoeckler
-
tstoeckler →
committed bcd8a6dd on 2.x
Issue #3395781 by tstoeckler: Improve/fix ExistingConfigTestBase
-
tstoeckler →
committed bcd8a6dd on 2.x
- Merge request !34Issue #3395781 by tstoeckler: Add a test with a config/sync profile → (Merged) created by tstoeckler
-
tstoeckler →
committed 3d97236b on 2.x
Issue #3395781 by tstoeckler: Add a test with a config/sync profile
-
tstoeckler →
committed 3d97236b on 2.x
- 🇩🇪Germany tstoeckler Essen, Germany
OK, looks good now.
Will add some docs for the
config_sync_directory
workaround over in 📌 Add explanation of how various scenarios are handled to README Active . Marking fixed. Automatically closed - issue fixed for 2 weeks with no activity.