The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Problem/Motivation
While working on #3518869: Allow configs to be enforced by default I didn't find any clear/easy way to run the Behat tests, and I want to add additional test coverage for that feature.
Proposed resolution
Bring over a .local-dev setup similar to that found in workflow_eca, perhaps with some differences.
Remaining tasks
TBD
User interface changes
n/a
API changes
n/a
Data model changes
n/a
Issue fork config_enforce_devel-3520841
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
star-szrNoting a TODO: "make tests" is taking a snapshot, maybe we can use DDEV snapshots for this instead, unless there is a compelling reason not to.
Comment #3
star-szrNoting another TODO/thing to explore: The/opt/projectmount might not be needed with this setup, since our contrib project is available at/var/www/htmland we could presumably use that as our composer symlink.Edit: Nevermind, the separate mount is really helpful.
Comment #4
spiderman@star-szr: I would suggest dropping the "make snapshot" from the "make tests" target in this context- I believe that is cruft from the example I referred you to, which was a project where the tests themselves would restore this snapshot to reset the state. In this case I think that's overkill, and only slows the tests process down.
Comment #39
star-szrMerged into 2.0.x.
I am also going to add credit for @spiderman and @ergonlogic for their support and review on this issue.